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 <[email protected]> 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.
