Re: Context-Aware Functions for Apache Polaris

2025-06-17 Thread Prashant Singh
Hey Alex, Thank you for your interest in the thread, and appreciate your inputs ! It seems like there is a misunderstanding about the thread, my intention was just to introduce these catalog evaluated functions or *variables*, which are evaluated based on callers context, and are replaced inline, t

Re: [DISCUSS] Branches in the github repository / + stale branches

2025-06-17 Thread Kenneth Kang
My team has been tracking the 0.9 and 0.10 branches. They haven't diverged too much from their branching points off main. I am good with pruning the branches to focus usage to current versions. Kenneth On 6/16/25 07:57, Dmitri Bourlatchkov wrote: Dropping the 0.9 release branch, and keeping t

Re: [DISCUSS] Branches in the github repository / + stale branches

2025-06-17 Thread Dmitri Bourlatchkov
Hi Kenneth, Slightly off topic to this thread, but you might be interested in the "evolution" PR [1] and the related dev email [2] from the "user side". Any feedback is welcome. [1] https://github.com/apache/polaris/pull/1890 [2] https://lists.apache.org/thread/c0sk6hmtz9l4vs0mjc21wvlpblqhgx7r T

Re: [DISCUSS] Gradle and Maven runner plugins

2025-06-17 Thread Yufei Gu
Thanks for the explanation. I'm OK with moving on with it. The point of suggesting a separate repo is for the PR owner's convenience and for follow-up maintainers. Sorry if that didn’t resonate; I'm OK with either way. Yufei On Tue, Jun 17, 2025 at 1:50 AM Pierre Laporte wrote: > On Tue, Jun 1

Re: [DISCUSS] Gradle and Maven runner plugins

2025-06-17 Thread Pierre Laporte
On Tue, Jun 17, 2025 at 1:42 AM Yufei Gu wrote: > Thanks for the summary. > > * Given that a solution based on Gradle ExecFork or Gretty would only serve > > Polaris devs, and would not be usable by users, it does not seems to be a > > good fit for the overarching goal. > > Could you clarify the

Re: Proposal for Implementation of the Proposed Iceberg REST Spec - Events API

2025-06-17 Thread Adnan Hemani
Hi all, As per the latest community discussion today (6/17), there was a request to put down the intended use cases for storing Polaris Events in the persistence. There are two main use cases I am intending to support: [From the Iceberg Events API proposal

Re: Polaris Community Sync on Events

2025-06-17 Thread Adnan Hemani
Hi everyone, In lieu of a recording of today’s Community Sync on Events, I am posting some notes regarding what was discussed: What is the relationship between Iceberg Events API and Polaris Events, which are proposed in https://github.com/apache/polaris/pull/1844? Persisting Polaris events are

Re: Context-Aware Functions for Apache Polaris

2025-06-17 Thread Alex Dutra
Hi all, Catching up quite late with this discussion thread, my apologies. Trying to sum up my impressions so far: We should definitely avoid parsing SQL and altering view definitions. Instead it seems that Eric's proposal of defining FGAC policies with a clear syntax and spec is a much more robus

Re: [DISCUSS] Polaris Evolution statements for 1.0

2025-06-17 Thread Dmitri Bourlatchkov
FYI: I pushed another update: * Removed java code from SemVer - the main rationale for this is that the API surface at this stage of the project is still pretty volatile and following semver will probably mean that every release is a new major. Please let me know if you'd prefer a different approa