There’s a difference between the two though. Constraints are part of the table
schema, and (independent of the interaction with Guardrails), have no
dependency on yaml files being perfectly in sync across the cluster. Therefore,
the feature (Constraints) on its own doesn’t depend on
To me, the difference between system-level guardrails and table-level
constraints is the difference between operational concerns (guardrails) and
business concerns (table-level constraints). The two things are only related to
one another because they both may limit the value of a field in some
+1 (nb, but not a vote, so ¯\_(ツ)_/¯ ) - would be lovely to not have to deal
with this individually for each project in which we use the in-jvm dtest
framework. As Francisco noted, we’re using this in the sidecar and Analytics
projects now and I’ve had to jump through a lot of hoops to get
+1 (nb) - wiłl be nice for the analytics writer to be able to size SSTables
appropriately and efficiently.
Doug
> On Oct 24, 2023, at 10:36 PM, guo Maxwell wrote:
>
>
>
> Chris Lohfink mailto:clohfin...@gmail.com>>
> 于2023年10月25日周三 05:02写道：
>> +1
>>
>> On Tue, Oct 24, 2023 at 11:24 AM
+1 on reason string, especially some way to indicate what replaces a method if
it’s being moved into some other class/new method with more parameters/etc.
I’ve found lots of cases (in code bases in general, not C* in particular) where
something is marked as Deprecated but there’s no mention of
+1 (nb)
> On Oct 3, 2023, at 10:37 AM, C. Scott Andreas wrote:
>
> +1 (nb)
>
> Accepting this donation would mark a huge milestone for the project.
>
>> On Oct 3, 2023, at 4:25 AM, Josh McKenzie wrote:
>>
>>
>>> I see now this will likely be instead apache/cassandra-java-driver
>> I was
I’d agree that anywhere we’re calling `nodetoolResult` or `nodetool` in a test,
it would be better to enable JMX and use it rather than the older mocks we set
up to enable calling the mbeans directly. I don’t think enabling JMX by default
is the right way to go mostly due to the added
My only concern about removal in 5.1 would be that removing it in a “minor”
release would really be a breaking change, and semver says that should happen
in a major version.
If we really want to be semver compliant, it shouldn’t be removed until 6.0
(or, if we remove it in the next release, we
+1 (nb) - Thanks Dinesh!
Doug
> On Aug 16, 2023, at 5:34 PM, Dinesh Joshi wrote:
>
> Proposing the test build of in-jvm dtest API 0.0.16 for release.
>
> Repository:
> https://gitbox.apache.org/repos/asf?p=cassandra-in-jvm-dtest-api.git
>
> Candidate SHA:
>
+1 (nb)
> On May 24, 2023, at 11:32 AM, Brandon Williams wrote:
>
> +1
>
> Kind Regards,
> Brandon
>
> On Wed, May 24, 2023 at 10:31 AM Dinesh Joshi wrote:
>>
>> Proposing the test build of in-jvm dtest API 0.0.15 for release.
>>
>> Repository:
>>
+1 (nb)
Doug Rohrer
> On May 15, 2023, at 7:17 PM, Brandon Williams wrote:
>
> +1
>
> Kind Regards,
> Brandon
>
>> On Mon, May 15, 2023 at 5:12 PM Dinesh Joshi wrote:
>>
>> Proposing the test build of in-jvm dtest API 0.0.14 for release.
>>
+1 (nb)
> On May 8, 2023, at 4:52 AM, Piotr Kołaczkowski wrote:
>
> Let's vote.
>
> https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-29%3A+CQL+NOT+operator
>
> Piotr Kołaczkowski
> e. pkola...@datastax.com
> w. www.datastax.com
improving it.
Doug Rohrer
> On May 6, 2023, at 1:52 PM, Dinesh Joshi wrote:
>
> +1
>
>> On May 4, 2023, at 9:46 AM, Doug Rohrer wrote:
>>
>> Hello all,
>>
>> I’d like to put CEP-28 to a vote.
>>
>> Proposal:
>>
>> https://cwiki.apa
if there are at least three binding +1s and no binding vetoes.
Thanks,
Doug Rohrer
> On Apr 5, 2023, at 11:18 AM, Doug Rohrer wrote:
>
> Sorry for the delay in responding here - yes, we can add some diagrams to the
> CEP - I’ll try to get that done by end-of-week.
>
> Thanks,
>
> Doug
>
>> On Mar 28, 2023, at 1:14 PM, J. D. Jordan wrote:
>
Sorry for the delay in responding here - yes, we can add some diagrams to the
CEP - I’ll try to get that done by end-of-week.
Thanks,
Doug
> On Mar 28, 2023, at 1:14 PM, J. D. Jordan wrote:
>
> Maybe some data flow diagrams could be added to the cep showing some example
> operations for
I agree that the analytics library will need to support vnodes. To be clear,
there’s nothing preventing the solution from working with vnodes right now, and
no assumptions about a 1:1 topology between a token and a node. However, we
don’t, today, have the ability to test vnode support
keep the discussion here on the dev list vs. in the wiki,
as we’ve found it easier to manage via email.
Sincerely,
Doug Rohrer & James Berragan
Hi folks:
I’d like to post a CEP, but given it’s the first time I’m trying to contribute
to the wiki, I don’t have access.
If someone with access could please grant user drohrer access to post, I’d
greatly appreciate it.
Thanks,
Doug Rohrer
19 matches
Mail list logo
