Fixed issues in Apache Ozone

Review the list of Ozone issues that are resolved in Cloudera Runtime 7.1.7 SP1.

CDPD-33191: Fixed the problem that S3 copy-object request would fail if source name contained special chars. For example,=.
This issue is now resolved.
CDPD-33186: The Ozone Recon service was incorrectly flagging deleted containers as missing.
This issue is now resolved.
CDPD-33182: When using the ofs scheme to access an Ozone cluster, the "mkdir -p" operation now correctly creates the target bucket if it did not exist already.
This issue is now resolved.
CDPD-33180: This fix addresses a bug in the Storage Container Manager component of Ozone that would result in the SCM crashing after restart.
This issue is now resolved.
CDPD-33176: This fixes a potential data loss issue during multi-part upload commit where the key contents may have been incorrectly garbage collected.
This issue is now resolved.
CDPD-30734: Fixed the problem that keys stored in encrypted buckets in Ozone via S3 multipart upload (MPU) could not be read by client, if MPU part size was not a multiple of 8KB.
This issue is now resolved.
CDPD-30185: Impala did not work correctly with Ozone paths using the ofs file system scheme in CDP 7.1.7. This has been fixed in 7.1.7 SP1.
This issue is now resolved.

Apache Patch Information

  • HDDS-6096
  • HDDS-5235
  • HDDS-5891
  • HDDS-5973
  • HDDS-5893
  • HDDS-5461
  • HDDS-6349