Strong +1 to copy all options by default. This is intuitive to me. Then I
would like to explicitly override any options of my choosing.
-Dave
On Wed, Oct 23, 2024 at 9:57 PM guo Maxwell wrote:
> OK，thank you for your suggestions ，I will revise the CEP and copy table
> OPTIONS by default.
>
> J
OK，thank you for your suggestions ，I will revise the CEP and copy table
OPTIONS by default.
Jon Haddad 于2024年10月23日 周三下午9:18写道：
> Also strongly +1 to copying all the options.
>
>
> On Wed, Oct 23, 2024 at 5:52 AM Josh McKenzie
> wrote:
>
>> I'm a very strong +1 to having the default functionalit
Hello,
I wanted to throw some ideas and a vision in terms of metrics,
trancing and the adoption of new integrations, particularly
OpenTelemetry. I personally feel that the more integrations we have,
the better the adoption of Cassandra as a database will be. With
OpenTelemetry, users could have a
https://issues.apache.org/jira/projects/CASSPYTHON/
https://issues.apache.org/jira/projects/CASSJAVA/
https://issues.apache.org/jira/projects/CASSGO/
are now live. If you know of any issues to move there, please do so.
Kind Regards,
Brandon
On Wed, Oct 23, 2024 at 6:59 AM Brandon Williams wrot
Also strongly +1 to copying all the options.
On Wed, Oct 23, 2024 at 5:52 AM Josh McKenzie wrote:
> I'm a very strong +1 to having the default functionality be to copy *ALL*
> options.
>
> Intuitively, as a user, if I tell a software system to make a clone of
> something I don't expect it to be
I'm a very strong +1 to having the default functionality be to copy *ALL*
options.
Intuitively, as a user, if I tell a software system to make a clone of
something I don't expect it to be shallow or a subset defined by some external
developer somewhere. I expect it to be a clone.
Adding in som
If nobody objects I will be creating the CASS jira projects later today.
Kind Regards,
Brandon
On Tue, Oct 22, 2024 at 10:35 AM Ekaterina Dimitrova
wrote:
>
> Honestly, counting the letters was also a thing that happened to me but I
> should admit that even with CASSANDRAANALYTICS we count the
On Wed, 23 Oct 2024 at 05:48, Jordan West wrote:
> Josh/Mick, where does that leave us? I’d like to start with the smaller
> scope Josh described in his last email. We can tackle in-tree/stress
> separately.
>
> I was going to start working on getting signed ICLAs. Does that still
> sound like th
options are inherently part of that table as well, same as schema. In fact,
_schema_ includes all options. Not just columns and its names. If you
change some option, you effectively have a different schema, schema version
changes by changing an option. So if we do not copy options too, we are
kind
