This is an automated email from the ASF dual-hosted git repository.
yuqi1129 pushed a change to branch cherry-pick-8d6591d9-to-branch-1.3
in repository https://gitbox.apache.org/repos/asf/gravitino.git
omit 9737325f91 [#11946] improvement(api): Add properties field to
TableChange.AddIndex for custom index parameters (#12013)
add a67dee8d6a [#11912] feat(clickhouse): support set data skipping index
type (#11916)
add c7cd8eb0e2 [#11946] improvement(api): Add properties field to
TableChange.AddIndex for custom index parameters (#12013)
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (9737325f91)
\
N -- N -- N refs/heads/cherry-pick-8d6591d9-to-branch-1.3
(c7cd8eb0e2)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
.../org/apache/gravitino/rel/indexes/Index.java | 3 ++
.../catalog/clickhouse/ClickHouseConstants.java | 3 --
.../operations/ClickHouseTableOperations.java | 61 ++++++++++------------
.../test/CatalogClickHouseClusterIT.java | 18 +++++++
.../integration/test/CatalogClickHouseIT.java | 45 ++++++++++++++--
.../operations/TestClickHouseTableOperations.java | 17 +++---
docs/jdbc-clickhouse-catalog.md | 9 ----
7 files changed, 99 insertions(+), 57 deletions(-)
