Cloudera Docs

Known issues and limitations in Cloudera Data Visualization 8.0.3

Learn about the known issues and limitations that you might experience while using Cloudera Data Visualization. You can find information about the areas of impact, affected product versions, and possible workarounds.

Picklist in complex data types Show Selected unselects previous selections
Show selected in a filter list selection may not show all selections depending on the data type. A fix is expected in a future release.
Workaround
None
Versions affected
Cloudera Data Visualization 7.0.2 - 8.0.4
Fixed in version
N/A
Cloudera issue
VIZ-456
Inconsistent support for non-roman or character-based alphabets across visual types
Non-romanized or character-based alphabets are not consistently supported across various visual types. If not supported, the affected visual is not properly rendered in PDF/PNG downloads. CSV/Excel downloads and general dashboard viewing is available for all languages.

The following languages are not supported when using a table visual.

In Cloudera AI: In Cloudera Data Warehouse:
  • Amharic (Ethiopia)
  • Arabic (multiple countries)
  • Bengali (Bangladesh)
  • Berber (multiple countries)
  • Burmese (Myanmar)
  • Dari Pashto (Afghanistan)
  • Dzongkha (Bhutan)
  • Fijian (Fiji)
  • Georgian
  • Hebrew (Israel)
  • Khmer (Cambodia)
  • Lao
  • Malay (Brunei)
  • Many Indian languages
  • Nepalese (Nepal)
  • Persian (Iran)
  • Tamil (Malaysia, India, Singapore)
  • Thai (Thailand)
  • Urdu (Pakistan)
  • Amharic (Ethiopia)
  • Bengali (Bangladesh)
  • Burmese (Myanmar)
  • Dzongkha (Bhutan)
  • Fijian (Fiji)
  • Khmer (Cambodia)
  • Many Indian languages
  • Nepalese (Nepal)
  • Tamil (Malaysia, India, Singapore)
  • Thai (Thailand)
Workaround
None
Versions affected
Cloudera Data Visualization 7.0.2 - 8.0.4
Fixed in version
N/A
Cloudera issue
VIZ-984
Saved value does not show properly when arcapi is present
After the fix included for VIZ-1070, a known issue is still present when using arcapi.sendParameters with app-scope filters.
Workaround
None
Versions affected
Cloudera Data Visualization 7.0.2 - 8.0.4
Fixed in version
N/A
Cloudera issue
VIZ-1181
Selecting NULL values can cause ParseException syntax error from Cloudera Data Visualization 7.1.3
After upgrading to Cloudera Data Visualization 7.1.3 or later, selecting "NULL" values in filters may lead to a ParseException syntax error.
Workaround:
To resolve this issue, deselect the “NULL” value in the picklist filter.
Versions affected:
Cloudera Data Visualization 7.1.3 - 8.0.4
Fixed in version:
N/A
Cloudera issue:
VIZ-2224
Long-running queries cannot be canceled for some data connections

For data connections other than Hive or Impala, long-running queries cannot be canceled since they are run synchronously.

Workaround:

Restart the Cloudera Data Visualization application.

Versions affected:
All versions
Fixed in version:
N/A
Cloudera issue:
VIZ-2634
Data compatibility check does not work for SQL-based datasets that join on multiple tables

When importing in visual artifacts that use SQL-based datasets, the “data compatibility” check may fail with an “IndexError: list index out of range” error, if the dataset joins multiple tables.

Workaround:

Disable “Check data table compatibility” when importing in visual assets with complex queries.

Versions affected:
All versions
Fixed in version:
N/A
Cloudera issue:
VIZ-3121
AI visual cannot compute tokens when network is restricted

In air-gapped or network-restricted environments, the AI visual cannot estimate token usage because it requires access to https://openaipublic.blob.core.windows.net/encodings/cl100k_base.tiktoken.

Workaround:

Set the token limit to 0 in the visual settings and define the AI_MODEL_COMPLETION_TOKEN_LIMIT variable as 0 in the advanced site settings.

Versions affected:
Cloudera Data Visualization 8.0.3-8.0.4
Fixed in version:
N/A
Cloudera issue:
VIZ-3325
AI visual cannot compute tokens when network is restricted

In air-gapped or network-restricted environments, the AI visual cannot estimate token usage because it requires access to https://openaipublic.blob.core.windows.net/encodings/cl100k_base.tiktoken.

Workaround:

Set the token limit to 0 in the visual settings and define the AI_MODEL_COMPLETION_TOKEN_LIMIT variable as 0 in the advanced site settings.

Versions affected:
Cloudera Data Visualization 8.0.3-8.0.4
Fixed in version:
N/A
Cloudera issue:
VIZ-3325
Unnecessary replacements of datasets and cloned dashboards during import

When importing a cloned dashboard, it is always marked for replacement in the target system, even if no changes were made there. The same behavior occurs with datasets, which are also flagged as needing replacement regardless of actual changes.

Workaround:

For cloned dashboards, set the parent_report_id property to null in the exported JSON file.

For datasets, replace the version_name with the same version_name in the target system.

Versions affected:
Cloudera Data Visualization 6.3.0 and higher
Fixed in version:
Cloudera Data Visualization 8.0.4
Cloudera issue:
VIZ-3345, VIZ 3347
Query cancellation can exhaust thread pool resources

Canceling queries, either manually or by navigating away from a page, terminates the associated connection thread. Over time, this can deplete the thread pool, potentially leading to degraded performance or failed query execution. No indicators currently show how many threads have been consumed.

Workaround:

Restarting Cloudera Data Visualization or increasing the data connection concurrency limits resets the thread pool.

Also, a patch is available that can be applied using Advanced Site Settings, followed by restarting Cloudera Data Visualization. Contact Cloudera Support for assistance if needed.

Versions affected:
Cloudera Data Visualization 8.0.3
Fixed in version:
Cloudera Data Visualization 8.0.4
Cloudera issue:
VIZ-3349
Dashboard deletion may be slow after upgrading to Cloudera Data Visualization 8.0.2 and 8.0.3

You may experience delays (up to a minute) when deleting dashboards. After confirming deletion, the UI may appear unresponsive before completing the operation. This is caused by unoptimized query handling during the delete process.

Workaround:
None
Versions affected:
Cloudera Data Visualization 8.0.2-8.0.3
Fixed in version:
Cloudera Data Visualization 8.0.4
Cloudera issue:
VIZ-3359