Fixed issues in Cloudera Data Explorer (Hue)

Fixed issues for Cloudera Data Explorer (Hue) are addressed in Cloudera Runtime 7.3.3.

Cloudera Runtime 7.3.3

CDPD-125832: Storage Browser file download failure in Data Explorer
7.3.3.0
Previously, file downloads and previews failed when you used the Storage Browser in Data Explorer behind a Knox gateway. This issue occurred because generated download and preview URLs omitted the required gateway proxy prefix, preventing requests from reaching the service. This issue is resolved by appending the proxy path prefix to download and preview URLs.
CDPD-125184: Oozie workflow submission failure in Data Explorer
7.3.3.0
Previously, submitting Oozie workflows from the Storage Browser in Data Explorer failed. This issue occurred because workflow submission omitted external parameter names. This issue is resolved by preserving workflow variable parameters, correcting processing, and refining route query parameters during submission.
CDPD-124478: Error when accessing the Impala tab in the Jobs browser
7.3.3.0
Previously, an error occurred when you clicked a query ID in the editor to open the query profile page if your environment uses an active-passive coordinator setup. This issue exists as a result of changes made to support active-active coordinator configurations, preventing access to detailed query metrics in active-passive environments. This issue is now resolved.
CDPD-124161: TLS hostname validation failure in Data Explorer
7.3.3.0
Previously, Impala connections in Data Explorer running on Python 3.12 failed TLS hostname validation when coordinator fully qualified domain names (FQDNs) exceeded 64 characters or when connections used HAProxy aliases. This issue occurred because hostname validation did not evaluate Subject Alternative Names (SAN) defined in valid certificates. This issue is resolved by updating hostname validation logic in Data Explorer to validate SAN entries on Python 3.12.
CDPD-123398: Gunicorn server log rotation failure in Data Explorer
7.3.3.0
Previously, rungunicornserver.log files in Data Explorer rotated prematurely at irregular file sizes well below the configured 4.8 MB threshold. This behavior caused overlapping timestamps and fragmented entries across rotated log files. This issue is resolved by improving log file handling across worker processes to ensure log files rotate at the configured file size threshold.
CDPD-101348: Data Explorer administration UI leads to incorrect URL
7.3.3.0
Previously, the Download logs button in the Data Explorer administration UI pointed to an incorrect or outdated URL, which prevented from downloading server logs. This issue is now resolved by updating the log download API endpoints.
CDPD-98406: Excessive Gunicorn debug log generation
7.3.3.0
Previously, Gunicorn log listeners generated debug-level records for access and metrics even when Data Explorer debug mode was disabled. This behavior caused unnecessary log clutter. This issue is now resolved by ensuring Gunicorn log output honors the Data Explorer debug mode setting.
CDPD-96460: Impala query profile row count display error
7.3.3.0
Previously, the Data Explorer Impala editor component displayed incorrect row count values for large tables because it incorrectly parsed the RowsReturned metric property from the EXCHANGE node component inside the Impala query profile log. This issue is fixed by implementing a threshold-based bucketing approach that displays approximate row count indicators, such as 1000+ rows or 10000+ rows, to prevent inaccurate query metadata displays.
CDPD-95948: Orphaned process detection failure in Data Explorer
7.3.3.0
Previously, process cleanup in Data Explorer incorrectly flagged active processes as orphaned, causing valid service processes to stop unexpectedly during cleanup routines. This issue is resolved by improving the detection logic to prevent false positives during process management cleanup.
CDPD-69906: Impala file import failure in Data Explorer
7.3.3.0
Previously, importing files into Impala by using Data Explorer failed on high-speed network connections. This issue occurred because rapid automated query progression stalled during sequential import operations, and result size requests were incorrectly triggered for data definition statements. This issue is resolved by improving query progression handling during automated imports and bypassing result size checks for statements without active query handles.
CDPD-125940: Storage Browser refresh failure in Data Explorer
Previously, refreshing Amazon S3 directories in the Data Explorer Storage Browser failed. This issue occurred because a name collision existed between the fs query parameter in the frontend and a parameter in the backend middleware. This issue is resolved by renaming the frontend query parameter from fs to tab.
CDPD-125833: Zero-byte file upload failure in Data Explorer
Previously, uploading zero-byte files to cloud storage by using the Storage Browser in Data Explorer failed with an XML error. This issue occurred because the upload process initiated multipart upload operations that Amazon S3 rejects when no parts are submitted. This issue is resolved by writing zero-byte files through a single put operation instead of a multipart upload, and removing the zero-byte file size check from the client-side.