Skip to main content
VeloDB Cloud 4.x·Apache Doris 3.x·"Since X.Y" tags refer to Doris versionsversion mapping →

v4.1

This article describes the release notes for VeloDB Core v4.1.

Note VeloDB Core v4.1 was developed based on Apache Doris v3.1 .

v4.1.7 (May 21, 2026)​

This release incorporates Apache Doris v3.1.6 along with VeloDB-specific enhancements.

New Features

  • Added the mmh64_v2 hash function.
  • Added the ability to view the compute group used by a routine load job.

Improvements

  • Reduced memory usage during data loading and large queries.
  • Improved the performance of large table scans.
  • Allowed Variant columns to use light schema change, speeding up ALTER TABLE operations.

Bug Fixes

  • Fixed incorrect column parsing when loading CSV files that both use an enclosure character and begin with a UTF-8 byte order mark (BOM). You are affected if you load such CSV files.
  • Fixed the date_format function dropping microseconds for datetimev2 values. You are affected if you format datetime values that carry sub-second precision.
  • Fixed the json_extract_string function returning an incorrect result in some cases. You are affected if you use json_extract_string to read string values from JSON.
  • Fixed a missing predicate filter that could return extra rows when a single scan of an external file table used both native and JNI readers, for example a Hive or Iceberg table whose columns are read by different reader types.
  • Fixed ALTER VIEW not propagating the new definition to follower frontends when the statement included a comment, which left followers serving the old view. You are affected only in multi-frontend deployments.
  • Fixed RESTORE not preserving cross-database references when restoring views that reference tables in another database.
  • Fixed a crash in set operations (UNION, INTERSECT, EXCEPT) when the combined data exceeded 4 GB.
  • Fixed a crash in the ORC reader when predicate pushdown was applied while reading ORC files, for example external Hive or Iceberg tables.

v4.1.6 (April 30, 2026)​

This is a maintenance release with internal stability and performance improvements. No user-facing changes.

v4.1.5 (April 15, 2026)​

Improvements

  • Improved read performance after cluster scaling or failover, so newly added compute resources can serve cached data sooner.
  • Improved the performance of queries that sort large result sets.

v4.1.4 (March 27, 2026)​

This release incorporates Apache Doris v3.1.5 along with VeloDB-specific enhancements.

New Features

  • Added custom analyzer support for full-text search, including a pinyin tokenizer and filter.
  • Added support for 45-minute time zone offsets.
  • Extended Paimon catalog support, including the REST catalog and additional partition data types.
  • Added support for writing compressed CSV files with column names and types in SELECT INTO OUTFILE.

Improvements

  • Improved the performance of queries that sort data or that run large joins and aggregations.
  • Raised the default maximum number of Variant subcolumns to 2048.
  • Improved storage and compaction efficiency for wide tables with many sparse columns.

Bug Fixes

  • Fixed INSERT OVERWRITE failing on an auto-partitioned table when the cluster was rebalancing tablets at the same time.
  • Fixed INSERT OVERWRITE raising an error when it targeted partitions that had already been deleted.
  • Fixed the disable_auto_compaction table property being ignored in cloud mode. You are affected if you set this property on a table.
  • Fixed routine load jobs being incorrectly cancelled after a frontend restart that followed a table swap (REPLACE).
  • Fixed queries not being automatically retried after a backend restarted, for example during an upgrade or a scaling operation.
  • Fixed an INSERT failing when a schema change ran on the same table at the same time.
  • Fixed primary-key point queries ignoring the session time zone for time functions such as from_unixtime.
  • Fixed JDBC catalog issues, including incorrect NULL detection for PostgreSQL arrays and date predicate pushdown for SQL Server. You are affected if you query PostgreSQL or SQL Server through a JDBC catalog.
  • Fixed a crash when casting a string to a STRUCT where the string contained more fields than the struct.
  • Fixed a crash in the substring_index function on certain arguments.
  • Fixed DELETE incorrectly requiring the LOAD privilege on a table referenced only in a subquery, such as a NOT EXISTS clause, which could block users who had the correct SELECT privilege.
  • Fixed several cases that could return incorrect results: set operations (UNION, INTERSECT, EXCEPT), queries with a filter pushed through a UNION that contains constant expressions, and aggregation over a primary-key to foreign-key join.

v4.1.3 (February 12, 2026)​

Improvements

v4.1.2 (January 7, 2026)​

Improvements

  • Optimized the processing logic of view creation in special scenarios to improve the SQL user experience.
  • Optimized the temporary resource management mechanism to enhance the long - term operational stability of the system.
  • Optimized the cache capacity management strategy to improve resource utilization efficiency.
  • Optimized the execution performance and stability of Routine Load in update scenarios.
  • Optimized the transaction recycling process to strengthen the system's robustness.
  • Added monitoring metrics related to transaction writing to enhance observability capabilities.
  • Optimized the task scheduling and resource recycling efficiency in cloud environments.

v4.1.1 (December 10, 2025)​

Improvements

v4.1.0 (October 17, 2025)​

Improvements