Skip to main content
Version: 2.14

Ververica Platform 2.13.0

Release Date: 2024-05-15

Changelog​

Ververica Platform 2.13.0 supports the following versions:

  • Apache Flink® 1.19
  • Apache Flink® 1.18
  • Apache Flink® 1.17

Ververica Platform 2.13.0 supports Apache Flink® 1.19, Apache Flink® 1.18, and Apache Flink® 1.17 under SLA.

For Stream Edition the following Apache Flink® Docker images are available. Please check Ververica Platform Docker Images for all available Apache Flink® images and additional tags.

  • 1.17.2-stream2-scala_2.12-java8
  • 1.17.2-stream2-scala_2.12-java11
  • 1.18.1-stream3-scala_2.12-java8
  • 1.18.1-stream3-scala_2.12-java11
  • 1.18.1-stream3-scala_2.12-java17
  • 1.19.0-stream1-scala_2.12-java8
  • 1.19.0-stream1-scala_2.12-java11
  • 1.19.0-stream1-scala_2.12-java17

For Spring Edition the following archives are available:

Additionally, the Apache Flink 1.16.3 has been patched to include the FLINK-34496 bug fix from Flink 1.19.0:

1.16.3-stream2-scala_2.12-java8 1.16.3-stream2-scala_2.12-java11 1.16.3-spring2-scala_2.12.tgz

See Flink 1.19.0 release.

New features​

New Oracle Catalog Added to Ververica Platform​

Ververica Platform now supports Oracle in Flink SQL's JDBC catalog. This new offering joins MySQL and Postgres catalogs, significantly enhancing the platform's data exploration capabilities.

The Oracle Catalog is provided as a pluggable user-defined Catalog. The jar is available in the portal (checksum). The Oracle Catalog supports the following options:

  • default-database: required, default database to connect to
  • username: required, Oracle account username
  • password: required, Oracle account password
  • base-url: required

The following example shows how to create an Oracle Catalog:

CREATE CATALOG TEST_CATALOG WITH(
    'type' = 'jdbc-oracle',
    'default-database' = '{your-database}',
    'username' = '{your-username}',
    'password' = '{your-password}',
    'base-url' = 'jdbc:oracle:thin:@{your-host}:{your-port}'
);
USE CATALOG TEST_CATALOG;

Oracle database has an additional namespace, schema (user), compared to Flink. The metaspace mapping between a Flink Catalog and Oracle is as follows:

Flink Catalog Metaspace StructureOracle Metaspace Structure
catalog nameN/A
database namedatabase name
table nameschema_name.table_name

Note that the schema_name is required. Below are some examples:

SELECT * FROM `TEST_SCHEMA.TEST_TABLE`;
SELECT * FROM `TEST_DB`.`TEST_SCHEMA.TEST_TABLE`;
SELECT * FROM `TEST_CATALOG`.`TEST_DB`.`TEST_SCHEMA.TEST_TABLE`;

Expanded SSL Configuration Support for Session Clusters in Ververica Platform​

Ververica Platform has expanded its SSL support to provide enhanced security for job and session clusters. With this update, users can configure SSL in three distinct ways:

  • Disable SSL: The default setting where HTTP is used for communication with the Session Cluster.
  • Enable SSL with auto-generated certificates: Ververica Platform automatically generates the necessary certificates for the Session Cluster and configures Flink SSL, securing internal and REST communications. Note that SSL for the blob service, which handles job dependency uploads, is currently disabled in this mode.
  • Enable SSL with custom certificates: This advanced option allows users to provide their own certificates and Flink SSL configuration, offering flexibility for specific security requirements.

This update not only enhances security but also offers greater flexibility and ease of SSL management across cluster types, ensuring compliance with enterprise security protocols. For more information on configuration, check out the Pluggable Certificates documentation and Session Cluster SSL/TLS.

info

SQL Editor Query Preview functionality currently does not support SSL. You can still use Query Preview in a Session Cluster with SSL disabled. Alternatively, you can mimic Query Preview functionality by creating an SQL deployment with SSL enabled and a print-sink connector acting as a sink.

Improvements​

Stream Audit Logs Directly to Kafka​

Ververica Platform now features enhanced audit log management, allowing direct streaming of audit logs to a specified Kafka topic. This new capability enables users to externalize audit logs without accessing them through the web UI or extracting them via the REST API. Users can now simplify log management and improve real-time monitoring and analysis by integrating audit log data into their existing Kafka environments.

This feature streamlines workflows, strengthens compliance and auditing processes, and makes audit log data more accessible and actionable. For a configuration example, go over to the Audit Logs with Kafka documentation.

Bug fixes​

Improved Dropdown Interaction in Ververica Platform​

We've improved the user interface interaction in Ververica Platform by resolving an issue with dropdown menus. Previously, dropdowns would stay open while scrolling, requiring users to click elsewhere to close them. Dropdowns will now automatically close when you scroll, providing a smoother and more intuitive user experience.

Invalid JSON Body with certain Default Deployment settings​

We've resolved a Ververica Platform version 2.12.3 issue where specific deployment default settings were misinterpreted, causing errors when editing newly created deployments. This fix ensures consistent and error-free deployment editing.

  • Updated org.apache.avro:avro to 1.11.3 to resolve vulnerability CVE-2024-39410
  • Updated swagger-dist-ui to 5.15.2 and DOMPurify to 3.1.0, to resolve vulnerability of Template Injection (CWE-1336)
  • Updated Nginx to 1.25.5 to resolve vulnerability CVE-2024-24990
  • Updated Spring Boot to 3.1.11 to resolve vulnerabilities CVE-2024-22259, CVE-2024-22243, CVE-2024-22257
  • Updated BouncyCastleJDK18 to 1.78.1 to resolve CVE-2023-33201
  • Updated pyarrow to resolve CVE-2023-47248
  • Updated pip up to 21.1 to resolve CVE-2023-5752, CVE-2021-3572

Upgrade​

As always, we recommend upgrading via Helm using the following commands:

$ helm repo add ververica https://charts.ververica.com
$ helm repo update
$ helm upgrade [RELEASE] ververica/ververica-platform --version 5.9.0 --values custom-values.yaml