Product updates

Get the latest updates on features, fixes and improvements.

RSS feed

729 results

  • Nov 18, 2024

    New

    Aiven for Apache Kafka® Connect

    Aiven for Apache Kafka Connect® now supports Debezium with mTLS for PostgreSQL

    Aiven for Apache Kafka Connect supports secure PostgreSQL integration using the Debezium connector with mutual TLS (mTLS). This connector, now generally available, enhances security through mutual authentication between the client and server.

    To learn more, see Integrate Apache Kafka Connect with PostgreSQL using Debezium and mutual TLS.

  • Nov 14, 2024

    Improved

    Aiven for PostgreSQL®

    TimescaleDB extension 2.17.2 for Aiven for PostgreSQL® released

    TimescaleDB extension version 2.17.2 is now available for Aiven for PostgreSQL®. It introduces bug fixes on top of release 2.17.1. Upgrade to 2.17.2 at your earliest convenience to make sure you use the most robust and secure version available.

    Refer to TimescaleDB release notes for all the changes introduced in this release.

    Bug fixes

    • #7384: Fix negative bitmapset member not allowed and performance degradation on queries to compressed tables with the ORDER BY clause matching the order of the compressed data
    • #7388: Use-after-free in vectorized grouping by segmentby columns

  • Nov 14, 2024

    New

    Aiven Terraform provider

    Autoscaler now supported in Aiven Provider for Terraform

    The autoscaler service integration is supported in version 4.29.0 of Aiven Provider for Terraform including the latest configuration options for services, integrations, and endpoints.

    Additionally, starting with this release, the changelog will now highlight every schema change. This should make it easier to track and understand the updates Aiven is delivering with the Terraform provider.

    For more information on Aiven Provider for Terraform, view the documentation.


  • Oct 31, 2024

    Improved

    Aiven CLI

    Aiven CLI version 4.4.0 now available

    A new minor version of the Aiven CLI has been released to support the following:

    • avn byoc tags list
    • avn byoc tags update --add-tag KEY=VALUE --remove-tag KEY
    • avn byoc tags replace --tag KEY=VALUE

    These tags are attached to BYOC environments and cascaded to bastion nodes in private deployment models.

    For more information, see Aiven CLI release notes.

  • Oct 30, 2024

    Improved

    Aiven for PostgreSQL®

    TimescaleDB extension 2.17.1 for Aiven for PostgreSQL® released

    TimescaleDB extension version 2.17.1 is now available for Aiven for PostgreSQL®. It introduces new features, performance improvements, and bug fixes on top of release 2.16.1. Upgrade to 2.17.1 at your earliest convenience to make sure you use the most robust and secure version available.

    Refer to TimescaleDB release notes for all the changes introduced in this release.

    Key new features

    • Full PostgreSQL 17 support for all existing features:
      TimescaleDB 2.17.1 is available for PostgreSQL 14, 15, 16, and 17.
    • Significant performance improvements for continuous aggregate policies:
      Continuous aggregate refresh is now using merge instead of deleting old materialized data and re-inserting. This update can decrease dramatically the amount of data that must be written on the continuous aggregate in the presence of a small number of changes, reduce the i/o cost of refreshing a continuous aggregate, and generate fewer Write-Ahead Logs (WAL). Overall, continuous aggregate policies will be more lightweight, use less system resources, and complete faster.
    • Increased performance for real-time analytical queries over compressed hypertables:
      Introducing additional Single Instruction, Multiple Data (SIMD) vectorization optimization to our engine by supporting vectorized execution for queries that group by using the segment_by column(s) and aggregate using the basic aggregate functions (sum, count, avg, min, max)
    • Improved performance of deletes on compressed hypertables when a large amount of data is affected:
      Speeding up operations that delete whole segments by skipping the decompression step (enabled for all deletes that filter by segment_by columns)

    PostgreSQL 14 deprecation announcement

    PostgreSQL 14 will be supported until April 2025. Closer to that time, there will be an announcement of the specific version of TimescaleDB in which PostgreSQL 14 support will not be included going forward.

    New features

    • #7360 Add chunk skipping GUC
    • #6882: Allow delete of full segments on compressed chunks without decompression.
    • #7033: Use merge statement on continuous aggregates refresh.
    • #7126: Add functions to show the compression information.
    • #7147: Vectorize partial aggregation for sum(int4) with grouping on segment by columns.
    • #7204: Track additional extensions in telemetry.
    • #7207: Refactor the decompress_batches_scan functions for easier maintenance.
    • #7209: Add a function to drop the osm chunk.
    • #7275: Add support for the returning clause for merge.
    • #7200: Vectorize common aggregate functions like min, max, sum, avg, stddev, variance for compressed columns of arithmetic types, when there is grouping on segment by columns or no grouping.

    Bug fixes

    • #7335 Change log level used in compression
    • #7342 Fix collation for in-memory tuple filtering
    • #7187: Fix the string literal length for the compressed_data_info function.
    • #7191: Fix creating default indexes on chunks when migrating the data.
    • #7195: Fix the segment by and order by checks when dropping a column from a compressed hypertable.
    • #7201: Use the generic extension description when building apt and rpm loader packages.
    • #7227: Add an index to the compression_chunk_size catalog table.
    • #7229: Fix the foreign key constraints where the index and the constraint column order are different.
    • #7230: Do not propagate the foreign key constraints to the osm chunk.
    • #7234: Release the cache after accessing the cache entry.
    • #7258: Force English in the pg_config command executed by cmake to avoid the unexpected building errors.
    • #7270: Fix the memory leak in compressed DML batch filtering.
    • #7286: Fix the index column check while searching for the index.
    • #7290: Add check for null offset for continuous aggregates built on top of continuous aggregates.
    • #7301: Make foreign key behavior for hypertables consistent.
    • #7318: Fix chunk skipping range filtering.
    • #7320: Set the license specific extension comment in the install script.

  • Oct 30, 2024

    Improved

    Aiven for OpenSearch®

    30-node plan no longer available for Aiven for OpenSearch®

    Premium-30x-* plans for Aiven for OpenSearch are no longer available in the Aiven Console. Existing 30-node plans remain unaffected. If your project currently or previously had a 30-node plan, you can still create new 30-node plans without consulting sales. Custom plans are not impacted.

    For further assistance, contact your Aiven sales team.

  • Oct 24, 2024

    Improved

    Aiven for Apache Kafka®

    Karapace version 4.0.0

    Karapace has been upgraded to version 4.0.0, bringing important updates and fixes.

    Key changes:

    • Systemd journal logging: Added support for logging to the systemd journal for easier log management.
    • Schema compatibility checks: Introduced a new messages field in the compatibility API, which provides more precise explanations of schema issues.

    To be enabled later:

    • Protobuf formatter: This release includes preparation for the Protobuf formatter, which will be available in a future update. It will provide more flexibility when handling Protobuf schemas.

    For more details, see the Karapace 4.0.0 release notes.

  • Oct 23, 2024

    Improved

    Aiven for Apache Kafka®

    Tiered storage in Aiven for Apache Kafka is now self-service

    You can now enable tiered storage in Aiven for Apache Kafka without needing to contact support.

    Key considerations:

    • Once enabled, tiered storage cannot be disabled.
    • Shutting down the service will result in permanent loss of data stored in tiered storage.
    • Tiered storage is available only on AWS, Google Cloud, and Microsoft Azure.

    For more information, see Get started with tiered storage and review the existing limitations for tiered storage.

  • Oct 17, 2024

    Improved

    Aiven for ClickHouse®

    Aiven for ClickHouse® upgraded to 24.3

    Aiven for ClickHouse® has been upgraded to version 24.3, which contains new features, improvements to existing functionalities, and a variety of fixes on top of the previous version:

    • New string similarity functions: arrayRandomSample, editDistance, dramerauLevenshteinDistance, jaroSimilarity, and more
    • Other new functions: arrayFold, groupArrayIntersect, largestTriangleThreeBuckets, seriesPeriodDetectFFT, and more
    • Space-filling curves (such as mortonEncode) can be used for primary key, which is useful if there are two separate expressions (rather than just one) that are often filtered by.
    • Automatic detection of a file format (for example, Parquet) for files with no extension
    • ALTER materialized_view MODIFY query
    • Support for NPY file format for better NumPy interoperability
    • GCD compression codec for integers
    • PASTE JOIN: create a table by joining all columns from a left subquery to all columns from a right subquery in the order of their respective rows
    • Vectorized functions cosineDistance, dotProduct, and L2Distance for better performance and additional ClickHouse vector database capabilities
    • Adaptive asynchronous INSERTs: adjust flush timeout based on frequency of INSERTSs
    • Performance improvements

    ClickHouse 24.3 brings changes to defaults of a few settings related to JSON, Parquet, ORC, and Arrow input/output formats:

    • input_format_json_try_infer_numbers_from_strings: true → false
    • output_format_parquet_string_as_string: false → true
    • output_format_arrow_string_as_string: false → true
    • output_format_orc_string_as_string: false → true

    If you’re using these settings, append a SETTINGS section to the end of queries while upgrading, for example:

    SELECT *
    FROM table
    FORMAT Parquet
    SETTINGS output_format_parquet_string_as_string=0;