[VOTE] Release Apache Cassandra 5.0.2

Proposing the test build of Cassandra 5.0.2 for release. sha1: f278f6774fc76465c182041e081982105c3e7dbb Git: https://github.com/apache/cassandra/tree/5.0.2-tentative Maven Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1349/org/apache/cassandra/cassandra-all/5.0.2

Re: [VOTE] Release Apache Cassandra 5.0.2

+1. CASSANDRA-19989 and CASSANDRA-19968 will be good fixes to get out. On Oct 16, 2024, at 5:20 AM, Mick Semb Wever wrote: Proposing the test build of Cassandra 5.0.2 for release. sha1: f278f6774fc76465c182041e081982105c3e7dbb Git: https://github.com/apache/cassandra/tree/5.0.2-tentative Maven

Re: [DISCUSS] Introduce CREATE TABLE LIKE grammer

Disscussed with Bernardo on slack，and +1 with his advice on adding a fourth keyword. The keyword would be CONSTRAINTS ， any more suggestion ？ guo Maxwell 于2024年10月16日 周三上午9:55写道： > Hi yifan, > Thanks for bringing this up. The SELECT permission on the original table > is needed. Mysql and PG all

Re: [DISCUSS] Introduce CREATE TABLE LIKE grammer

Sorry that I overlooked the definition of the default in the CEP. I did look for it but I didn’t see it. I think the default behavior you explained makes perfect sense & what one would expect. I like the flexibility of INCLUDING and EXCLUDING that you are considering. Would it make sense to use

Re: [DISCUSS] Introduce CREATE TABLE LIKE grammer

I'm coming at this with both a deep ANSI SQL background as well as CQL background. Defining the default behavior is the starting point. What gets copied if we do "CREATE TABLE new_table LIKE original_table;" without a WITH clause? Then, you build on that with the specific WITH options. WITH ALL

Re: [VOTE] Release Apache Cassandra 5.0.2

+1 On Thu, 17 Oct 2024 at 0:46, David Capwell wrote: > +1 > > > On Oct 16, 2024, at 2:45 PM, Dinesh Joshi wrote: > > +1 > > On Wed, Oct 16, 2024 at 5:19 AM Mick Semb Wever wrote: > >> Proposing the test build of Cassandra 5.0.2 for release. >> >> sha1: f278f6774fc76465c182041e081982105c3e7dbb

Re: [DISCUSS] Introduce CREATE TABLE LIKE grammer

To yifan : At the beginning of the period, I also thought about adding the keyword ALL, refer to pg , but I give up when writing cep as I find that there may be not so many properties (only three) to copy for C* and It is possible to d

Re: [VOTE] Release Apache Cassandra 5.0.2

+1 On Wed, Oct 16, 2024 at 5:19 AM Mick Semb Wever wrote: > Proposing the test build of Cassandra 5.0.2 for release. > > sha1: f278f6774fc76465c182041e081982105c3e7dbb > Git: https://github.com/apache/cassandra/tree/5.0.2-tentative > Maven Artifacts: > https://repository.apache.org/content/repos

Re: [VOTE] Release Apache Cassandra 5.0.2

+1 > On Oct 16, 2024, at 2:45 PM, Dinesh Joshi wrote: > > +1 > > On Wed, Oct 16, 2024 at 5:19 AM Mick Semb Wever > wrote: >> Proposing the test build of Cassandra 5.0.2 for release. >> >> sha1: f278f6774fc76465c182041e081982105c3e7dbb >> Git: https://github.com/apache/

Re: [DISCUSS] Introduce CREATE TABLE LIKE grammer

"WITH ALL" seems to be a natural addition to the directives. What do you think about adding the fifth keyword ALL to retain all fields of the table schema? For instance, CREATE TABLE new_table LIKE original_table WITH ALL, it replicates options, indexes, triggers, constraints and any applicable ki

Re: [DISCUSS] Introduce CREATE TABLE LIKE grammer

+1 That makes much more sense in my experience. On Wed, Oct 16, 2024 at 12:12 PM Dave Herrington wrote: > I'm coming at this with both a deep ANSI SQL background as well as CQL > background. > > Defining the default behavior is the starting point. What gets copied if > we do "CREATE TABLE new_t