Known issues and limitations in Data Visualization 7.0.1
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.
- CANCEL button on Edit User or New User modal needs to be clicked twice
- Clicking the CANCEL button in the Edit User or New User modals may display an unexpected validation error instead of closing the modal.
- Workaround:
- The error can be bypassed by clicking CANCEL a second time.
- Versions affected:
- Cloudera Data Visualization 7.0.0 - 7.0.1
- Fixed in version:
- Cloudera Data Visualization 7.0.2
- Cloudera issue:
- VIZ-829
- Filtering for null values does not work
- It is possible to create filters for fields whose set contains
NULL
values. However, it is not possible to display only the rows that haveNULL
for the filtered field value. - Workaround
- None
- Versions affected
- Cloudera Data Visualization 7.0.1 - 7.0.2
- Fixed in version
- 7.0.3
- Cloudera issue
- VIZ-1452
- Disable CDW warehouse input if there are no options
- In CDW, if there are no associated data warehouses in the same workspace, the dropdown appears, but remains empty. It will be disabled in future.
- Workaround
- None
- Versions affected
- Cloudera Data Visualization 7.0.1 - 7.0.4
- Fixed in version
- 7.0.5
- Cloudera issue
- VIZ-1454
- Upgrade snowflake-connector-python when the corresponding issue is fixed
- For some characters, snowflake queries return "Failed to convert current row, cause: 'utf-8' codec can't decode byte" error (SNOW-182387: UTF-8 decoding exception when querying table in SNOWFLAKE_SAMPLE_DATA).
- Workaround
- None
- Versions affected
- Cloudera Data Visualization 7.0.0 - 7.2.9
- Fixed in version
- Cloudera Data Visualization 7.2.2
- Cloudera issue
- VIZ-1455
- Console errors when queries are automatically cancelled
- Cancelled queries may result in intermittent dashboard errors or console errors unexpectedly.
- Workaround:
- None
- Versions affected:
- Cloudera Data Visualization 7.0.0 - 7.0.5
- Fixed in version:
- Cloudera Data Visualization 7.1.0
- Cloudera issue:
- VIZ-1457
- Email fails with error
- TLS and SSL can both be enabled even if they are mutually exclusive. This results in an error and sending the email fails.
- Workaround:
- None
- Versions affected:
- Cloudera Data Visualization 7.0.1
- Fixed in version:
- Cloudera Data Visualization 7.0.2
- Cloudera issue:
- VIZ-1486
- Custom background color assignment on dimensions or measures not possible
- Cannot fix colors for specific dimension values or numeric ranges when adding background colors to tables or crosstabs.
- Workaround:
- To resolve this issue, add such basic custom styles into the application.
- Versions affected:
- Cloudera Data Visualization 7.0.0 - 7.0.3
- Fixed in version:
- 7.0.4
- Cloudera issue:
- VIZ-1580 & VIZ-1060
- Trigger Jobs fail with "name 'username' is not defined" NameError
- Workaround:
- None
- Versions affected:
- Cloudera Data Visualization 7.0.1 - 7.0.4
- Fixed in version:
- 7.0.4-b41
- Cloudera issue:
- VIZ-1742
- Emailing jobs fail when SSL and TLS errors are disabled
- Workaround:
- To resolve this issue, switch to an email server that supports TLS or SSL.
- Versions affected:
- Cloudera Data Visualization 7.0.1 - 7.0.4
- Fixed in version:
- 7.0.4-b41
- Cloudera issue:
- VIZ-1743
- Histogram visual fails with an execution error “e.map is not a function”
- Workaround:
- N/A
- Versions affected:
- Cloudera Data Visualization 6.2.6 - 7.1.4
- Fixed in version:
- Cloudera Data Visualization 7.1.4-b74
- Cloudera issue:
- VIZ-2058
- Partitioned Cloudera Impala on premise extract tables cannot be updated
-
Tables in Cloudera Impala that are both partitioned and set as extract targets cannot be updated directly. This prevents operations such as dropping or adding new partitions.
- Workaround:
-
Move the data to a new table that supports altering commands. Then replace the original extract table by renaming the newly created table. Optionally, you can create a backup of the original table before replacing it.
A sample SQL workflow is provided below. Customize the components marked in blue, while the remaining parts of the query are standard.
-
Create a temporary table (
database_name.new_table_name
) that supports altering.create table database_name.cdv_table_name_new (table_definition) partitioned by (partition_field string) tblproperties('transactional'='false');
-
Copy existing data from the original extract target.
insert into database_name.cdv_table_name_new partition(partition_field) select * from database_name.cdv_table_name;
-
[Optional] Save the original extract target as a backup.
alter table database_name.cdv_table_name rename to database_name.cdv_table_name_bak;
-
Make the temporary table the current extract target.
alter table database_name.cdv_table_name_new rename to database_name.cdv_table_name;
-
- Versions affected:
- Cloudera Data Visualization 7.2.8 and all earlier versions
- Fixed in version:
- Cloudera Data Visualization 7.2.9
- Cloudera issue:
- VIZ-3042