Re: Java Driver 3.0 for Apache Cassandra - Documentation Outdated?

[Sylvain Lebresne]

On Tue, Jun 7, 2016 at 1:50 AM, Chris Mattmann  wrote:

> Excellent, why am I the first person to ask that, and why didn’t
> a PMC member point that out right away and why did it take me asking
> to point to the Apache docs.
>
> This is what I am talking about in terms of the Apache community..
>

You seem to have make your mind on the Cassandra PMC doing a poor
job so you'll probably consider my response as just proof of how bad we are
(since I'm PMC), but I genuinely fail to see what you think was wrong on the
answer given by Nate to this original email. I mean, that original email is
very
explicitly asking a question about the DataStax java driver documentation,
which as we've established is not part of the Cassandra, and Nate helpfully
explained that fact. So I'm curious as to what else you would have wanted
us the PMC to point out as response to that initial email so we can do
better
next time.

Or, to answer your question more directly, no PMC member pointed right
away to the CQL documentation as response to Madhi original email because
his question was not about CQL, it was about the DataStax Java driver.

--
Sylvain


>
>
>
>
>
> On 6/6/16, 4:47 PM, "Michael Kjellman" 
> wrote:
>
> >http://cassandra.apache.org/doc/cql3/CQL.html
> >
> >On Jun 6, 2016, at 4:42 PM, Mattmann, Chris A (3980) <
> chris.a.mattm...@jpl.nasa.gov>
> wrote:
> >
> >Hi,
> >
> >So, the core documentation for a key part of Cassandra is hosted
> >at DataStax?
> >
> >Cheers,
> >Chris
> >
> >++
> >Chris Mattmann, Ph.D.
> >Chief Architect
> >Instrument Software and Science Data Systems Section (398)
> >NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> >Office: 168-519, Mailstop: 168-527
> >Email: chris.a.mattm...@nasa.gov
> >WWW:  http://sunset.usc.edu/~mattmann/
> >++
> >Director, Information Retrieval and Data Science Group (IRDS)
> >Adjunct Associate Professor, Computer Science Department
> >University of Southern California, Los Angeles, CA 90089 USA
> >WWW: http://irds.usc.edu/
> >++
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >On 6/6/16, 7:32 AM, "Mahdi Mohammadi" > wrote:
> >
> >Team,
> >
> >I was checking the documentation for TupleType in DataStax docs here
> ><
> https://docs.datastax.com/en/latest-java-driver/java-driver/reference/tupleTypes.html
> >
> >and
> >the code example was like this:
> >
> >TupleType theType = TupleType.of(DataType.cint(), DataType.text(),
> >DataType.cfloat());
> >
> >
> >But in the code, the *TupleType.of* has two additional parameters not
> >mentioned in the documentation:
> >
> >
> >*public static TupleType of(ProtocolVersion protocolVersion, CodecRegistry
> >codecRegistry, DataType... types)*
> >
> >Maybe I am looking in the wrong place. Could someone please explain how
> can
> >I instantiate a *TupleType*?
> >
> >I have the same question for *Map* type.
> >
> >Thanks for your help.
> >
> >===
> >Best Regards
> >
>
>

Gossip Behavioral Difference between C* 2.0 and C* 2.1

[Michael Fong]

Hi,

We recently discovered that there are some differences in gossip behavior 
between C* 2.0 and C* 2.1. In some cases of network instability or a node 
reboot, we can observe some behavioral differences from Cassandra/system.log.

2.0.17
We can observe this log of similar pattern in log :
DEBUG [RequestResponseStage:3] 2016-04-19 11:18:18,332 Gossiper.java (line 977) 
removing expire time for endpoint : /192.168.88.34
INFO [RequestResponseStage:3] 2016-04-19 11:18:18,333 Gossiper.java (line 978) 
InetAddress /192.168.88.34 is now UP
DEBUG [RequestResponseStage:4] 2016-04-19 11:18:18,335 Gossiper.java (line 977) 
removing expire time for endpoint : /192.168.88.34
INFO [RequestResponseStage:4] 2016-04-19 11:18:18,335 Gossiper.java (line 978) 
InetAddress /192.168.88.34 is now UP
DEBUG [RequestResponseStage:3] 2016-04-19 11:18:18,335 Gossiper.java (line 977) 
removing expire time for endpoint : /192.168.88.34
INFO [RequestResponseStage:3] 2016-04-19 11:18:18,335 Gossiper.java (line 978) 
InetAddress /192.168.88.34 is now UP


It seems the longer for the node to regain connection (or reboot), the more 
accumulated gossip message, and the more gossip message will appear afterwards.

However,  in 2.1, we do not observe this kind of behavior any more. There seems 
to be some fundamental changes on gossip protocol. Did anyone also observe the 
similar pattern, or could kindly point out which changes (JIRA #) that made of 
this improvement?

Thanks in advanced!

Sincerely,

Michael Fong

Re: Cassandra Java Driver and DataStax

[Pavel Yaskevich]

Hi Chris,

   On a similar note to what Andres mentioned, me and couple of other
people have recently contributed index implementation (SASI), which
significantly extends
   indexing capabilities of Apache Cassandra, and might be one of the
biggest changes to the database in years.
   I'm a member of PMC for the project and I am not affiliated with
DataStax and although SASI introduces conflict of interests with DSE,
   similar (if not greater) to the work Andres is doing at Stratio, I have
only received positive feedback and help from development community -
people helped to review changes, added new features, contributed tests,
   wrote blog posts about it, organized meetups etc.

Best Regards, Pavel.


On Mon, Jun 6, 2016 at 4:43 PM, Chris Mattmann  wrote:

> Thanks Jonathan.
>
> I have seen several people replying back and citing general
> technical benefits again to having different drivers hosted
> elsewhere. I have also seen people say, “well it’s ALv2
> and open source, so people can fork it and blah and blah”.
>
> “Opensource” and “ALv2” don’t necessarily a community make and
> I think that point is a little lost amongst people who are
> part of this Apache PMC.
>
> Thanks for being willing to update the report as I asked and
> I look forward to your thoughts and the community thinking
> on this and reviewing it with my board hat on.
>
> Cheers,
> Chris
>
>
>
>
> On 6/6/16, 3:19 PM, "Jonathan Ellis"  wrote:
>
> >I’m happy to consult with my peers in other projects for the board report
> >and summarize their ideas and Cassandra PMC's to improve contributor
> >diversity.  I’ll plan to attend the meeting in person to discuss this
> >further.
> >
> >On Sun, Jun 5, 2016 at 5:33 PM, Mattmann, Chris A (3980) <
> >chris.a.mattm...@jpl.nasa.gov> wrote:
> >
> >> Thanks for the info Jonathan. I think have assessed based on
> >> the replies thus far, my studying of the archives and
> >> commit and project history the following situation.
> >>
> >> Unfortunately it seems like there is a bit of control going on
> >> I’m going to call a spade a spade here. A key portion of your
> >> software’s stack, a client driver to use it, exists outside of
> >> Apache in separate communities. This is an inherent risk to the
> >> project. Some of you cite flexibility and adaptability as reasons
> >> for this - I’ve seen it in so many communities over the last 12+
> >> years in the foundation - it’s not really due to those issues.
> >> There is definitely some control going on. I would ask you all
> >> this - has there been a PR or patch in the past year or two that
> >> wasn’t singularly reviewed by DataStax committers and PMC? Also,
> >> as to the composition of the PMC when was the last time a non
> >> DataStax person was elected to the PMC and/or as a committer?
> >>
> >> By itself the diversity issues alone are not damning to the
> >> project, but taken together with the citation to other project
> >> communities even those outside of Apache (e.g., the comments
> >> well “Postgres does it this way, so it’s a good example to
> >> compare us to” or “these other 4 projects at the ASF do it
> >> like this, so X”.. [sic]) and with the perception being created
> >> to those that don’t work at DataStax, and there is an issue here.
> >>
> >> I would like to see a discussion in your next board report about
> >> the diversity and health issues of the project, and also some
> >> ideas about potential strategies for mitigation.
> >>
> >> I appreciate the open and honest conversation thus far. Let’s
> >> keep it up.
> >>
> >> Cheers,
> >> Chris
> >>
> >> ++
> >> Chris Mattmann, Ph.D.
> >> Chief Architect
> >> Instrument Software and Science Data Systems Section (398)
> >> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> >> Office: 168-519, Mailstop: 168-527
> >> Email: chris.a.mattm...@nasa.gov
> >> WWW:  http://sunset.usc.edu/~mattmann/
> >> ++
> >> Director, Information Retrieval and Data Science Group (IRDS)
> >> Adjunct Associate Professor, Computer Science Department
> >> University of Southern California, Los Angeles, CA 90089 USA
> >> WWW: http://irds.usc.edu/
> >> ++
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> On 6/5/16, 1:51 PM, "Jonathan Ellis"  wrote:
> >>
> >> >On Sun, Jun 5, 2016 at 8:32 AM, Mattmann, Chris A (3980) <
> >> >chris.a.mattm...@jpl.nasa.gov> wrote:
> >> >
> >> >> 1. Is Apache Cassandra useful *without* a driver? That is, can
> >> >> you use the database without a driver to connect to it or in the
> >> >> real world would your users all have to download at least one
> >> >> driver in order to use the DB?
> >> >>
> >> >
> >> >The users do need to download a driver--but this is pretty normal for
> >> >community-driven OSS databases.  Besides the 

Re: Java Driver 3.0 for Apache Cassandra - Documentation Outdated?

[Chris Mattmann]

It’s not about whether DataStax has great documentation or not. 
That’s fine - it’s about the perception of the *first* place to
look for that documentation. If someone came to Apache OODT, 
Nutch, Tika, Lucene, Spark, etc., and we had great documentation 
at JPL to go along with these, as a PMC member for these projects
I would first point to the ASF documentation, or I would work to
make sure the ASF documentation got a look and set of updates 
first. Point them at the company docs, fine, but make sure the ASF
docs are also great as a priority.




On 6/6/16, 4:57 PM, "Michael Kjellman"  wrote:

>I think it comes down to having full time tech writers employed and paid. If 
>Datastax has the $$ to provide a significant benefit to the community (well 
>thought out documentation) that's better than little or no documentation (if 
>it was only done via developers who most likely won't document or do a poor 
>job at documentation).
>
>Having some documentation is much better for the community than the 
>alternative that "the code is the documentation".
>
>Nothing is free.
>
>On Jun 6, 2016, at 4:50 PM, Chris Mattmann 
>> wrote:
>
>Excellent, why am I the first person to ask that, and why didn’t
>a PMC member point that out right away and why did it take me asking
>to point to the Apache docs.
>
>This is what I am talking about in terms of the Apache community..
>
>
>
>
>
>On 6/6/16, 4:47 PM, "Michael Kjellman" 
>> wrote:
>
>http://cassandra.apache.org/doc/cql3/CQL.html
>
>On Jun 6, 2016, at 4:42 PM, Mattmann, Chris A (3980) 
>> wrote:
>
>Hi,
>
>So, the core documentation for a key part of Cassandra is hosted
>at DataStax?
>
>Cheers,
>Chris
>
>++
>Chris Mattmann, Ph.D.
>Chief Architect
>Instrument Software and Science Data Systems Section (398)
>NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>Office: 168-519, Mailstop: 168-527
>Email: chris.a.mattm...@nasa.gov
>WWW:  http://sunset.usc.edu/~mattmann/
>++
>Director, Information Retrieval and Data Science Group (IRDS)
>Adjunct Associate Professor, Computer Science Department
>University of Southern California, Los Angeles, CA 90089 USA
>WWW: http://irds.usc.edu/
>++
>
>
>
>
>
>
>
>
>
>
>On 6/6/16, 7:32 AM, "Mahdi Mohammadi" 
>> wrote:
>
>Team,
>
>I was checking the documentation for TupleType in DataStax docs here
>
>and
>the code example was like this:
>
>TupleType theType = TupleType.of(DataType.cint(), DataType.text(),
>DataType.cfloat());
>
>
>But in the code, the *TupleType.of* has two additional parameters not
>mentioned in the documentation:
>
>
>*public static TupleType of(ProtocolVersion protocolVersion, CodecRegistry
>codecRegistry, DataType... types)*
>
>Maybe I am looking in the wrong place. Could someone please explain how can
>I instantiate a *TupleType*?
>
>I have the same question for *Map* type.
>
>Thanks for your help.
>
>===
>Best Regards
>
>
>

Re: Java Driver 3.0 for Apache Cassandra - Documentation Outdated?

[Michael Kjellman]

I think it comes down to having full time tech writers employed and paid. If 
Datastax has the $$ to provide a significant benefit to the community (well 
thought out documentation) that's better than little or no documentation (if it 
was only done via developers who most likely won't document or do a poor job at 
documentation).

Having some documentation is much better for the community than the alternative 
that "the code is the documentation".

Nothing is free.

On Jun 6, 2016, at 4:50 PM, Chris Mattmann 
> wrote:

Excellent, why am I the first person to ask that, and why didn’t
a PMC member point that out right away and why did it take me asking
to point to the Apache docs.

This is what I am talking about in terms of the Apache community..





On 6/6/16, 4:47 PM, "Michael Kjellman" 
> wrote:

http://cassandra.apache.org/doc/cql3/CQL.html

On Jun 6, 2016, at 4:42 PM, Mattmann, Chris A (3980) 
> wrote:

Hi,

So, the core documentation for a key part of Cassandra is hosted
at DataStax?

Cheers,
Chris

++
Chris Mattmann, Ph.D.
Chief Architect
Instrument Software and Science Data Systems Section (398)
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 168-519, Mailstop: 168-527
Email: chris.a.mattm...@nasa.gov
WWW:  http://sunset.usc.edu/~mattmann/
++
Director, Information Retrieval and Data Science Group (IRDS)
Adjunct Associate Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
WWW: http://irds.usc.edu/
++










On 6/6/16, 7:32 AM, "Mahdi Mohammadi" 
> wrote:

Team,

I was checking the documentation for TupleType in DataStax docs here

