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

When object creation fails (intermediate state) while using decoupled archive naming policy, the object physical path remains in consistent mode. #2160

Open
1 task
JustinKyleJames opened this issue Jan 6, 2024 · 0 comments
Labels

Comments

@JustinKyleJames
Copy link
Contributor

JustinKyleJames commented Jan 6, 2024

  • main

When object creation fails while using decoupled archive naming policy, the object physical path remains in consistent mode.

This was discovered when running the test case which does the following:

  1. Sets invalid secret key for the S3 credentials.
  2. Attempt to put the a file to the S3 resource which has archive naming policy of decoupled.
  3. The object remains in an intermediate state.
  4. Checking the physical path is appears as if the archive naming policy is consistent.

It appears that the things set up to make sure the physical path is updated doesn't get reflected back to the database.

This is a minor issues for the following reasons:

  1. Once the secret key is fixed, subsequent overwrites will be successful. All other operations (reads/removals/etc) succeed.
  2. The physical path (S3 object key) used will be the same as what was in the database so there is no inconsistency.
  3. While the physical path (S3 object key) is not as expected, this is a fairly obscure scenario.

At this point since this is a minor issue, I propose it only gets fixed in 4.3.

@alanking alanking added the bug label Jan 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants