Skip to content

[#11829] fix(doris): support replication allocation property#11877

Open
hutiefang76 wants to merge 1 commit into
apache:mainfrom
hutiefang76:codex/gravitino-11829-doris-replication-allocation
Open

[#11829] fix(doris): support replication allocation property#11877
hutiefang76 wants to merge 1 commit into
apache:mainfrom
hutiefang76:codex/gravitino-11829-doris-replication-allocation

Conversation

@hutiefang76

Copy link
Copy Markdown

What changed

This PR lets the JDBC Doris catalog accept the Doris 2.1+ replication_allocation table property.

It also keeps the existing single-BE fallback behavior for old-style replication_num, but skips that automatic replication_num=1 injection when the user has already provided replication_allocation. Doris treats those two properties as mutually exclusive, so adding both can make table creation fail.

Why

replication_allocation is valid Doris table syntax, but Gravitino did not register it in the Doris table property metadata. In single-backend environments, Gravitino could also add replication_num automatically, which conflicts with the user-supplied allocation policy.

Tests

JAVA_HOME=$(/usr/libexec/java_home -v 17) ./gradlew :catalogs:catalog-jdbc-doris:test --tests org.apache.gravitino.catalog.doris.TestDorisCatalog --tests org.apache.gravitino.catalog.doris.operation.TestDorisTableOperationsSqlGeneration -PskipITs
git diff --check

Closes #11829

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug report]jdbc-doris catalog does not support replication_allocation table property (Doris 2.1+ resource tag)

1 participant