This process applies exclusively to Citus clusters, which support the creation of distributed tables by defining a field as the distributionKey in a Data Source or Datamart. However, switching the distributionKey does not automatically convert the table within the database, as this process can be time-consuming. Instead, it is performed via a background job with a Job Scheduling Tool (JST), which may result in a temporary mismatch between the configuration layer (domain level) and the database layer. In such cases, a warning message is displayed.
The warning appears in the following scenarios:
-
If the
distributionKeyis configured but distribution is not supported in the database (this feature requires a fully configured Citus cluster in the application environment) the message displayed is:
Distributed tables not currently supported in this partition.
-
If the
distributionKeyconfigured in the Datamart does not match the current setup in the database, one of the following messages will be shown, depending on the specific case:
-
Table yet to be distributed in the database (due to setting distribution key to '%s') -
Table yet to be undistributed in the database (due to dropping distribution key '%s') -
Table yet to be re-distributed in the database (due to distribution key change from '%s' to '%s')