Re: NGCC 2018?

[Ben Bromhead]

I like Jon's idea, plenty of food for thought in terms of a 4.0
retrospective + what's on the future.

On Wed, Sep 5, 2018 at 1:18 PM sankalp kohli  wrote:

> Another thing to  discuss will be how to improve testing further from the
> learning of finding bugs in C* 4.0.
>
> On Wed, Sep 5, 2018 at 9:57 AM Jason Brown  wrote:
>
> > +1 to Jon's sentiment. Further, perhaps we should use that time after
> > GA'ing 4.0 to poll our users what they need/want from the next major
> > release of the database.
> >
> > On Wed, Sep 5, 2018 at 9:31 AM, Jonathan Haddad 
> wrote:
> >
> > > I'm thinking a month or two after 4.0 would give us time to unwind
> after
> > > the release and start to give real thought to big changes coming in the
> > > next release.  Let's focus on one thing at a time.
> > >
> > > On Wed, Sep 5, 2018 at 12:29 PM sankalp kohli 
> > > wrote:
> > >
> > > > A good time for NGCC will be closer to 4.0 release where we can plan
> > what
> > > > we can put it on 4.0-next. I am not sure doing it now is going to
> help
> > > when
> > > > we are months away from 4.0 release.
> > > >
> > > > On Fri, Aug 31, 2018 at 7:42 AM Jay Zhuang 
> > > wrote:
> > > >
> > > > > Are we going to have a dev event next month? Or anything this year?
> > We
> > > > may
> > > > > also be able to provide space in bay area and help to organize it.
> > > > (Please
> > > > > let us know, so we could get final approval for that).
> > > > >
> > > > > On Fri, Jul 27, 2018 at 10:05 AM Jonathan Haddad <
> j...@jonhaddad.com>
> > > > > wrote:
> > > > >
> > > > > > My interpretation of Nate's statement was that since there would
> > be a
> > > > > bunch
> > > > > > of us at Lynn's event, we might as well do NGCC at the same time.
> > > > > >
> > > > > > On Thu, Jul 26, 2018 at 9:03 PM Ben Bromhead <
> b...@instaclustr.com>
> > > > > wrote:
> > > > > >
> > > > > > > It sounds like there may be an appetite for something, but the
> > NGCC
> > > > in
> > > > > > its
> > > > > > > current format is likely to not be that useful?
> > > > > > >
> > > > > > > Is a bay area event focused on C* developers something that is
> > > > > > interesting
> > > > > > > for the broader dev community? In whatever format that may be?
> > > > > > >
> > > > > > > On Tue, Jul 24, 2018 at 5:02 PM Nate McCall <
> zznat...@gmail.com>
> > > > > wrote:
> > > > > > >
> > > > > > > > This was discussed amongst the PMC recently. We did not come
> > to a
> > > > > > > > conclusion and there were not terribly strong feelings either
> > > way.
> > > > > > > >
> > > > > > > > I don't feel like we need to hustle to get "NGCC" in place,
> > > > > > > > particularly given our decided focus on 4.0. However, that
> > should
> > > > not
> > > > > > > > stop us from doing an additional 'c* developer' event in
> sept.
> > to
> > > > > > > > coincide with distributed data summit.
> > > > > > > >
> > > > > > > > On Wed, Jul 25, 2018 at 5:03 AM, Patrick McFadin <
> > > > pmcfa...@gmail.com
> > > > > >
> > > > > > > > wrote:
> > > > > > > > > Ben,
> > > > > > > > >
> > > > > > > > > Lynn Bender had offered a space the day before Distributed
> > Data
> > > > > > Summit
> > > > > > > in
> > > > > > > > > September (http://distributeddatasummit.com/) since we are
> > > both
> > > > > > > platinum
> > > > > > > > > sponsors. I thought he and Nate had talked about that
> being a
> > > > good
> > > > > > > place
> > > > > > > > > for NGCC since many of us will be in town already.
> > > > > > > > >
> > > > > > > > > Nate, now that I've spoken for you, you can clarify, :D
> > > > > > > > >
> > > > > > > > > Patrick
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > -
> > > > > > > > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> > > > > > > > For additional commands, e-mail:
> dev-h...@cassandra.apache.org
> > > > > > > >
> > > > > > > > --
> > > > > > > Ben Bromhead
> > > > > > > CTO | Instaclustr 
> > > > > > > +1 650 284 9692 <(650)%20284-9692>
> > > > > > > Reliability at Scale
> > > > > > > Cassandra, Spark, Elasticsearch on AWS, Azure, GCP and
> Softlayer
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Jon Haddad
> > > > > > http://www.rustyrazorblade.com
> > > > > > twitter: rustyrazorblade
> > > > > >
> > > > >
> > > >
> > >
> > >
> > > --
> > > Jon Haddad
> > > http://www.rustyrazorblade.com
> > > twitter: rustyrazorblade
> > >
> >
>
-- 
Ben Bromhead
CTO | Instaclustr 
+1 650 284 9692
Reliability at Scale
Cassandra, Spark, Elasticsearch on AWS, Azure, GCP and Softlayer

Re: NEQ-restriction in select-where clause

[dilaz03]

Yes, but I need for select ;-)

