...
1. builds/intermittent test failures
TODOThere are no intermittent failures specific to the HDDS-2939 branch as of now. During the development , it was ensured all the CI checks are clean prior to every commit merge .The plan is to run repeated CI checks on the merge commit to master.
2. documentation
TODODescribed feature in apache ozone page via HDDS-5067.
3. design, attached the docs
TODOAll the design docs are linked from the documentation as part of HDDS-2939
4. s3 compatibility
TODOThere are no incompatibilities with respect to S3.
5. docker-compose / acceptance tests
TODOAdded docker test cases.
6. support of containers / Kubernetes:
NA. Deployment model for OzoneManager remains as earlier.
Example files are committed with HDDS-5018TODO
7. coverage/code quality:
Sonar master branch
Sonar HDDS-2939 branch.
The branch has better coverage than master.TODO
8. build time
There is no significant difference between local build time
...
.
Recent HDDS-2939 branch buildTODO
9. possible incompatible changes/used feature flag:
TODOFor using this feature, "ozone.om.metadata.layout" config needs to be set to be true in ozone-site.xml.
10. third party dependencies/licence changes:
...
No new dependencies are added.
11. performance
Done testing to evaluate the performance of delete, rename operations in feature branch vs master code base. Following charts capturing the directory delete and rename operations execution time shows that, feature branch has a very significant performance gain compared to the master.
...
12. security considerations
TODOEverything works as earlier and there is no security implications because of the feature.