Known issues and limitations
Learn about the known issues in Flink and SQL Stream Builder, the impact or changes to the functionality, and the workaround in Cloudera Streaming Analytics 1.8.0.
SQL Stream Builder
- Auto discovery is not supported for Apache Knox
- You need to manually configure Knox with SQL Stream Builder to enable Knox authentication.
- Complete the configuration based on the CDP Private Cloud Base version you use. For more information, see the Enabling Knox authentication for SSB documentation.
- Streaming SQL Console cannot be accessed through Knox when High Availability is enabled
- When SQL Stream Builder SSB is deployed in High Availability with Load Balancer, the Streaming SQL Console cannot be accessed directly using Apache Knox.
- For accesing Streaming SQL Console, use the secured Load Balancer deployment or authenticate using SPNEGO.
- SSB service fails when using Active Directory (AD) Kerberos authentication
- If you use AD Kerberos for authentication and the Load Balancer URL is not provided, it can cause the SQL Stream Builder (SSB) service to fail. The issue is caused by the keytab generation. When the keytab is generated by Cloudera Manager it requires the principals from the AD for the Load Balancer host, and without no host specified for the Load Balancer, the SSB service cannot be started by Cloudera Manager. This issue also persists when the Load Balancer role is not deployed or used with SSB.
- Fill out the Load Balancer URL parameter in Cloudera Manager regardless of using Load Balancer with SSB. For more information, see the Enabling High Availability for SSB documentation.
- CSA-2016: Deleting table from other teams
- There is a limitation when using the Streaming SQL Console for deleting tables. It is not possible to delete a table that belongs to another team using the Delete button on the User Interface.
DROP TABLEstatement from the SQL window.
- CSA-1454: Timezone settings can cause unexpected behavior in Kafka tables
- You must consider the timezone settings of your environment when
using timestamps in a Kafka table as it can affect the results of your query. When the
timestamp in a query is identified with
from_unixtime, it returns the results based on the timezone of the system. If the timezone is not set in UTC+0, the timestamp of the query results will shift in time and will not be correct.
- Change your local timezone settings to UTC+0.
- CSA-1231: Big numbers are incorrectly represented on the Streaming SQL Console UI
- The issue impacts the following scenarios in Streaming SQL
- When having integers bigger than 253-1 among your values, the Input transformations and User Defined Functions are considered unsafe and produce incorrect results as these numbers will lose precision during parsing.
- When having integers bigger than 253-1 among your values, sampling to the Streaming SQL Console UI produces incorrect results as these numbers will lose precision during parsing.
In Cloudera Streaming Analytics, the following SQL API features are in preview:
- Match recognize
- Stream-Table join (without rowtime input)
- DataStream conversion limitations
- Converting between Tables and POJO DataStreams is currently not supported in CSA.
- Object arrays are not supported for Tuple conversion.
java.timeclass conversions for Tuple DataStreams are only supported by using explicit
java.sql.Timestampis supported for rowtime conversion,
java.time.LocalDateTimeis not supported.
- Kudu catalog limitations
- Primary keys can only be set by the
kudu.primary-key-columnsproperty. Using the
PRIMARY KEYconstraint is not yet possible.
- Range partitioning is not supported.
- Primary keys can only be set by the
- When getting a table through the catalog,
PRIMARY KEYconstraints are ignored. All columns are described as being nullable, and not being primary keys.
- Kudu tables cannot be altered through the catalog other than simply renaming them.
- Schema Registry catalog limitations
- Currently, the Schema Registry catalog / format only supports reading messages with the latest enabled schema for any given Kafka topic at the time when the SQL query was compiled.
- No time-column and watermark support for Registry tables.
CREATE TABLEsupport. Schemas have to be registered directly in the
SchemaRegistryto be accessible through the catalog.
- The catalog is read-only. It does not support table deletions or modifications.
- By default, it is assumed that Kafka message values contain the schema id as a
prefix, because this is the default behaviour for the
SchemaRegistryKafka producer format. To consume messages with schema written in the header, the following property must be set for the Registry client: