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.

Sign up for GitHub

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

Jump to bottom

Allow to create/update a file which is already in S3 #4839

Closed
imsdu opened this issue Apr 5, 2024 · 0 comments · Fixed by #4878
Closed

Allow to create/update a file which is already in S3 #4839

imsdu opened this issue Apr 5, 2024 · 0 comments · Fixed by #4878
Assignees
@dantb
Labels
delta feature

Comments

@imsdu
Copy link
Contributor

imsdu commented Apr 5, 2024 •
edited
Loading

Motivation
Some files may be pushed in S3 by other channels than Delta and we still want them to be registered in Nexus

Acceptance criteria

  1. The file must exist in S3
  2. The file stays in the same location
  3. S3 Object metadata is used to populate fields like the file size or the checksum
  4. Nexus file metadata can be optionally provided like the other operations on files
  5. The file registered this way must have a dedicated FileAttributesOrigin
  6. Documentation should inform that it is not the recommended way as Nexus is not taking care of the storage of the physical file
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dantb dantb

Labels
delta feature
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Register S3 files in-place dantb/nexus
2 participants
@imsdu @dantb