Re: [DISCUSS] CEP 52: Schema Annotations for ApacheCassandra

2025-08-12 Thread Jyothsna Konisa
Hi Stefan, Patrick, and everyone, Thank you all for your valuable feedback and suggestions. I've consolidated the key points and wanted to share our thinking on a path forward. *Regarding the PostgreSQL-style Syntax (COMMENT ON & SECURITY LABEL)* We agree with the consensus that adopting Postgr

Re: [DISCUSS] CEP 52: Schema Annotations for ApacheCassandra

2025-08-12 Thread Štefan Miklošovič
One more point I would like to add. If we enrich the output with comments, I think that seeing comments should be only default if I can take what DESCRIBE prints and I can copy it as-is and create tables from it. Very often, DESCRIBE acts as something like "I will copy this schema here so I can re

JDK 25 Initial Release Candidate

2025-08-12 Thread David Delabassee via dev
Welcome to the OpenJDK Quality Outreach summer update! Everything is on track for the General Availability of Java 25 on September 16 as the JDK 25 Release Candidate builds (RC1 - builds 35) are now available[1]. If you haven't done so yet, please start testing your project(s) using JDK 26 earl

Re: [DISCUSS] CEP 52: Schema Annotations for ApacheCassandra

2025-08-12 Thread Mick
a point of order and a reminder: aside from suggestions that the CEP author is free to adopt or not, anything that's assuming to steer what the CEP should be should be accompanied with the willingness to commit in helping making it happen. we want to work as a meritocracy: those that lead the w

Re: [DISCUSS] CEP 52: Schema Annotations for ApacheCassandra

2025-08-12 Thread Štefan Miklošovič
I like the idea of COMMENT ON and alike from PG! Yes, great stuff, as we do not invent anything custom and we will be as close as possible to industry standard. So, if I understand this correctly, on COMMENT ON, we would save each comment to a dedicated table. Then on DESCRIBE, we would "enrich" t