Re: Polaris Community Sync on Events

First of all, sorry all for the misformating in my previous email - seems my mail client wasn’t playing well with the Apache mail server. > Adding that there's been consensus in the meeting to start with a pure Java > interface and go from there. I’m not sure what this means - can you expand on

Discussion Regarding Events Instrumentation - GH PR #1904

Hi all, As per the comment on GitHub PR #1904 , I am opening this mailing thread to discuss the PR implementation. This PR is only adding instrumentation for additional events in `PolarisServiceImpl.java`. There is no additional business logic as pa

Re: [DISCUSS] Prepare for 1.0 Release

The rename commits( https://github.com/apache/polaris/commit/ab228afa4d975faabb7aaf1e8abb0804f5b9d353 and https://github.com/apache/polaris/commit/fccc51ab111b7ee1a0d3c8898e94b0c54bc73d80) have been cherry-picked to 1.0 branch. Yufei On Wed, Jun 18, 2025 at 2:51 PM Yufei Gu wrote: > We could r

Re: [DISCUSS] Prepare for 1.0 Release

Hi Yufei, As discussed before, I think it is preferable to do the renames in / before 1.0 because module names affect published Maven artifact names. For that matter, why not re-branch release/1.0.x from `main`? Thanks, Dmitri. On Wed, Jun 18, 2025 at 5:37 PM Yufei Gu wrote: > Hi JB and Dmitr

Re: [DISCUSS] Prepare for 1.0 Release

We could re-branch, but folks mentioned there are a few Python commits(like https://github.com/apache/polaris/pull/1810) we are not comfortable with having them in 1.0 branch. Feel free to bring up a discussion for more PRs you think it's 1.0 blockers and needed in 1.0. Yufei On Wed, Jun 18, 20

Re: [DISCUSS] Prepare for 1.0 Release

Hi JB and Dmitri, do we need https://github.com/apache/polaris/pull/1695 in 1.0? We used to agree on bringing it to 1.0 if it's ready, but I'm OK with either way. Yufei On Wed, Jun 18, 2025 at 2:31 PM Yufei Gu wrote: > https://github.com/apache/polaris/issues/1616 was resolved by #1830, > #183

Re: [DISCUSS] Prepare for 1.0 Release

https://github.com/apache/polaris/issues/1616 was resolved by #1830, #1834 and #1839. And these three commits are cherry-picked to 1.0 branch already. https://github.com/apache/polaris/issues/1881 was just resolved by #1889, which has been cherry-picked to 1.0 branch. Yufei On Wed, Jun 18, 2025

Re: [DISCUSS] Prepare for 1.0 Release

Hi Yufei, et al. It looks like only two 1.0 blockers remain: [1] https://github.com/apache/polaris/issues/1616 [2] https://github.com/apache/polaris/issues/1881 Re: [1] is anybody actively working on it? Also, I believe a lot of relevant changes got merged recently... WDYT about re-branching `r

Re: Polaris Community Sync on Events

Adding that there's been consensus in the meeting to start with a pure Java interface and go from there. I'm not sure that the statement "Ordering guarantees are **only** possible ... event creation time" (emphasis mine) is correct. During the meeting I mentioned that I strongly believe that