Closed
Conversation
Contributor
Author
|
cc @snazy , @adnanhemani |
Contributor
Author
|
@snazy or @adnanhemani please can one of you have a look when you have time? |
snazy
reviewed
Jan 26, 2026
CHANGELOG.md
Outdated
| - The EclipseLink Persistence implementation has been completely removed. | ||
| - The default request ID header name has changed from `Polaris-Request-Id` to `X-Request-ID`. | ||
| - The (Before/After)CommitTableEvent has been removed. | ||
| - The (Before/After)CommitViewEvent has been removed. |
Member
There was a problem hiding this comment.
This needs to go into the "unreleased" part of CHANGELOG.
…e docker tag to v1.24-1 (apache#3297)
To prevent duplicate version-bump PRs like apache#3299 and apache#3300
* Ensure release publish workflow can only run from last RC (apache#3290) * Enable use of second release workflow for RC>0 * Patch 3rd workflow to support commits with multiple RC tags * Force 4th workflow to only run from a release branch * Update release guide to match new workflows
…e docker tag to v1.24-2 (apache#3313)
* Fix openapi-generator-cli version in build system * Fix openapi-generator-cli version in build system
This is a safety net in case Properties are generated anywhere during the build.
Add error detection and validation to API calls in the quickstart docker-compose setup with clear error messages for easier debugging.
This commit fixes apache#3080
…e#3511) * Add doc for couple new feature flags * Add doc for couple new feature flags
* Fading anchor * Fading anchor
…MS permission for RO/RW (apache#3493)
The `site.yml` workflow is currently triggered in the following scenarios: 1. A push to the `main` branch, using the state of the site and the workflow as on `main`. 2. A push to a `release/*`branch, using the state of the site and the workflow as on that release branch. Notice that workflows get the repo state (from the checkout actions) and the workflow state as its on that particular branch. Put in other words: if we'd have a change to some old `release/1.0.x` branch, the web site would be updated as it is defined on that `release/1.0.x` branch, which is wrong and not the intended behavior. This change updates the workflow triggers to only run for pushes to the `main` branch, plus PRs against the `main` branch and when called from another workflow. This is part of apache#3516
The script `site/bin/checkout-releases.sh` is a convenience to get the `versioned-docs` branch locally. It is missing a `git pull` to get the latest state of that branch though, which can be confusing.
The Iceberg PR apache/iceberg#14991 bumps the https://github.com/RoaringBitmap/RoaringBitmap version, which is not published to Maven Central. We need to declare in the jitpack.io repository to prepare for the next Iceberg release.
…n.idea-ext:gradle-idea-ext to v1.4 (apache#3549)
…apache#3507) Addresses the issues discussed on the dev mailing-list discussion https://lists.apache.org/thread/gkyw7m4fcbjbzhcrlrp4kcq5lr05r0m4, opting to use Guava as the easiest replacement here.
Contributor
Author
|
messed up the rebase flow will create a new PR |
github-project-automation
bot
moved this from PRs In Progress
to Done
in Basic Kanban Board
6 tasks
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
20 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.
This PR addresses issue #3418 after this PR recently did the same for tables.
Given that the current implementation of commitTransaction works only for table (from my reading, please correct if I am wrong), I concluded only removing events would be enough especially since *ReplaceView is already supported.
Tests:
Ran integration tests.
Checklist
CHANGELOG.md(if needed)site/content/in-dev/unreleased(if needed)