.. _version_6.3.1:

=============
Version 6.3.1
=============

Released on 2026-04-14.

.. NOTE::

    If you are upgrading a cluster, you must be running CrateDB 5.0.0 or higher
    before you upgrade to 6.3.1.

    We recommend that you upgrade to the latest 6.2 release before moving to
    6.3.1.

    A rolling upgrade from >= 6.2.0 to 6.3.0 is supported.
    Before upgrading, you should `back up your data`_.

.. WARNING::

    Tables that were created before CrateDB 5.x will not function with 6.x
    and must be recreated before moving to 6.x.x.

    You can recreate tables using ``COPY TO`` and ``COPY FROM`` or by
    `inserting the data into a new table`_.

.. _back up your data: https://cratedb.com/docs/crate/reference/en/latest/admin/snapshots.html
.. _inserting the data into a new table: https://cratedb.com/docs/crate/reference/en/latest/admin/system-information.html#tables-need-to-be-recreated

.. rubric:: Table of contents

.. contents::
   :local:


See the :ref:`version_6.3.0` release notes for a full list of changes in the 6.3
series.

Fixes
=====

- Fixed an issue that caused :ref:`ALTER COLUMN
  <SQL-alter-table-alter-column-default>` to require super user permissions,
  instead of ``DDL`` privileges on the table.

- Fixed an issue that caused empty statements to require super user permissions.

- Fixed a regression introduced in 6.3.0 that prevented azure repositories to
  use the default ``endpoint`` if not set explicitly.

- Fixed an issue that caused a ``Function [...] is not a scalar function.``
  error if using a parameter placeholder as argument to an aggregation function
  used in the ``HAVING`` clause.

- Fixed an issue that caused tables created by
  :ref:`logical replication <administration-logical-replication>` subscriptions
  to not receive schema or data updates from a published table, if a publisher
  cluster's primary shards were active on polling the state and became
  inactive before restoring started (for example, due to shards relocation).