and
the code example was like this:

TupleType theType = TupleType.of(DataType.cint(), DataType.text(),
DataType.cfloat());


But in the code, the *TupleType.of* has two additional parameters not
mentioned in the documentation:


*public static TupleType of(ProtocolVersion protocolVersion, CodecRegistry
codecRegistry, DataType... types)*

Maybe I am looking in the wrong place. Could someone please explain how can
I instantiate a *TupleType*?

I have the same question for *Map* type.

Thanks for your help.

===
Best Regards

Re: Java Driver 3.0 for Apache Cassandra - Documentation Outdated?

[Chris Mattmann]

Excellent, why am I the first person to ask that, and why didn’t
a PMC member point that out right away and why did it take me asking
to point to the Apache docs.

This is what I am talking about in terms of the Apache community..





On 6/6/16, 4:47 PM, "Michael Kjellman"  wrote:

>http://cassandra.apache.org/doc/cql3/CQL.html
>
>On Jun 6, 2016, at 4:42 PM, Mattmann, Chris A (3980) 
>> wrote:
>
>Hi,
>
>So, the core documentation for a key part of Cassandra is hosted
>at DataStax?
>
>Cheers,
>Chris
>
>++
>Chris Mattmann, Ph.D.
>Chief Architect
>Instrument Software and Science Data Systems Section (398)
>NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>Office: 168-519, Mailstop: 168-527
>Email: chris.a.mattm...@nasa.gov
>WWW:  http://sunset.usc.edu/~mattmann/
>++
>Director, Information Retrieval and Data Science Group (IRDS)
>Adjunct Associate Professor, Computer Science Department
>University of Southern California, Los Angeles, CA 90089 USA
>WWW: http://irds.usc.edu/
>++
>
>
>
>
>
>
>
>
>
>
>On 6/6/16, 7:32 AM, "Mahdi Mohammadi" 
>> wrote:
>
>Team,
>
>I was checking the documentation for TupleType in DataStax docs here
>
>and
>the code example was like this:
>
>TupleType theType = TupleType.of(DataType.cint(), DataType.text(),
>DataType.cfloat());
>
>
>But in the code, the *TupleType.of* has two additional parameters not
>mentioned in the documentation:
>
>
>*public static TupleType of(ProtocolVersion protocolVersion, CodecRegistry
>codecRegistry, DataType... types)*
>
>Maybe I am looking in the wrong place. Could someone please explain how can
>I instantiate a *TupleType*?
>
>I have the same question for *Map* type.
>
>Thanks for your help.
>
>===
>Best Regards
>

Re: Java Driver 3.0 for Apache Cassandra - Documentation Outdated?

[Mattmann, Chris A (3980)]

Hi,

So, the core documentation for a key part of Cassandra is hosted
at DataStax?

Cheers,
Chris

++
Chris Mattmann, Ph.D.
Chief Architect
Instrument Software and Science Data Systems Section (398)
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 168-519, Mailstop: 168-527
Email: chris.a.mattm...@nasa.gov
WWW:  http://sunset.usc.edu/~mattmann/
++
Director, Information Retrieval and Data Science Group (IRDS)
Adjunct Associate Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
WWW: http://irds.usc.edu/
++










On 6/6/16, 7:32 AM, "Mahdi Mohammadi"  wrote:

>Team,
>
>I was checking the documentation for TupleType in DataStax docs here
>
>and
>the code example was like this:
>
>TupleType theType = TupleType.of(DataType.cint(), DataType.text(),
>DataType.cfloat());
>
>
>But in the code, the *TupleType.of* has two additional parameters not
>mentioned in the documentation:
>
>
>*public static TupleType of(ProtocolVersion protocolVersion, CodecRegistry
>codecRegistry, DataType... types)*
>
>Maybe I am looking in the wrong place. Could someone please explain how can
>I instantiate a *TupleType*?
>
>I have the same question for *Map* type.
>
>Thanks for your help.
>
>===
>Best Regards

Re: Java Driver 3.0 for Apache Cassandra - Documentation Outdated?

[Nate McCall]

Thanks for bringing this up, but the Java Driver is a separate project
maintained here:
https://github.com/datastax/java-driver

with it's own mailing list:
https://groups.google.com/a/lists.datastax.com/forum/#!forum/java-driver-user

Documentation for the driver is also maintained by the community in-tree:
https://github.com/datastax/java-driver/tree/3.0/manual




On Mon, Jun 6, 2016 at 9:32 AM, Mahdi Mohammadi  wrote:

> Team,
>
> I was checking the documentation for TupleType in DataStax docs here
> <
> https://docs.datastax.com/en/latest-java-driver/java-driver/reference/tupleTypes.html
> >
> and
> the code example was like this:
>
> TupleType theType = TupleType.of(DataType.cint(), DataType.text(),
> DataType.cfloat());
>
>
> But in the code, the *TupleType.of* has two additional parameters not
> mentioned in the documentation:
>
>
> *public static TupleType of(ProtocolVersion protocolVersion, CodecRegistry
> codecRegistry, DataType... types)*
>
> Maybe I am looking in the wrong place. Could someone please explain how can
> I instantiate a *TupleType*?
>
> I have the same question for *Map* type.
>
> Thanks for your help.
>
> ===
> Best Regards
>



-- 
-
Nate McCall
Austin, TX
@zznate

CTO
Apache Cassandra Consulting
http://www.thelastpickle.com

Re: Cassandra Java Driver and DataStax

[Jeremy Hanna]

> On Jun 5, 2016, at 4:33 PM, Mattmann, Chris A (3980) 
>  wrote:
> 
> Thanks for the info Jonathan. I think have assessed based on
> the replies thus far, my studying of the archives and
> commit and project history the following situation.
> 
> Unfortunately it seems like there is a bit of control going on
> I’m going to call a spade a spade here. A key portion of your 
> software’s stack, a client driver to use it, exists outside of
> Apache in separate communities. This is an inherent risk to the
> project. Some of you cite flexibility and adaptability as reasons
> for this - I’ve seen it in so many communities over the last 12+
> years in the foundation - it’s not really due to those issues.

Not all open-source projects do well under the apache umbrella in my opinion.  
Additionally not all library dependencies for all apache projects come from 
apache.

> There is definitely some control going on.

One thing I like about the ASF is that it’s about contribution and meritocracy. 
 If you have a company that is devoted to making a project successful, you’ll 
have more contribution from them.  Some people will gravitate to work for that 
company because they are passionate about the project and working there allows 
them to spend more time on it than they would have been able to at other 
companies.  And yet there are several committers and PMC members that don’t 
work for DataStax who have an influence over its development.  I think you may 
mean control in terms of contribution as you talk about in your next questions. 
 If that’s the case, how do you get other people to contribute more?  DataStax 
has already sponsored several contributor bootcamps for instance.  If it’s 
about contribution and meritocracy, is there an instance where a contribution 
was not accepted because of where an individual was employed?  Is there an 
instance where someone wasn’t accepted as a contributor or committer or pmc 
member because of where they worked?  Several of those committers/PMC members 
who are currently at DataStax became committers/PMC members before joining 
DataStax.  I’m just trying to understand the nature of where you see a problem.

> I would ask you all
> this - has there been a PR or patch in the past year or two that
> wasn’t singularly reviewed by DataStax committers and PMC? Also,
> as to the composition of the PMC when was the last time a non 
> DataStax person was elected to the PMC and/or as a committer?
> 
> By itself the diversity issues alone are not damning to the 
> project, but taken together with the citation to other project
> communities even those outside of Apache (e.g., the comments
> well “Postgres does it this way, so it’s a good example to
> compare us to” or “these other 4 projects at the ASF do it 
> like this, so X”.. [sic]) and with the perception being created
> to those that don’t work at DataStax, and there is an issue here.

I don’t quite understand the thinking here - referencing how successful 
open-source projects operate (outside the asf) is damning?  Mentioning that 
Cassandra is not unique within Apache to have client drivers outside of the 
main project is damning?  I don’t understand why that either of those would be 
in any way negative or invalid.

Regarding the thread generally, I still haven’t seen 1) an instance where 
having client drivers developed outside of the core project being a problem or 
2) an example where employees of datastax exerted control over the project to 
the detriment of others or 3) an example of anyone in the community saying 
“yeah, you’re right, they do control stuff and it sucks.”

Personally, I would like to see more specific concrete evidence of a problem.  
I’ve been involved with the project since 0.6 and it’s always had a very open 
and active community complete with ideas, disagreements, and mistakes.  Take 
for example CASSANDRA-9666 where the best time series compaction strategy 
alternatives are discussed.  It was determined that a community contribution 
from a third party company was going to supersede/replace what was in the tree. 
 If there are specific concerns, I think everyone involved in the project would 
like to know.

> 
> I would like to see a discussion in your next board report about
> the diversity and health issues of the project, and also some 
> ideas about potential strategies for mitigation. 
> 
> I appreciate the open and honest conversation thus far. Let’s
> keep it up.
> 
> Cheers,
> Chris
> 
> ++
> Chris Mattmann, Ph.D.
> Chief Architect
> Instrument Software and Science Data Systems Section (398)
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 168-519, Mailstop: 168-527
> Email: chris.a.mattm...@nasa.gov
> WWW:  http://sunset.usc.edu/~mattmann/
> ++
> Director, Information Retrieval and Data Science Group (IRDS)
> Adjunct 

3.7 and 3.0.7 frozen

[Jake Luciani]

These releases have been tentatively frozen and tagged for testing

[RELEASE] Apache Cassandra 3.6 released

[Jake Luciani]

The Cassandra team is pleased to announce the release of Apache Cassandra
version 3.6.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a tick-tock feature release[1] on the 3.x series. As
always, please pay
attention to the release notes[2] and Let us know[3] if you were to
encounter
any problem.

Enjoy!

[1]: http://goo.gl/eu90nx (CHANGES.txt)
[2]: http://goo.gl/ugkBQW (NEWS.txt)
[3]: https://issues.apache.org/jira/browse/CASSANDRA

Re: Cassandra Java Driver and DataStax

[Brandon Williams]

On Sun, Jun 5, 2016 at 3:20 PM, Mattmann, Chris A (3980) <
chris.a.mattm...@jpl.nasa.gov> wrote:

> #1 - a driver is needed to use Apache Cassandra right? As in, you
> wouldn’t expect users of Apache Cassandra to get the database core
> from the ASF, and then use it without a driver (from somewhere else?)
>

I need a browser to use Apache HTTPD, right?

[VOTE RESULT] Release Apache Cassandra 3.6 (Attempt #2)

[Jake Luciani]

With 6 binding +1, 6 non-binding +1 and no -1 the vote passes.



On Fri, Jun 3, 2016 at 4:02 AM, Benjamin Lerer 
wrote:

> +1
>
> On Wed, Jun 1, 2016 at 7:30 PM, Jake Luciani  wrote:
>
> > I propose the following artifacts for release as 3.6.
> >
> > sha1: 8d22d9fd1842c59ea65a3793aceb5a78c5852351
> > Git:
> >
> >
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.6-tentative
> > Artifacts:
> >
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1114/org/apache/cassandra/apache-cassandra/3.6/
> > Staging repository:
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1114/
> >
> > The artifacts as well as the debian package are also available here:
> > http://people.apache.org/~jake
> >
> > The vote will be open for 72 hours (longer if needed).
> >
> > [1]: http://goo.gl/lg9U9a (CHANGES.txt)
> > [2]: http://goo.gl/nyDyxk (NEWS.txt)
> > [3]: https://goo.gl/hNyrnW (DataStax QA Report)
> >
>



-- 
http://twitter.com/tjake

Re: Cassandra Java Driver and DataStax

[Eric Stevens]

> A key portion of your software’s stack, a client driver to use it, exists
outside of Apache in separate communities. This is an inherent risk to the
project.

That's not at all obvious to me.  The driver you're concerned about is not
under ASF, but it is Apache licensed, if DataStax took it in a direction
unfavorable to the community, the community would be able to just fork it.
Your concern here seems mostly to be surrounding one project vs two.  At
worst this is a layout concern.

> I would ask you all this - has there been a PR or patch in the past year
or two that wasn’t singularly reviewed by DataStax committers and PMC?

There are numerous non-PMC non-DataStax committers.  Regardless, this is
the wrong question to ask.  The question is not how well reviewed the code
is and whether there are a tight set of gate keepers, but rather whether
there are contributions being rejected which would advance the product in a
material way, but are being rejected by reviewers due to, for example, a
conflict of interest.

> Does anyone in the community see this “controlling” behavior going on?
... Thanks for any help you can provide in rooting this out.
> ...
> Unfortunately it seems like there is a bit of control going on...There is
definitely some control going on

You asked the community for feedback on this, and it was pretty clear to me
that nobody here felt like that was the case.

If you're aware of *actual* examples of impropriety in this or another
sense, I think the community would like to hear about it.  Something more
substantial than vague assertions and hand waving.  However, claiming
repeatedly that you see control going on, but without something to
substantiate the accusation feels like an expedition fishing for drama.

On Mon, Jun 6, 2016 at 5:36 AM Jeremiah D Jordan 
wrote:

> The Apache Cassandra project has always left development of its drivers up
> to the community.  The DataStax Java Driver is not part of the Apache
> Cassandra project, it is an open source project created by DataStax.  You
> can find a large list of drivers for Cassandra here:
> https://wiki.apache.org/cassandra/ClientOptions some of them developed by
> DataStax, some developed by Netflix, and many others.
>
> -Jeremiah
>
> > On Jun 3, 2016, at 9:29 PM, Chris Mattmann  wrote:
> >
> > Hi All,
> >
> > I’m investigating something a few ASF members contacted
> > me about and pointed out, so I’m hoping you can help
> > guide me here as a community. I have heard that a company,
> > DataStax, whose marketing material mentions it as the only
> > Cassandra vendor, “controls” the Java Driver for Apache
> > Cassandra.
> >
> > Of course, no company “controls” our projects or its code,
> > so I told the folks that mentioned it to me that I’d investigate
> > with my board hat on.
> >
> > I’d like to hear the community’s thoughts here on this. Does
> > anyone in the community see this “controlling” behavior going
> > on? Please speak up, as I’d like to get to the bottom of it,
> > and I’ll be around on the lists, doing some homework and reading
> > up on the archives to see what’s up.
> >
> > Thanks for any help you can provide in rooting this out.
> >
> > Cheers,
> > Chris
> >
> >
> >
> >
>
>

Re: Cassandra Java Driver and DataStax

[Jeremiah D Jordan]

The Apache Cassandra project has always left development of its drivers up to 
the community.  The DataStax Java Driver is not part of the Apache Cassandra 
project, it is an open source project created by DataStax.  You can find a 
large list of drivers for Cassandra here: 
https://wiki.apache.org/cassandra/ClientOptions some of them developed by 
DataStax, some developed by Netflix, and many others.

-Jeremiah

> On Jun 3, 2016, at 9:29 PM, Chris Mattmann  wrote:
> 
> Hi All,
> 
> I’m investigating something a few ASF members contacted
> me about and pointed out, so I’m hoping you can help 
> guide me here as a community. I have heard that a company,
> DataStax, whose marketing material mentions it as the only
> Cassandra vendor, “controls” the Java Driver for Apache 
> Cassandra. 
> 
> Of course, no company “controls” our projects or its code,
> so I told the folks that mentioned it to me that I’d investigate
> with my board hat on.
> 
> I’d like to hear the community’s thoughts here on this. Does
> anyone in the community see this “controlling” behavior going
> on? Please speak up, as I’d like to get to the bottom of it,
> and I’ll be around on the lists, doing some homework and reading
> up on the archives to see what’s up.
> 
> Thanks for any help you can provide in rooting this out.
> 
> Cheers,
> Chris
> 
> 
> 
>