<add title>

[sqxinquan]

Is there an existing issue for this?

• I have searched the existing issues

Description

The ​content rendering incompleteness bug in ​CDH6.3.2 and ​Hue4.4.0 can be translated as follows:
"Incomplete Content Rendering Bug in CDH6.3.2/Hue4.4.0"

Key Technical Context and Fixes:
​Frontend CSS/JavaScript Issues
The bug often manifests as truncated columns, missing UI elements (e.g., logs in Oozie workflows), or misaligned layout components. This is frequently caused by improper static resource loading (e.g., CSS files) or browser caching.
​Fix: Modify the Hue frontend code (e.g., adjust .resultTable CSS properties to enable horizontal scrolling) and redeploy static resources.
​Backend Configuration Errors
Incorrect HBase Thrift Server configurations or port conflicts (e.g., port 9090) may block data retrieval, leading to partial rendering. For example, Hue logs might show 500 Server Error when connecting to HBase.
​Fix: Verify Thrift Server status and update hbase.regionserver.thrift.http settings.
​Browser Compatibility and Caching
Browser-specific issues (e.g., Chrome/Firefox scaling) or stale cached files can disrupt rendering.
​Fix: Clear browser cache or use incognito mode. Adjust browser zoom to 100%.
References to Known Workarounds:
For Oozie workflow log display issues, modify the JavaScript logic in list_oozie_workflow_graph.mako to resolve action name parsing errors.
Adjust hue.ini parameters like max_result_rows to handle large datasets and prevent truncation.
This bug is a common issue in CDH6.3.2 environments and requires a combination of frontend adjustments, backend validations, and cache management to resolve fully.

Steps To Reproduce

The ​content rendering incompleteness bug in ​CDH6.3.2 and ​Hue4.4.0 can be translated as follows:
"Incomplete Content Rendering Bug in CDH6.3.2/Hue4.4.0"

Key Technical Context and Fixes:
​Frontend CSS/JavaScript Issues
The bug often manifests as truncated columns, missing UI elements (e.g., logs in Oozie workflows), or misaligned layout components. This is frequently caused by improper static resource loading (e.g., CSS files) or browser caching.
​Fix: Modify the Hue frontend code (e.g., adjust .resultTable CSS properties to enable horizontal scrolling) and redeploy static resources.
​Backend Configuration Errors
Incorrect HBase Thrift Server configurations or port conflicts (e.g., port 9090) may block data retrieval, leading to partial rendering. For example, Hue logs might show 500 Server Error when connecting to HBase.
​Fix: Verify Thrift Server status and update hbase.regionserver.thrift.http settings.
​Browser Compatibility and Caching
Browser-specific issues (e.g., Chrome/Firefox scaling) or stale cached files can disrupt rendering.
​Fix: Clear browser cache or use incognito mode. Adjust browser zoom to 100%.
References to Known Workarounds:
For Oozie workflow log display issues, modify the JavaScript logic in list_oozie_workflow_graph.mako to resolve action name parsing errors.
Adjust hue.ini parameters like max_result_rows to handle large datasets and prevent truncation.
This bug is a common issue in CDH6.3.2 environments and requires a combination of frontend adjustments, backend validations, and cache management to resolve fully.

Logs

No response

Hue version

4.4