Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

asset: never reprocess assets when duplicated #1979

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

gioelecerati
Copy link
Member

What does this pull request do? Explain your changes. (required)

Just a proposal to never reprocess assets when the import url is duplicated per userId

Specific updates (required)

How did you test each of these updates (required)

Does this pull request close any open issues?

Screenshots (optional)

Checklist

  • I have read the CONTRIBUTING document.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.

@gioelecerati gioelecerati requested a review from a team as a code owner November 20, 2023 13:00
Copy link

vercel bot commented Nov 20, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
livepeer-studio ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 20, 2023 1:02pm

@victorges
Copy link
Member

As per our discussion on Discord, I am unsure about this since it might not make sense all users to share the same asset objects between their end-users because the underlying videos is the same. Different users wouldn't be able to set custom access control conditions on their version for example. IMO we can optimize this on the infrastructure layer, like sharing the storage for the assets with the same content, but it is still useful to have the separate asset "metadata objects" imo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants