Review the list of Streaming Analytics behavioral changes in Cloudera DataFlow for Data
Hub 7.3.1.
SQL Stream Builder
- Summary:
- CSA-4046 - Use KNOX for SSB as Load-Balancer
- Previous behavior:
- New behavior:
- Summary:
- CSA-5068 - Page refresh is not required to update result samples.
- Previous behavior:
- Sample ids could become invalid if another user restarted the job while polling in the UI.
- New behavior:
- Sample ids are updated before and during polling.
- Summary:
- CSA-5238 - Yarn is set as default token renewer automatically based on configuration.
- Previous behavior:
- Configuration check wasn't performed and yarn wasn't set as the default renewer.
- New behavior:
- Yarn is set as the default token renewer if the deployment target is
yarn-session or yarn-per-job.
- Summary:
- CSA-5258 - Extended validation for dynamic MV parameter names.
- Previous behavior:
- Dynamic pattern validation was restrictive which could result in errors when querying MV.
- New behavior:
- Validation pattern is extended to
[A-Za-z\_\-0-9\.\~]+
- Summary:
- CSA-5214 - Add option to SSB service to customize default truststore
- Previous behavior:
- Default Kafka TrustStore configurations could only be customized in Flink configurations.
- New behavior:
- Customizing default Kafka TrustStore configurations was added to Streaming SQL Console. Kafka TrustStore can be configured during adding Kafka as a Data Source on the UI.
- Summary:
- CSA-5199 - API change: the Cloudera registry catalog type
registry is now named cloudera-registry
- Previous behavior:
- When creating a Schema Registry data source catalog type property had to be
registry
- New behavior:
- Catalog type property now has to be
cloudera-registry when creating a Schema Registry data source, but registry is backward compatible.
- Summary:
- CSA-5306 - SSB API does not validate data sources before saving
- Previous behavior:
- There was no validation before saving a data source via API. If the user wanted to make sure to save a valid data source they had to use the validate endpoint before saving. When creating a data source on SSB UI, the user had the option to save an invalid data source.
- New behavior:
- Saving the data source is only allowed if the data source is valid. SSB API validates the data source before saving and on the SSB UI Create/Save button is only active if the validation is successful.
