Open
Conversation
…docs about catalogs in folder `catalogs-contrib` (apache#10065) (apache#10118) **Cherry-pick Information:** - Original commit: fcaded2 - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts) Co-authored-by: Qi Yu <yuqi@datastrato.com>
… version count assertions with semantic checks in TestFilesetMetaService and TestFunctionMetaService (apache#10137) (apache#10142) **Cherry-pick Information:** - Original commit: e928b2f - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts) Co-authored-by: mchades <liminghuang@datastrato.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…lude all Trino connector versions in distribution (apache#10144) (apache#10146) **Cherry-pick Information:** - Original commit: 0b978f2 - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts) Co-authored-by: Yuhui <hui@datastrato.com>
…s about Flink catalog name limitation (apache#10145) (apache#10152) **Cherry-pick Information:** - Original commit: ab28a7f - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts) Co-authored-by: roryqi <he@datastrato.com>
…etrics model and support read metrics from local file (apache#10138) (apache#10157) **Cherry-pick Information:** - Original commit: e69b663 - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts) Co-authored-by: FANNG <xiaojing@datastrato.com>
…apache#10045][apache#10048][apache#10056] fix and improve function related issue (apache#10114) (apache#10154) **Cherry-pick Information:** - Original commit: a89e394 - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts) Co-authored-by: Qian Xia <qian@datastrato.com>
… columns table for creating clickhouse provider (apache#10153) (apache#10184) **Cherry-pick Information:** - Original commit: 94c9f58 - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts) Co-authored-by: Qian Xia <qian@datastrato.com>
… table in TestCompactionStrategyHandler (apache#10120) (apache#10178) **Cherry-pick Information:** - Original commit: 47b42f7 - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts) Co-authored-by: Roman Horilyi <gorilyiroman@gmail.com> Co-authored-by: Roman Horilyi <rhorilyi@pinterest.com>
…d `maxStatisticsPerUpdate` configuration for Lance partition storage (apache#10149) (apache#10159) **Cherry-pick Information:** - Original commit: 615568a - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts) Co-authored-by: roryqi <he@datastrato.com>
…zer client (apache#10110) (apache#10185) **Cherry-pick Information:** - Original commit: e140398 - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts) Co-authored-by: FANNG <xiaojing@datastrato.com>
…prove recommender log messaging (apache#10121) (apache#10192) **Cherry-pick Information:** - Original commit: fc6e11e - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts) Co-authored-by: Roman Horilyi <gorilyiroman@gmail.com> Co-authored-by: Roman Horilyi <rhorilyi@pinterest.com>
…ally run CI for auto-cherry-pick PRs (apache#10211) (apache#10228) **Cherry-pick Information:** - Original commit: 01e75cb - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts)
… clearing column comments in table updates (apache#9694) (apache#9881) (apache#10205) **Cherry-pick Information:** - Original commit: 6827ca1 - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts) Co-authored-by: Tanay Paul <145260122+paultanay@users.noreply.github.com>
…ize the catalog wrapper and entity cache expiry strategy (apache#10180) (apache#10207) **Cherry-pick Information:** - Original commit: dfec1b6 - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts) Co-authored-by: roryqi <he@datastrato.com>
…hange log for version 1.2.0 (apache#10197) (apache#10227) **Cherry-pick Information:** - Original commit: b863b95 - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts) Co-authored-by: Yuhui <hui@datastrato.com>
…talog): fix creating distribute table error. (apache#10088) (apache#10231) **Cherry-pick Information:** - Original commit: 38c2115 - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts) Co-authored-by: Yuhui <hui@datastrato.com>
…d the version segment module to support Trino 473-478 (apache#10188) (apache#10208) **Cherry-pick Information:** - Original commit: acb38a1 - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts) Co-authored-by: Yuhui <hui@datastrato.com> Co-authored-by: qbhan <qbhan@lilith.com>
…izer integration tests (apache#10191) (apache#10236) **Cherry-pick Information:** - Original commit: 004d514 - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts) Co-authored-by: FANNG <xiaojing@datastrato.com>
…port TableWritePrivilege for Spark 3.5+ authorization (apache#10194) (apache#10237) **Cherry-pick Information:** - Original commit: 2f8c329 - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts) Co-authored-by: roryqi <he@datastrato.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
…ersion requirements in build and usage documentation (apache#10179) (apache#10239) **Cherry-pick Information:** - Original commit: 5d8946a - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts)
…nterfaces `register table` and `register view` (apache#10241) (apache#10245) **Cherry-pick Information:** - Original commit: d237143 - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts) Co-authored-by: roryqi <he@datastrato.com>
… (cherry-pick) (apache#10202) ### What changes were proposed in this pull request? This pull request makes significant improvements to the GitHub Actions workflows for integration and build testing. The main changes focus on more efficient test execution, better detection of changed modules, and consistent naming and exclusion logic across workflows. The updates help optimize CI resource usage and improve maintainability. ### Why are the changes needed? For better development Fix: apache#10155 ### Does this PR introduce _any_ user-facing change? N/A ### How was this patch tested? CI
…ouldn't contain the test jar (apache#10386) (apache#10418) **Cherry-pick Information:** - Original commit: db40dc6 - Target branch: `branch-1.2` - Status:⚠️ **Has conflicts - manual resolution required** Please review and resolve the conflicts before merging. Co-authored-by: roryqi <he@datastrato.com>
…ry change (apache#10288) (apache#10438) **Cherry-pick Information:** - Original commit: 891ab2d - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts) --------- Co-authored-by: roryqi <he@datastrato.com>
… to updaters (apache#10456) (apache#10461) **Cherry-pick Information:** - Original commit: e875274 - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts) Co-authored-by: FANNG <xiaojing@datastrato.com>
…ries missing version-info JOIN and field aliases (apache#10451) (apache#10460) **Cherry-pick Information:** - Original commit: 421b43d - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts) Co-authored-by: Jerry Shao <jerryshao@datastrato.com>
…ook exception when rollback fails (apache#10293) (apache#10468) **Cherry-pick Information:** - Original commit: 6315603 - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts) Co-authored-by: pythaac <86088023+pythaac@users.noreply.github.com> Co-authored-by: Qi Yu <yuqi@datastrato.com>
…ease task and centralize JDK8 compatibility (apache#10485) ### What changes were proposed in this pull request? This PR backports apache#10385 to `branch-1.2`. The backport removes the Gradle `release` task usage from the CI/release flow and centralizes the JDK8 compatibility logic in the root build script, instead of keeping scattered module-local handling. ### Why are the changes needed? `branch-1.2` still carries the same build/release-task coupling and JDK8 compatibility fragmentation fixed in main. Backporting this change keeps the branch behavior aligned and avoids relying on the removed release task path. Fix: apache#10262 ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Verified by compiling the directly affected modules: ```bash ./gradlew :clients:client-java:compileJava :flink-connector:flink:compileJava :spark-connector:spark-common:compileJava --console=plain ```
…se-catalog): Fix ClickHouse alter-table bugs (apache#10383) (apache#10487) **Cherry-pick Information:** - Original commit: 8afb307 - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts) Co-authored-by: Qi Yu <yuqi@datastrato.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…verified JDBC compatibility matrix (apache#10463) (apache#10491) **Cherry-pick Information:** - Original commit: 9377ca2 - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts) Co-authored-by: Qi Yu <yuqi@datastrato.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
… batch get owner (apache#9914) (apache#10489) **Cherry-pick Information:** - Original commit: 20e2ae1 - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts) Co-authored-by: yangyang zhong <35210666+hdygxsj@users.noreply.github.com> Co-authored-by: Rory <he@datastrato.com>
…ions): include partition path parameter in getPartition error handling (apache#10388) (apache#10483) **Cherry-pick Information:** - Original commit: 5a3c595 - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts) Co-authored-by: Sambhavi Pandey <48976443+pandeysambhi@users.noreply.github.com>
… multi-version integration test automation (apache#10455) (apache#10505) **Cherry-pick Information:** - Original commit: d7ca344 - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts)
…10504)(cherry-pick-to-1.2) (apache#10506) ### What changes were proposed in this pull request? Pin all `docker/*` GitHub Actions to their exact commit SHA (v4.0.0) in every CI workflow file, as required by the Apache GitHub organization policy. The Apache allowlist at https://github.com/apache/infrastructure-actions/blob/main/actions.yml requires SHA-pinned references, not floating tags like `@v3` or `@v3.6.0`. Updated SHAs (from the Apache allowlist): | Action | SHA | Tag | |--------|-----|-----| | `docker/setup-qemu-action` | `ce360397dd3f832beb865e1373c09c0e9f86d70a` | v4.0.0 | | `docker/login-action` | `b45d80f862d83dbcd57f89517bcf500b2ab88fb2` | v4.0.0 | | `docker/setup-buildx-action` | `4d04d5d9486b7bd6fa91e7baf45bbb4f8b9deedd` | v4.0.0 | Affected files (10): - `.github/workflows/access-control-integration-test.yml` - `.github/workflows/python-integration-test.yml` - `.github/workflows/trino-integration-test.yml` - `.github/workflows/backend-integration-test-action.yml` - `.github/workflows/cron-integration-test.yml` - `.github/workflows/gvfs-fuse-build-test.yml` - `.github/workflows/flink-integration-test-action.yml` - `.github/workflows/spark-integration-test-action.yml` - `.github/workflows/frontend-integration-test.yml` - `.github/workflows/docker-image.yml` ### Why are the changes needed? Fix apache#10502 The Apache GitHub organization policy requires actions to be referenced by their exact commit SHA. Using floating tags (`@v3`, `@v3.6.0`) causes all CI runs to fail with: > The action docker/setup-qemu-action@v3.6.0 is not allowed in apache/gravitino because all actions must be from a repository owned by your enterprise, created by GitHub, or match one of the patterns ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? CI-only change; no logic modified. Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
… docker image version to 4.14.0 to fix CI problem (apache#10528) (apache#10530) **Cherry-pick Information:** - Original commit: bbb14ad - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts) Co-authored-by: Qi Yu <yuqi@datastrato.com>
…up redundant code in GravitinoLanceTableOperations#createTable (apache#10497) (apache#10533) **Cherry-pick Information:** - Original commit: 837e2b1 - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts) Co-authored-by: Yuw1 <imwangyu@126.com> Co-authored-by: Qi Yu <yuqi@datastrato.com>
…use-paimon): exclude unnecessary tomcat transitive dependency (apache#10526) (apache#10540) **Cherry-pick Information:** - Original commit: 1d9bebb - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts) Co-authored-by: geyanggang <geyanggang@qq.com>
…ckage size of Hive Metastore 2 and 3 catalogs (apache#10465) (apache#10544) **Cherry-pick Information:** - Original commit: 74e9881 - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts) Co-authored-by: Yuhui <hui@datastrato.com>
… to pod spec in deployment.yaml (apache#10573) (apache#10582) **Cherry-pick Information:** - Original commit: 47a005d - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts) Co-authored-by: Bharath Krishna <bmurali@roku.com>
…itino.sh instead of gravitino.sh to launch the service (apache#10583) (apache#10654) **Cherry-pick Information:** - Original commit: c55ad35 - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts) Co-authored-by: Danhua Wang <danhua@datastrato.com>
…te N+1 queries in metadata object (apache#10589) (apache#10655) **Cherry-pick Information:** - Original commit: 2b31bb2 - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts) Co-authored-by: Babu Mahesh <prbabumahesh@gmail.com> Co-authored-by: Babu Mahesh <babu.mahesh@acceldata.io>
…x from config endpoint per Iceberg REST spec (apache#10652) (apache#10666) **Cherry-pick Information:** - Original commit: 706e40c - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts) Co-authored-by: akshay thorat <ak007t@gmail.com>
…error body instead of HTML for pre-JAX-RS errors (apache#10668) (apache#10679) **Cherry-pick Information:** - Original commit: 922009a - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts) Co-authored-by: akshay thorat <ak007t@gmail.com>
… cascade owner relation cleanup for schema and catalog deletion (apache#10678) (apache#10680) **Cherry-pick Information:** - Original commit: 04f5dda - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts) Co-authored-by: Sachin Ranjalkar <52783123+sachinnn99@users.noreply.github.com>
… from 4 to 7 (apache#10646) (apache#10703) **Cherry-pick Information:** - Original commit: 96be23c - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
("metalakeId") to GroupRoleRelMapper.softDeleteGroupRoleRelByMetalakeId (apache#10664) (apache#10702) **Cherry-pick Information:** - Original commit: a7914c9 - Target branch: `branch-1.2` - Status: ✅ Clean cherry-pick (no conflicts) Co-authored-by: Sachin Ranjalkar <52783123+sachinnn99@users.noreply.github.com>
Author
|
is it need to issue a PR to branch-1.2.0, not to main branch? @roryqi |
Contributor
You should raise a pull request to main branch first. Branch 1.2 shouldn't merge new feature. So I am sorry that this feature may not be merged to branch 1.2. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
add the grant_type=password, to support the new feature, from: #10749