Re: JIRA Label for Client-Impacting Changes/Decisions

2014-12-16 Thread Tyler Hobbs
+1 on starting a new label. Feel free to start labelling. Other tickets that should be labelled: * https://issues.apache.org/jira/browse/CASSANDRA-7536 * https://issues.apache.org/jira/browse/CASSANDRA-7523 Note: I also created https://issues.apache.org/jira/browse/CASSANDRA-8495 to document typ

Re: JIRA Label for Client-Impacting Changes/Decisions

2014-12-16 Thread Adam Holmberg
I think the issue that brought this up was more about collection serialization. Since collections existed before v3, it was surprising to see outer collections serialized with one format and inner with another. I'm not questioning that decision, nor do I want to operate in 'undocumented territory'

Re: JIRA Label for Client-Impacting Changes/Decisions

2014-12-16 Thread Sylvain Lebresne
We already try to use labels (though we definitively haven't always done it in the past): all protocolv4 stuffs should have a protocolv4 label, and I'm all for continuing to stick to it. I'm fine having an additional "driver impacting" tag for stuff that are likely to need special driver handling (

Re: JIRA Label for Client-Impacting Changes/Decisions

2014-12-16 Thread Aleksey Yeschenko
A label works for me. But we also need a separate .txt file, or a section in NEWS.txt, for those who can’t, or don’t want to follow the JIRA. Can’t realistically expect people to do that. --  AY On December 16, 2014 at 8:15:43 PM, Tyler Hobbs (ty...@datastax.com) wrote: I'm personally in favo

Re: unable to get saved data after successfully calling batch_mutate

2014-12-16 Thread Tyler Hobbs
This user mailing list (u...@cassandra.apache.org) is a better place for this. The dev mailing list is for committers and others working on Cassandra itself. On Fri, Dec 12, 2014 at 5:02 PM, cong.ling wrote: > Hi, > I met an issue that cassendra can't save some data, but can save others. > I ca

Re: JIRA Label for Client-Impacting Changes/Decisions

2014-12-16 Thread Tyler Hobbs
I'm personally in favor of using a label. Besides myself, Sylvain, Benjamin, and Aleksey are probably the most likely to be keeping track of this. Any objections or alternatives from you guys? On Fri, Dec 12, 2014 at 5:41 PM, Adam Holmberg wrote: > As a Cassandra driver developer, I'm looking

Re: incrementally acquiring tokens

2014-12-16 Thread Tyler Hobbs
On Sat, Dec 13, 2014 at 11:33 AM, Jonathan Haddad wrote: > > As a potential approach, would it be possible for a node to incrementally > acquire tokens, and as a result incrementally stream? You could have a > node serving requests after acquiring 1 token, and it would gradually take > ownership