@Marton, [1] backward compatibility: No backward compatibility issues. S3 works well as the feature code sits behind the ozone.om.metadata.layout feature flag. Yes, same normalization behavior as before. Even with feature turned ON the normalization behaviour is the same, as the configuration "ozone.om.enable.filesystem.paths" should be set to "true".
Thanks the answer. It turned out that we have backward compatibility issues: when the flag is turned on in an existing cluster we can have unexpected results. One problem is tracked with HDDS-5094, but --- in general -- I think we should be sure that we have no data inconsistency loss when feature flag is modified in a cluster. Just to having the flag doesn't save us from all the backward compatibility issues.
[2] performance: When it is turned OFF then there is zero performance penalty because the existing functionality is not changed. With the feature flag turned OFF, master code will create intermediate directories during create. When it is turned ON the prefix code also does a similar approach during create. But, surely we will be focusing on the performance path post merge and improving it further.
My question was about the normal key creation performance when the flag is turned ON. We shared that the deletion / rename performance is significant better, but I guess we have some overhead in the normal key creation which would be great to know.
[4] security: As you have pointed out, everything works as earlier and there are no security implications because of the feature.
I just learned that we have new code for all the new key creation including new ACL checks. So we have new implementation for the existing functionalities. (I am not sure if we can any test to be more sure, but it's definitely something which is changed, and -- imho -- even the alpha features should be secure on master).
Thanks the answers, Marton --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@ozone.apache.org For additional commands, e-mail: dev-h...@ozone.apache.org