пн, 10 сент. 2018 г., 11:03 Jacques-Henri Berthemet <
jacques-henri.berthe...@genesys.com>:

> Hi,
>
> You can only use IF = or IF != on insert, update or delete statements, it
> does not work on select. When using it, it will create a LWT transaction
> and you'll need full PK in the where condition, you can apply the IF on
> values of the row. For example:
>
> update table set type = 'somethingelse' where pk='42' if type !=
> 'something';
>
> --
> Jacques-Henri Berthemet
>
> -Original Message-
> From: Dmitry Lazurkin 
> Sent: Sunday, September 09, 2018 2:12 AM
> To: dev@cassandra.apache.org
> Subject: NEQ-restriction in select-where clause
>
> Hello.
>
> Does it make sense to implement != restriction in select-where clause?
> Is it possible?
>
> Thank you.
>
> PS. I want to implement that.
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
>

Re: NEQ-restriction in select-where clause

[dilaz03]

Thank you. Yes, I known, it's working only for ALLOW FILTERING. Ok, I
understand, it's possible.

пн, 10 сент. 2018 г., 11:24 Benjamin Lerer :

> It can be done for filtering, otherwise it is really tricky (I am not even
> sure it can be done to be honest).
>
>
>
> On Sun, Sep 9, 2018 at 2:11 AM, Dmitry Lazurkin  wrote:
>
> > Hello.
> >
> > Does it make sense to implement != restriction in select-where clause?
> > Is it possible?
> >
> > Thank you.
> >
> > PS. I want to implement that.
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> > For additional commands, e-mail: dev-h...@cassandra.apache.org
> >
> >
>

Re: NEQ-restriction in select-where clause

[Benjamin Lerer]

It can be done for filtering, otherwise it is really tricky (I am not even
sure it can be done to be honest).



On Sun, Sep 9, 2018 at 2:11 AM, Dmitry Lazurkin  wrote:

> Hello.
>
> Does it make sense to implement != restriction in select-where clause?
> Is it possible?
>
> Thank you.
>
> PS. I want to implement that.
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
>

RE: NEQ-restriction in select-where clause

[Jacques-Henri Berthemet]

Hi,

You can only use IF = or IF != on insert, update or delete statements, it does 
not work on select. When using it, it will create a LWT transaction and you'll 
need full PK in the where condition, you can apply the IF on values of the row. 
For example:

update table set type = 'somethingelse' where pk='42' if type != 'something';

--
Jacques-Henri Berthemet

-Original Message-
From: Dmitry Lazurkin  
Sent: Sunday, September 09, 2018 2:12 AM
To: dev@cassandra.apache.org
Subject: NEQ-restriction in select-where clause

Hello.

Does it make sense to implement != restriction in select-where clause?
Is it possible?

Thank you.

PS. I want to implement that.


-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org