Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
EC-Branch
-
None
Description
sodonnell pointed out that, currently we are taking bucket default at client and passing to server when there are no client defaults. This could be an issue if some one changes the bucket replication config behind but client holds the old bucket object and keep creating the keys.
This Jira to investigate and address the issue.
One idea to check the feasibility is that, when client does not have replicationConfig configured, we just need to pass null/NoOpReplicationConfig.SO, that server can take the buchekdefaults or server defaults based on availability.
Attachments
Issue Links
- links to