Patrick and Jeff,
I have to chime in with an opinion having been a SQL person for more than
30 years...
The DISTINCT concept is a little confusing to me, since, in SQL, DISTINCT
reduces a repeating result set to a unique result set (where all of the
selected values are repeating), rather than jus
of Cassandra nodes in a
> cluster. There is no TTL because each row represents the repair status of
> that particular node. The entries would be automatically added/removed as
> nodes are added/removed from the Cassandra cluster.
>
> Jaydeep
>
> On Sat, Mar 8, 2025 at 7:46
Jaydeep,
Thank you for your excellent efforts on this mission-critical feature. The
stated goals of CEP-37 are noble and stand to make valuable improvements
for cluster operations. I look forward to testing these new capabilities.
My apologies up-front if you’ve already answered these questions
and Chief Engineer
RhinoSource, Inc.
*Data Lake Architecture, Cloud Computing and Advanced Analytics.*
www.rhinosource.com
On Sun, Dec 8, 2024 at 7:22 AM Dave Herrington
wrote:
> Paulo,
>
> I understand your perspective.
>
> Short of waiting for UCS to prove itself out, I guess i
optimize the cost for you. Otherwise, the database should
> work out of the box and this is provided by LCS. If LCS can not keep up, it
> means the cluster is under provisioned and needs to be expanded, it's not a
> functional issue but a capacity issue.
>
> Cheers,
>
>
Chiming in from the field, I think maintaining the familiar status quo
until a panacea compaction strategy proves itself out (could that be UCS?)
makes sense to me. I feel it could be maddening to customers if LCS
started showing up in schemas after an upgrade just because the default
changed. If
👍
On Thu, Nov 7, 2024 at 10:58 PM guo Maxwell wrote:
> Thank you very much for your careful observation. I have corrected it, it
> is out of date, just remove the OPTIONS keyword.
>
>
> Dave Herrington 于2024年11月8日周五 14:52写道：
>
>> I wanted to weigh in on the options ha
gt;>>>>> Thanks.
>>>>>>
>>>>>> Štefan Miklošovič 于2024年11月4日周一 17:00写道：
>>>>>>
>>>>>>> Hi Maxwell,
>>>>>>>
>>>>>>> 1) I noticed that there is table copying across
于2024年10月21日周一 14:56写道：
>>>
>>> To yifan :
>>> I don't mind adding the ALL keyword, and it has been updated into CEP.
>>>
>>> As all you can see, our original intention was that the grammar would
>>> not be too complicated, which is what I
er we are copying a table here so if a base one has
> constraints, its copy will have them too. A user can subsequently "ALTER"
> them.
>
> On Thu, Oct 17, 2024 at 5:31 PM Dave Herrington
> wrote:
>
>> Basing it on CREATE TABLE, the BNF definition of the simple
>>
}
AND default_time_to_live = 86400;
This seems pretty clean & straightforward.
-Dave
On Thu, Oct 17, 2024 at 4:05 PM Dave Herrington
wrote:
> This simple approach resonates with me. I think the Cassandra doc uses
> "INDEXES" as the plural for index, i.e.:
> https://cassan
else. "WITH" will opt-in into that.
>>>
>>>
>>> Seeing us contemplating using "INCLUDING" and "EXCLUDING" on individual
>>> options makes me sad a little bit. I think we are over-engineering this. I
>>> just don't see a
ult behavior is only copy column name, data type ,data mask , you
> can see more detail from CEP-43
> <https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-43++Apache+Cassandra+CREATE+TABLE++LIKE>
> .
>
>
> Patrick McFadin 于2024年10月17日周四 06:43写道：
>
>> +1 That makes mu
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
Jon/Jordan,
Happy to contribute to easy-cass-stress in any way I can that will help the
cause. I'd probably be most effective in a QA role, since much of my field
work with DataStax customers involves developing load & stress tests to
measure the outer bounds of cluster capacity under max load co
Hey, Paulo!
Thanks for reaching out about this event!
2 topics come to mind that I could present, based on recent project
experiences:
- Using NoSQLBench for Cassandra Load & Stress Testing (have done this
recently for US Postal Service and for a fraud detection company based in
SoCal,
16 matches
Mail list logo
