You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@polaris.apache.org by Dmitri Bourlatchkov <di...@apache.org> on 2025/10/24 16:38:14 UTC
[DISCUSS] Flagging Events Persistence as beta in 1.2.0
Hi All,
I'm starting this thread to consolidate the various discussions and reach
consensus about flagging events as "beta" in 1.2.0.
https://github.com/apache/polaris/pull/2877
https://lists.apache.org/thread/1wwr0wmt88rxrp0n0k0bgmjpls14tcgn
https://lists.apache.org/thread/wso9sv9s36wv8rcd2ol7rwq1d1mmt4f4
TL;DR:
* AFAIK 1.2.0 is the first release where events are available.
* The JDBC schema for events is very likely to change after 1.2.0 in a
non-backward compatible way.
* Java class are very likely to change too
To recap: I propose flagging the whole events feature as "beta" in 1.2.0
and specifically adding release notes that the JDBC schema will change and
old events data will NOT be readable (i.e. dropped) after upgrading to the
next release.
Thoughts?
Thanks,
Dmitri.
Re: [DISCUSS] Flagging Events Persistence as beta in 1.2.0
Posted by Alexandre Dutra <ad...@apache.org>.
Hi all,
I support flagging the whole Events feature as "beta" in 1.2.0.
I already commented in [2877] but to summarize my opinion here, I
think "beta" is appropriate for the following reasons:
1. The API is still evolving, including the SQL schema.
2. The sinks being released in 1.2 are only partially implemented.
I think it's important to flag now, and not in 1.3, because it would
be awkward to downgrade a feature from production-ready to beta.
Thanks,
Alex
On Fri, Oct 24, 2025 at 6:38 PM Dmitri Bourlatchkov <di...@apache.org> wrote:
>
> Hi All,
>
> I'm starting this thread to consolidate the various discussions and reach
> consensus about flagging events as "beta" in 1.2.0.
>
> https://github.com/apache/polaris/pull/2877
>
> https://lists.apache.org/thread/1wwr0wmt88rxrp0n0k0bgmjpls14tcgn
>
> https://lists.apache.org/thread/wso9sv9s36wv8rcd2ol7rwq1d1mmt4f4
>
> TL;DR:
>
> * AFAIK 1.2.0 is the first release where events are available.
> * The JDBC schema for events is very likely to change after 1.2.0 in a
> non-backward compatible way.
> * Java class are very likely to change too
>
> To recap: I propose flagging the whole events feature as "beta" in 1.2.0
> and specifically adding release notes that the JDBC schema will change and
> old events data will NOT be readable (i.e. dropped) after upgrading to the
> next release.
>
> Thoughts?
>
> Thanks,
> Dmitri.
Re: [DISCUSS] Flagging Events Persistence as beta in 1.2.0
Posted by Prashant Singh <pr...@snowflake.com.INVALID>.
Thank you everyone for chiming in and thoughtful suggestions !
We were able to reach a consensus on this and 1.2 PR with recommendations
is merged !
On Mon, Oct 27, 2025 at 10:53 AM Yufei Gu <fl...@gmail.com> wrote:
> +1 on flagging the events feature. I agree that it’s important to clearly
> communicate its evolving state in 1.2.0.
>
> That said, I’m slightly concerned about the long-term path of “removing the
> beta label”, which we don't have. In open source projects, that transition
> can be subjective and inconsistent across features. “Preview” might be a
> better term for features like this, it conveys that the design is
> stabilizing but still open to iteration, without implying a rigid beta to
> GA promotion process.
>
> Either way, I’m supportive of documenting the schema volatility and API
> evolution clearly in the release notes.
>
> Yufei
>
>
> On Mon, Oct 27, 2025 at 9:03 AM Dmitri Bourlatchkov <di...@apache.org>
> wrote:
>
> > Hi All,
> >
> > Linking about observation by Alex:
> > https://github.com/apache/polaris/issues/2913
> >
> > Cheers,
> > Dmitri.
> >
> > On Mon, Oct 27, 2025 at 11:28 AM Alexandre Dutra <ad...@apache.org>
> > wrote:
> >
> > > Hi all,
> > >
> > > Another angle to consider: afaict we don't do any integration test for
> > > any of the sinks (JDBC or CloudWatch) – only unit tests. This means
> > > that more complex issues may have gone unnoticed so far. Adding a few
> > > Quarkus or IT tests for both sinks would significantly increase our
> > > confidence in their reliability.
> > >
> > > Thanks,
> > > Alex
> > >
> > > On Sun, Oct 26, 2025 at 5:54 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
> > > wrote:
> > > >
> > > > Hi
> > > >
> > > > I’m in favor of indication in the release notes, that’s important.
> > > > Beta, preview, “can be change”, … I don’t have a strong opinion about
> > the
> > > > wording, but agree on the purpose.
> > > >
> > > > Regards
> > > > JB
> > > >
> > > > Le ven. 24 oct. 2025 à 18:38, Dmitri Bourlatchkov <di...@apache.org>
> a
> > > > écrit :
> > > >
> > > > > Hi All,
> > > > >
> > > > > I'm starting this thread to consolidate the various discussions and
> > > reach
> > > > > consensus about flagging events as "beta" in 1.2.0.
> > > > >
> > > > > https://github.com/apache/polaris/pull/2877
> > > > >
> > > > > https://lists.apache.org/thread/1wwr0wmt88rxrp0n0k0bgmjpls14tcgn
> > > > >
> > > > > https://lists.apache.org/thread/wso9sv9s36wv8rcd2ol7rwq1d1mmt4f4
> > > > >
> > > > > TL;DR:
> > > > >
> > > > > * AFAIK 1.2.0 is the first release where events are available.
> > > > > * The JDBC schema for events is very likely to change after 1.2.0
> in
> > a
> > > > > non-backward compatible way.
> > > > > * Java class are very likely to change too
> > > > >
> > > > > To recap: I propose flagging the whole events feature as "beta" in
> > > 1.2.0
> > > > > and specifically adding release notes that the JDBC schema will
> > change
> > > and
> > > > > old events data will NOT be readable (i.e. dropped) after upgrading
> > to
> > > the
> > > > > next release.
> > > > >
> > > > > Thoughts?
> > > > >
> > > > > Thanks,
> > > > > Dmitri.
> > > > >
> > >
> >
>
Re: [DISCUSS] Flagging Events Persistence as beta in 1.2.0
Posted by Yufei Gu <fl...@gmail.com>.
+1 on flagging the events feature. I agree that it’s important to clearly
communicate its evolving state in 1.2.0.
That said, I’m slightly concerned about the long-term path of “removing the
beta label”, which we don't have. In open source projects, that transition
can be subjective and inconsistent across features. “Preview” might be a
better term for features like this, it conveys that the design is
stabilizing but still open to iteration, without implying a rigid beta to
GA promotion process.
Either way, I’m supportive of documenting the schema volatility and API
evolution clearly in the release notes.
Yufei
On Mon, Oct 27, 2025 at 9:03 AM Dmitri Bourlatchkov <di...@apache.org>
wrote:
> Hi All,
>
> Linking about observation by Alex:
> https://github.com/apache/polaris/issues/2913
>
> Cheers,
> Dmitri.
>
> On Mon, Oct 27, 2025 at 11:28 AM Alexandre Dutra <ad...@apache.org>
> wrote:
>
> > Hi all,
> >
> > Another angle to consider: afaict we don't do any integration test for
> > any of the sinks (JDBC or CloudWatch) – only unit tests. This means
> > that more complex issues may have gone unnoticed so far. Adding a few
> > Quarkus or IT tests for both sinks would significantly increase our
> > confidence in their reliability.
> >
> > Thanks,
> > Alex
> >
> > On Sun, Oct 26, 2025 at 5:54 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
> > wrote:
> > >
> > > Hi
> > >
> > > I’m in favor of indication in the release notes, that’s important.
> > > Beta, preview, “can be change”, … I don’t have a strong opinion about
> the
> > > wording, but agree on the purpose.
> > >
> > > Regards
> > > JB
> > >
> > > Le ven. 24 oct. 2025 à 18:38, Dmitri Bourlatchkov <di...@apache.org> a
> > > écrit :
> > >
> > > > Hi All,
> > > >
> > > > I'm starting this thread to consolidate the various discussions and
> > reach
> > > > consensus about flagging events as "beta" in 1.2.0.
> > > >
> > > > https://github.com/apache/polaris/pull/2877
> > > >
> > > > https://lists.apache.org/thread/1wwr0wmt88rxrp0n0k0bgmjpls14tcgn
> > > >
> > > > https://lists.apache.org/thread/wso9sv9s36wv8rcd2ol7rwq1d1mmt4f4
> > > >
> > > > TL;DR:
> > > >
> > > > * AFAIK 1.2.0 is the first release where events are available.
> > > > * The JDBC schema for events is very likely to change after 1.2.0 in
> a
> > > > non-backward compatible way.
> > > > * Java class are very likely to change too
> > > >
> > > > To recap: I propose flagging the whole events feature as "beta" in
> > 1.2.0
> > > > and specifically adding release notes that the JDBC schema will
> change
> > and
> > > > old events data will NOT be readable (i.e. dropped) after upgrading
> to
> > the
> > > > next release.
> > > >
> > > > Thoughts?
> > > >
> > > > Thanks,
> > > > Dmitri.
> > > >
> >
>
Re: [DISCUSS] Flagging Events Persistence as beta in 1.2.0
Posted by Dmitri Bourlatchkov <di...@apache.org>.
Hi All,
Linking about observation by Alex:
https://github.com/apache/polaris/issues/2913
Cheers,
Dmitri.
On Mon, Oct 27, 2025 at 11:28 AM Alexandre Dutra <ad...@apache.org> wrote:
> Hi all,
>
> Another angle to consider: afaict we don't do any integration test for
> any of the sinks (JDBC or CloudWatch) – only unit tests. This means
> that more complex issues may have gone unnoticed so far. Adding a few
> Quarkus or IT tests for both sinks would significantly increase our
> confidence in their reliability.
>
> Thanks,
> Alex
>
> On Sun, Oct 26, 2025 at 5:54 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
> wrote:
> >
> > Hi
> >
> > I’m in favor of indication in the release notes, that’s important.
> > Beta, preview, “can be change”, … I don’t have a strong opinion about the
> > wording, but agree on the purpose.
> >
> > Regards
> > JB
> >
> > Le ven. 24 oct. 2025 à 18:38, Dmitri Bourlatchkov <di...@apache.org> a
> > écrit :
> >
> > > Hi All,
> > >
> > > I'm starting this thread to consolidate the various discussions and
> reach
> > > consensus about flagging events as "beta" in 1.2.0.
> > >
> > > https://github.com/apache/polaris/pull/2877
> > >
> > > https://lists.apache.org/thread/1wwr0wmt88rxrp0n0k0bgmjpls14tcgn
> > >
> > > https://lists.apache.org/thread/wso9sv9s36wv8rcd2ol7rwq1d1mmt4f4
> > >
> > > TL;DR:
> > >
> > > * AFAIK 1.2.0 is the first release where events are available.
> > > * The JDBC schema for events is very likely to change after 1.2.0 in a
> > > non-backward compatible way.
> > > * Java class are very likely to change too
> > >
> > > To recap: I propose flagging the whole events feature as "beta" in
> 1.2.0
> > > and specifically adding release notes that the JDBC schema will change
> and
> > > old events data will NOT be readable (i.e. dropped) after upgrading to
> the
> > > next release.
> > >
> > > Thoughts?
> > >
> > > Thanks,
> > > Dmitri.
> > >
>
Re: [DISCUSS] Flagging Events Persistence as beta in 1.2.0
Posted by Alexandre Dutra <ad...@apache.org>.
Hi all,
Another angle to consider: afaict we don't do any integration test for
any of the sinks (JDBC or CloudWatch) – only unit tests. This means
that more complex issues may have gone unnoticed so far. Adding a few
Quarkus or IT tests for both sinks would significantly increase our
confidence in their reliability.
Thanks,
Alex
On Sun, Oct 26, 2025 at 5:54 PM Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>
> Hi
>
> I’m in favor of indication in the release notes, that’s important.
> Beta, preview, “can be change”, … I don’t have a strong opinion about the
> wording, but agree on the purpose.
>
> Regards
> JB
>
> Le ven. 24 oct. 2025 à 18:38, Dmitri Bourlatchkov <di...@apache.org> a
> écrit :
>
> > Hi All,
> >
> > I'm starting this thread to consolidate the various discussions and reach
> > consensus about flagging events as "beta" in 1.2.0.
> >
> > https://github.com/apache/polaris/pull/2877
> >
> > https://lists.apache.org/thread/1wwr0wmt88rxrp0n0k0bgmjpls14tcgn
> >
> > https://lists.apache.org/thread/wso9sv9s36wv8rcd2ol7rwq1d1mmt4f4
> >
> > TL;DR:
> >
> > * AFAIK 1.2.0 is the first release where events are available.
> > * The JDBC schema for events is very likely to change after 1.2.0 in a
> > non-backward compatible way.
> > * Java class are very likely to change too
> >
> > To recap: I propose flagging the whole events feature as "beta" in 1.2.0
> > and specifically adding release notes that the JDBC schema will change and
> > old events data will NOT be readable (i.e. dropped) after upgrading to the
> > next release.
> >
> > Thoughts?
> >
> > Thanks,
> > Dmitri.
> >
Re: [DISCUSS] Flagging Events Persistence as beta in 1.2.0
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi
I’m in favor of indication in the release notes, that’s important.
Beta, preview, “can be change”, … I don’t have a strong opinion about the
wording, but agree on the purpose.
Regards
JB
Le ven. 24 oct. 2025 à 18:38, Dmitri Bourlatchkov <di...@apache.org> a
écrit :
> Hi All,
>
> I'm starting this thread to consolidate the various discussions and reach
> consensus about flagging events as "beta" in 1.2.0.
>
> https://github.com/apache/polaris/pull/2877
>
> https://lists.apache.org/thread/1wwr0wmt88rxrp0n0k0bgmjpls14tcgn
>
> https://lists.apache.org/thread/wso9sv9s36wv8rcd2ol7rwq1d1mmt4f4
>
> TL;DR:
>
> * AFAIK 1.2.0 is the first release where events are available.
> * The JDBC schema for events is very likely to change after 1.2.0 in a
> non-backward compatible way.
> * Java class are very likely to change too
>
> To recap: I propose flagging the whole events feature as "beta" in 1.2.0
> and specifically adding release notes that the JDBC schema will change and
> old events data will NOT be readable (i.e. dropped) after upgrading to the
> next release.
>
> Thoughts?
>
> Thanks,
> Dmitri.
>