Re: API for Cassandra CQL

[Benjamin Lerer]

Sorry,

This feature does not exist.

On Wed, Mar 29, 2017 at 3:13 AM, Ramesh Mani  wrote:

> Hello Cassandra team members,
>
> I am looking for API via which I can get the CQL session query as string?
> Is there a way I can get the Query executed by the users via API
>
> Thanks,
> Ramesh
>

[VOTE] self-assignment of jira tickets

[Jason Brown]

Hey all,

Following up on my emai

Re: [VOTE] self-assignment of jira tickets

[Jason Brown]

oops, hit sent too early. will send another email shortly

On Wed, Mar 29, 2017 at 6:14 AM, Jason Brown  wrote:

> Hey all,
>
> Following up on my emai
>

[VOTE] self-assignment of jira tickets

[Jason Brown]

Hey all,

Following up my thread from a week or two ago (
https://lists.apache.org/thread.html/0665f40c7213654e99817141972c003a2131aba7a1c63d6765db75c5@%3Cdev.cassandra.apache.org%3E),
I'd like to propose a vote to change to allow any potential contributor to
assign a jira to themselves without needing to be added to the contributors
group first.

https://issues.apache.org/jira/browse/INFRA-11950 is an example of how to
get this done with INFRA.

Vote will be open for 72 hours.

Thanks,

-Jason Brown

Re: [VOTE] self-assignment of jira tickets

[Jeremiah Jordan]

+1 non-binding. That requirement always seemed silly to me.

> On Mar 29, 2017, at 8:21 AM, Jason Brown  wrote:
> 
> Hey all,
> 
> Following up my thread from a week or two ago (
> https://lists.apache.org/thread.html/0665f40c7213654e99817141972c003a2131aba7a1c63d6765db75c5@%3Cdev.cassandra.apache.org%3E),
> I'd like to propose a vote to change to allow any potential contributor to
> assign a jira to themselves without needing to be added to the contributors
> group first.
> 
> https://issues.apache.org/jira/browse/INFRA-11950 is an example of how to
> get this done with INFRA.
> 
> Vote will be open for 72 hours.
> 
> Thanks,
> 
> -Jason Brown

Re: [VOTE] self-assignment of jira tickets

[Jeremy Hanna]

+1 non-binding.  I’ve always wondered why that restriction was in place.

> On Mar 29, 2017, at 8:21 AM, Jason Brown  wrote:
> 
> Hey all,
> 
> Following up my thread from a week or two ago (
> https://lists.apache.org/thread.html/0665f40c7213654e99817141972c003a2131aba7a1c63d6765db75c5@%3Cdev.cassandra.apache.org%3E),
> I'd like to propose a vote to change to allow any potential contributor to
> assign a jira to themselves without needing to be added to the contributors
> group first.
> 
> https://issues.apache.org/jira/browse/INFRA-11950 is an example of how to
> get this done with INFRA.
> 
> Vote will be open for 72 hours.
> 
> Thanks,
> 
> -Jason Brown

Re: [VOTE] self-assignment of jira tickets

[Robert Stupp]

non-binding +1, too.

—
Robert Stupp
@snazy

> On 29. Mar 2017, at 15:21, Jason Brown  wrote:
> 
> Hey all,
> 
> Following up my thread from a week or two ago (
> https://lists.apache.org/thread.html/0665f40c7213654e99817141972c003a2131aba7a1c63d6765db75c5@%3Cdev.cassandra.apache.org%3E),
> I'd like to propose a vote to change to allow any potential contributor to
> assign a jira to themselves without needing to be added to the contributors
> group first.
> 
> https://issues.apache.org/jira/browse/INFRA-11950 is an example of how to
> get this done with INFRA.
> 
> Vote will be open for 72 hours.
> 
> Thanks,
> 
> -Jason Brown



signature.asc
Description: Message signed with OpenPGP

Re: [VOTE] self-assignment of jira tickets

[Tommy Stendahl]

non-binding +1


On 2017-03-29 15:21, Jason Brown wrote:

Hey all,

Following up my thread from a week or two ago (
https://lists.apache.org/thread.html/0665f40c7213654e99817141972c003a2131aba7a1c63d6765db75c5@%3Cdev.cassandra.apache.org%3E),
I'd like to propose a vote to change to allow any potential contributor to
assign a jira to themselves without needing to be added to the contributors
group first.

https://issues.apache.org/jira/browse/INFRA-11950 is an example of how to
get this done with INFRA.

Vote will be open for 72 hours.

Thanks,

-Jason Brown

Re: [VOTE] self-assignment of jira tickets

[Jeff Jirsa]

+1

-- 
Jeff Jirsa


> On Mar 29, 2017, at 6:21 AM, Jason Brown  wrote:
> 
> Hey all,
> 
> Following up my thread from a week or two ago (
> https://lists.apache.org/thread.html/0665f40c7213654e99817141972c003a2131aba7a1c63d6765db75c5@%3Cdev.cassandra.apache.org%3E),
> I'd like to propose a vote to change to allow any potential contributor to
> assign a jira to themselves without needing to be added to the contributors
> group first.
> 
> https://issues.apache.org/jira/browse/INFRA-11950 is an example of how to
> get this done with INFRA.
> 
> Vote will be open for 72 hours.
> 
> Thanks,
> 
> -Jason Brown

Re: [VOTE] self-assignment of jira tickets

[Jonathan Haddad]

Non binding +1
On Wed, Mar 29, 2017 at 7:22 AM Jeff Jirsa  wrote:

> +1
>
> --
> Jeff Jirsa
>
>
> > On Mar 29, 2017, at 6:21 AM, Jason Brown  wrote:
> >
> > Hey all,
> >
> > Following up my thread from a week or two ago (
> >
> https://lists.apache.org/thread.html/0665f40c7213654e99817141972c003a2131aba7a1c63d6765db75c5@%3Cdev.cassandra.apache.org%3E
> ),
> > I'd like to propose a vote to change to allow any potential contributor
> to
> > assign a jira to themselves without needing to be added to the
> contributors
> > group first.
> >
> > https://issues.apache.org/jira/browse/INFRA-11950 is an example of how
> to
> > get this done with INFRA.
> >
> > Vote will be open for 72 hours.
> >
> > Thanks,
> >
> > -Jason Brown
>

Re: [VOTE] self-assignment of jira tickets

[Benjamin Lerer]

Non binding +1

On Wed, Mar 29, 2017 at 4:24 PM, Jonathan Haddad  wrote:

> Non binding +1
> On Wed, Mar 29, 2017 at 7:22 AM Jeff Jirsa  wrote:
>
> > +1
> >
> > --
> > Jeff Jirsa
> >
> >
> > > On Mar 29, 2017, at 6:21 AM, Jason Brown  wrote:
> > >
> > > Hey all,
> > >
> > > Following up my thread from a week or two ago (
> > >
> > https://lists.apache.org/thread.html/0665f40c7213654e99817141972c00
> 3a2131aba7a1c63d6765db75c5@%3Cdev.cassandra.apache.org%3E
> > ),
> > > I'd like to propose a vote to change to allow any potential contributor
> > to
> > > assign a jira to themselves without needing to be added to the
> > contributors
> > > group first.
> > >
> > > https://issues.apache.org/jira/browse/INFRA-11950 is an example of how
> > to
> > > get this done with INFRA.
> > >
> > > Vote will be open for 72 hours.
> > >
> > > Thanks,
> > >
> > > -Jason Brown
> >
>

Re: [VOTE] self-assignment of jira tickets

[Sylvain Lebresne]

+1

On Wed, Mar 29, 2017 at 4:42 PM, Benjamin Lerer  wrote:

> Non binding +1
>
> On Wed, Mar 29, 2017 at 4:24 PM, Jonathan Haddad 
> wrote:
>
> > Non binding +1
> > On Wed, Mar 29, 2017 at 7:22 AM Jeff Jirsa  wrote:
> >
> > > +1
> > >
> > > --
> > > Jeff Jirsa
> > >
> > >
> > > > On Mar 29, 2017, at 6:21 AM, Jason Brown 
> wrote:
> > > >
> > > > Hey all,
> > > >
> > > > Following up my thread from a week or two ago (
> > > >
> > > https://lists.apache.org/thread.html/0665f40c7213654e99817141972c00
> > 3a2131aba7a1c63d6765db75c5@%3Cdev.cassandra.apache.org%3E
> > > ),
> > > > I'd like to propose a vote to change to allow any potential
> contributor
> > > to
> > > > assign a jira to themselves without needing to be added to the
> > > contributors
> > > > group first.
> > > >
> > > > https://issues.apache.org/jira/browse/INFRA-11950 is an example of
> how
> > > to
> > > > get this done with INFRA.
> > > >
> > > > Vote will be open for 72 hours.
> > > >
> > > > Thanks,
> > > >
> > > > -Jason Brown
> > >
> >
>

Re: [VOTE] self-assignment of jira tickets

[Sankalp Kohli]

+1

> On Mar 29, 2017, at 07:50, Sylvain Lebresne  wrote:
> 
> +1
> 
> On Wed, Mar 29, 2017 at 4:42 PM, Benjamin Lerer > wrote:
> 
>> Non binding +1
>> 
>> On Wed, Mar 29, 2017 at 4:24 PM, Jonathan Haddad 
>> wrote:
>> 
>>> Non binding +1
 On Wed, Mar 29, 2017 at 7:22 AM Jeff Jirsa  wrote:
 
 +1
 
 --
 Jeff Jirsa
 
 
> On Mar 29, 2017, at 6:21 AM, Jason Brown 
>> wrote:
> 
> Hey all,
> 
> Following up my thread from a week or two ago (
> 
 https://lists.apache.org/thread.html/0665f40c7213654e99817141972c00
>>> 3a2131aba7a1c63d6765db75c5@%3Cdev.cassandra.apache.org%3E
 ),
> I'd like to propose a vote to change to allow any potential
>> contributor
 to
> assign a jira to themselves without needing to be added to the
 contributors
> group first.
> 
> https://issues.apache.org/jira/browse/INFRA-11950 is an example of
>> how
 to
> get this done with INFRA.
> 
> Vote will be open for 72 hours.
> 
> Thanks,
> 
> -Jason Brown
 
>>> 
>> 

Re: Proposal: push TravisCI and CircleCI yaml files into the active branches

[Ariel Weisberg]

Hi,

I think we should support something that we can scale out and that can
produce consistent reproducible results.

One of the longer term issues is going to be different CI systems
producing different sets of failures. It's not going to happen often but
it will and it's one way flakiness will sneak in.

There is an argument for settling on a single platform in that respect.
If queue time are an issue and we can get more resources running
multiple platforms then a different tradeoff will make sense.

I have a desire to run my own CI box that can parallelize with
containers, but I admit it's pretty niche use case and not worth much
investment or overhead.

Ariel

On Tue, Mar 28, 2017, at 08:52 PM, Jeff Jirsa wrote:
> To further our recent conversations on testing, I've opened the following
> JIRA:
> 
> https://issues.apache.org/jira/browse/CASSANDRA-13388
> 
> This should allow us to do SOME amount of automated testing for
> developers
> without jumping through a ton of hoops. If the free plans prove to be
> insufficient, we can look into using the ASF's paid plan, or find other
> solutions.
> 
> If anyone has a reason that they feel this is inappropriate, speak up.
> Otherwise, I'll try to put together a few yaml files this week to commit
> soon'ish.
> 
> Here's an example circle run that just kicks off unit tests on one of my
> personal branches - https://circleci.com/gh/jeffjirsa/cassandra/35 -
> nothing fancy, but at least it gives us the junit/testall run to show us
> that we had one failure ( testDroppedMessages -
> org.apache.cassandra.net.MessagingServiceTest ). It appears that we can
> parallelize dtests and run dtests as a series of small tasks as well - we
> may be able to get jacoco to run within the time limit, if we split up
> unit
> tests a bit.
> 
> We can have this conversation on the list or on the JIRA, but does anyone
> have a great reason why we SHOULDN'T support one or both of these
> vendors,
> or alternatively, is there another vendor we should consider instead?
> 
> - Jeff

Re: [VOTE] self-assignment of jira tickets

[Dave Lester]

Non-binding +1

On 2017-03-29 08:42 (-0700), Sankalp Kohli  wrote: 
> +1
> 
> > On Mar 29, 2017, at 07:50, Sylvain Lebresne  wrote:
> > 
> > +1
> > 
> > On Wed, Mar 29, 2017 at 4:42 PM, Benjamin Lerer  >> wrote:
> > 
> >> Non binding +1
> >> 
> >> On Wed, Mar 29, 2017 at 4:24 PM, Jonathan Haddad 
> >> wrote:
> >> 
> >>> Non binding +1
>  On Wed, Mar 29, 2017 at 7:22 AM Jeff Jirsa  wrote:
>  
>  +1
>  
>  --
>  Jeff Jirsa
>  
>  
> > On Mar 29, 2017, at 6:21 AM, Jason Brown 
> >> wrote:
> > 
> > Hey all,
> > 
> > Following up my thread from a week or two ago (
> > 
>  https://lists.apache.org/thread.html/0665f40c7213654e99817141972c00
> >>> 3a2131aba7a1c63d6765db75c5@%3Cdev.cassandra.apache.org%3E
>  ),
> > I'd like to propose a vote to change to allow any potential
> >> contributor
>  to
> > assign a jira to themselves without needing to be added to the
>  contributors
> > group first.
> > 
> > https://issues.apache.org/jira/browse/INFRA-11950 is an example of
> >> how
>  to
> > get this done with INFRA.
> > 
> > Vote will be open for 72 hours.
> > 
> > Thanks,
> > 
> > -Jason Brown
>  
> >>> 
> >> 
> 

Re: [VOTE] self-assignment of jira tickets

[Dave Brosius]

+1


On 2017-03-29 09:21, Jason Brown wrote:

Hey all,

Following up my thread from a week or two ago (
https://lists.apache.org/thread.html/0665f40c7213654e99817141972c003a2131aba7a1c63d6765db75c5@%3Cdev.cassandra.apache.org%3E),
I'd like to propose a vote to change to allow any potential contributor 
to
assign a jira to themselves without needing to be added to the 
contributors

group first.

https://issues.apache.org/jira/browse/INFRA-11950 is an example of how 
to

get this done with INFRA.

Vote will be open for 72 hours.

Thanks,

-Jason Brown

Re: [VOTE] self-assignment of jira tickets

[Michael Shuler]

+1

On 03/29/2017 08:21 AM, Jason Brown wrote:
> Hey all,
> 
> Following up my thread from a week or two ago (
> https://lists.apache.org/thread.html/0665f40c7213654e99817141972c003a2131aba7a1c63d6765db75c5@%3Cdev.cassandra.apache.org%3E),
> I'd like to propose a vote to change to allow any potential contributor to
> assign a jira to themselves without needing to be added to the contributors
> group first.
> 
> https://issues.apache.org/jira/browse/INFRA-11950 is an example of how to
> get this done with INFRA.
> 
> Vote will be open for 72 hours.
> 
> Thanks,
> 
> -Jason Brown
> 

Re: [VOTE] self-assignment of jira tickets

[Licata, Christopher]

+1

On 3/29/17, 2:52 PM, "Michael Shuler"  wrote:

+1

On 03/29/2017 08:21 AM, Jason Brown wrote:
> Hey all,
> 
> Following up my thread from a week or two ago (
> 
https://lists.apache.org/thread.html/0665f40c7213654e99817141972c003a2131aba7a1c63d6765db75c5@%3Cdev.cassandra.apache.org%3E),
> I'd like to propose a vote to change to allow any potential contributor to
> assign a jira to themselves without needing to be added to the 
contributors
> group first.
> 
> https://issues.apache.org/jira/browse/INFRA-11950 is an example of how to
> get this done with INFRA.
> 
> Vote will be open for 72 hours.
> 
> Thanks,
> 
> -Jason Brown
> 





The information contained in this e-mail is confidential and/or proprietary to 
Capital One and/or its affiliates and may only be used solely in performance of 
work or services for Capital One. The information transmitted herewith is 
intended only for use by the individual or entity to which it is addressed. If 
the reader of this message is not the intended recipient, you are hereby 
notified that any review, retransmission, dissemination, distribution, copying 
or other use of, or taking of any action in reliance upon this information is 
strictly prohibited. If you have received this communication in error, please 
contact the sender and delete the material from your computer.

Re: [VOTE] self-assignment of jira tickets

[Nate McCall]

+1

Re: [VOTE] self-assignment of jira tickets

[Aleksey Yeschenko]

+1 super binding.

-- 
AY

On 29 March 2017 at 16:22:03, Jason Brown (jasedbr...@gmail.com) wrote:

Hey all,  

Following up my thread from a week or two ago (  
https://lists.apache.org/thread.html/0665f40c7213654e99817141972c003a2131aba7a1c63d6765db75c5@%3Cdev.cassandra.apache.org%3E),
  
I'd like to propose a vote to change to allow any potential contributor to  
assign a jira to themselves without needing to be added to the contributors  
group first.  

https://issues.apache.org/jira/browse/INFRA-11950 is an example of how to  
get this done with INFRA.  

Vote will be open for 72 hours.  

Thanks,  

-Jason Brown  

Re: Code quality, principles and rules

[Edward Capriolo]

On Sat, Mar 18, 2017 at 9:21 PM, Qingcun Zhou  wrote:

> I wanted to contribute some unit test cases. However the unit test approach
> in Cassandra seems weird to me after looking into some examples. Not sure
> if anyone else has the same feeling.
>
> Usually, at least for all Java projects I have seen, people use mock
> (mockito, powermock) for dependencies. And then in a particular test case
> you verify the behavior using junit.assert* or mockito.verify. However we
> don't use mockito in Cassandra. Is there any reason for this? Without
> these, how easy do people think about adding unit test cases?
>
>
> Besides that, we have lots of singletons and there are already a handful of
> tickets to eliminate them. Maybe I missed something but I'm not seeing much
> progress. Is anyone actively working on this?
>
> Maybe a related problem. Some unit test cases have method annotated with
> @BeforeClass to do initialization work. However, it not only initializes
> direct dependencies, but also indirect ones, including loading
> cassandra.yaml and initializing indirect dependencies. This seems to me
> more like functional/integration test but not unit test style.
>
>
> On Fri, Mar 17, 2017 at 2:56 PM, Jeremy Hanna 
> wrote:
>
> > https://issues.apache.org/jira/browse/CASSANDRA-7837 may be some
> > interesting context regarding what's been worked on to get rid of
> > singletons and static initialization.
> >
> > > On Mar 17, 2017, at 4:47 PM, Jonathan Haddad 
> wrote:
> > >
> > > I'd like to think that if someone refactors existing code, making it
> more
> > > testable (with tests, of course) it should be acceptable on it's own
> > > merit.  In fact, in my opinion it sometimes makes more sense to do
> these
> > > types of refactorings for the sole purpose of improving stability and
> > > testability as opposed to mixing them with features.
> > >
> > > You referenced the issue I fixed in one of the early emails.  The fix
> > > itself was a couple lines of code.  Refactoring the codebase to make it
> > > testable would have been a huge effort.  I wish I had time to do it.  I
> > > created CASSANDRA-13007 as a follow up with the intent of working on
> > > compaction from a purely architectural standpoint.  I think this type
> of
> > > thing should be done throughout the codebase.
> > >
> > > Removing the singletons is a good first step, my vote is we just rip
> off
> > > the bandaid, do it, and move forward.
> > >
> > > On Fri, Mar 17, 2017 at 2:20 PM Edward Capriolo  >
> > > wrote:
> > >
> > >>> On Fri, Mar 17, 2017 at 2:31 PM, Jason Brown 
> > wrote:
> > >>>
> > >>> To François's point about code coverage for new code, I think this
> > makes
> > >> a
> > >>> lot of sense wrt large features (like the current work on
> > >> 8457/12229/9754).
> > >>> It's much simpler to (mentally, at least) isolate those changed
> > sections
> > >>> and it'll show up better in a code coverage report. With small
> patches,
> > >>> that might be harder to achieve - however, as the patch should come
> > with
> > >>> *some* tests (unless it's a truly trivial patch), it might just work
> > >> itself
> > >>> out.
> > >>>
> > >>> On Fri, Mar 17, 2017 at 11:19 AM, Jason Brown 
> > >>> wrote:
> > >>>
> >  As someone who spent a lot of time looking at the singletons topic
> in
> > >> the
> >  past, Blake brings a great perspective here. Figuring out and
> > >>> communicating
> >  how best to test with the system we have (and of course
> incrementally
> >  making that system easier to work with/test) seems like an
> achievable
> > >>> goal.
> > 
> >  On Fri, Mar 17, 2017 at 10:17 AM, Edward Capriolo <
> > >> edlinuxg...@gmail.com
> > 
> >  wrote:
> > 
> > > On Fri, Mar 17, 2017 at 12:33 PM, Blake Eggleston <
> > >> beggles...@apple.com
> > 
> > > wrote:
> > >
> > >> I think we’re getting a little ahead of ourselves talking about DI
> > >> frameworks. Before that even becomes something worth talking
> about,
> > >>> we’d
> > >> need to have made serious progress on un-spaghettifying Cassandra
> in
> > >>> the
> > >> first place. It’s an extremely tall order. Adding a DI framework
> > >> right
> > > now
> > >> would be like throwing gasoline on a raging tire fire.
> > >>
> > >> Removing singletons seems to come up every 6-12 months, and
> usually
> > >> abandoned once people figure out how difficult they are to remove
> > > properly.
> > >> I do think removing them *should* be a long term goal, but we
> really
> > > need
> > >> something more immediately actionable. Otherwise, nothing’s going
> to
> > >> happen, and we’ll be having this discussion again in a year or so
> > >> when
> > >> everyone’s angry that Cassandra 5.0 still isn’t ready for
> > >> production,
> > >>> a
> > >> year after it’s release.
> > >>
> > >> That said, the reason singletons regularly get brought up is
> because
> > > doing
> > >> extensive te

Re: [VOTE] self-assignment of jira tickets

[Ben Bromhead]

+1 nb

On Wed, 29 Mar 2017 at 12:20 Aleksey Yeschenko  wrote:

> +1 super binding.
>
> --
> AY
>
> On 29 March 2017 at 16:22:03, Jason Brown (jasedbr...@gmail.com) wrote:
>
> Hey all,
>
> Following up my thread from a week or two ago (
>
> https://lists.apache.org/thread.html/0665f40c7213654e99817141972c003a2131aba7a1c63d6765db75c5@%3Cdev.cassandra.apache.org%3E
> ),
> I'd like to propose a vote to change to allow any potential contributor to
> assign a jira to themselves without needing to be added to the contributors
> group first.
>
> https://issues.apache.org/jira/browse/INFRA-11950 is an example of how to
> get this done with INFRA.
>
> Vote will be open for 72 hours.
>
> Thanks,
>
> -Jason Brown
>
-- 
Ben Bromhead
CTO | Instaclustr 
+1 650 284 9692
Managed Cassandra / Spark on AWS, Azure and Softlayer