[VOTE] Release Apache Cassandra 3.5 (Attempt #2)
I propose the following artifacts for release as 3.5. sha1: 020dd2d1034abc5c729edf1975953614b33c5a8b Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.5-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1106/org/apache/cassandra/apache-cassandra/3.5/ Staging repository: https://repository.apache.org/content/repositories/orgapachecassandra-1106/ 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/v1sH4v (CHANGES.txt) [2]: http://goo.gl/ZlHf5z (NEWS.txt)
max_mutation_size_in_kb addition not noted in CHANGES.txt
I don't find mention of max_mutation_size_in_kb in CHANGES.txt, but I do see it mentioned for 3.0.0 in NEWS.txt. It doesn't have (DataStax) doc either. It looks like it was added on 8/19/2015: "patch by Aleksey Yeschenko; reviewed by Benedict Elliott Smith for CASSANDRA-6230": https://github.com/apache/cassandra/commit/96d41f0e0e44d9b3114a5d80dedf12053d36a76b#diff-b66584c9ce7b64019b5db5a531deeda1 It probably should be (or have been) added to CHANGES.txt as well. I do see that comments on this was added to the yaml file on 10/2/2015 as part of: https://issues.apache.org/jira/browse/CASSANDRA-10256 -- Jack Krupansky
Re: [VOTE] Release Apache Cassandra 3.5 (Attempt #2)
+1 On Sun, Apr 10, 2016 at 10:43 AM, Jake Luciani wrote: > I propose the following artifacts for release as 3.5. > > sha1: 020dd2d1034abc5c729edf1975953614b33c5a8b > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.5-tentative > Artifacts: > > https://repository.apache.org/content/repositories/orgapachecassandra-1106/org/apache/cassandra/apache-cassandra/3.5/ > Staging repository: > https://repository.apache.org/content/repositories/orgapachecassandra-1106/ > > 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/v1sH4v (CHANGES.txt) > [2]: http://goo.gl/ZlHf5z (NEWS.txt) >
Re: [VOTE] Release Apache Cassandra 3.5 (Attempt #2)
+1 On 10 Apr 2016 19:54, "Brandon Williams" wrote: > +1 > > On Sun, Apr 10, 2016 at 10:43 AM, Jake Luciani wrote: > > > I propose the following artifacts for release as 3.5. > > > > sha1: 020dd2d1034abc5c729edf1975953614b33c5a8b > > Git: > > > > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.5-tentative > > Artifacts: > > > > > https://repository.apache.org/content/repositories/orgapachecassandra-1106/org/apache/cassandra/apache-cassandra/3.5/ > > Staging repository: > > > https://repository.apache.org/content/repositories/orgapachecassandra-1106/ > > > > 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/v1sH4v (CHANGES.txt) > > [2]: http://goo.gl/ZlHf5z (NEWS.txt) > > >
Criteria for upgrading to 3.x releases in PROD
Hi, Tick-Tock release strategy in 3.x was a good intiative to ensure frequent & stable releases. While odd releases are supposed to get all the bug fixes and should be most stable, many people like me, who got used to the comforting "production ready/stable" tag on Apache website, are still reluctant to take latest 3.x odd releases into production. I think the hesitation is somewhat justified as processes often take time to mature. So here I would like to ask the experts, people who know the ground situation, people who actively develop it and manage it. Considering the current scenario, What should be a resonable criteria for taking 3.x releases in production? ThanksAnuj
Re: [VOTE] Release Apache Cassandra 3.5 (Attempt #2)
+1 > On Apr 10, 2016, at 9:52 AM, Codarren Velvindron wrote: > > +1 >> On 10 Apr 2016 19:54, "Brandon Williams" wrote: >> >> +1 >> >>> On Sun, Apr 10, 2016 at 10:43 AM, Jake Luciani wrote: >>> >>> I propose the following artifacts for release as 3.5. >>> >>> sha1: 020dd2d1034abc5c729edf1975953614b33c5a8b >>> Git: >> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.5-tentative >>> Artifacts: >> https://repository.apache.org/content/repositories/orgapachecassandra-1106/org/apache/cassandra/apache-cassandra/3.5/ >>> Staging repository: >> https://repository.apache.org/content/repositories/orgapachecassandra-1106/ >>> >>> 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/v1sH4v (CHANGES.txt) >>> [2]: http://goo.gl/ZlHf5z (NEWS.txt) >>
Re: [VOTE] Release Apache Cassandra 3.5 (Attempt #2)
+1 On Sun, Apr 10, 2016 at 10:43 AM, Jake Luciani wrote: > I propose the following artifacts for release as 3.5. > > sha1: 020dd2d1034abc5c729edf1975953614b33c5a8b > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.5-tentative > Artifacts: > > https://repository.apache.org/content/repositories/orgapachecassandra-1106/org/apache/cassandra/apache-cassandra/3.5/ > Staging repository: > https://repository.apache.org/content/repositories/orgapachecassandra-1106/ > > 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/v1sH4v (CHANGES.txt) > [2]: http://goo.gl/ZlHf5z (NEWS.txt) > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Typo in CommitLog.java: maxiumum s.b. maximum
I was baffled why I couldn't find a user's reported log message of
"Mutation 32MB too large for maximum size of 16Mb" even when I searched
GitHub for "too large for maximum size". The reason my search failed was
that the user (or their email client) must have corrected the typo in the
message that the code actually produces - the code has the text "too large
for the maxiumum size", when "maxiumum" should be "maximum".
In CommitLog.java, the current code in the add method in trunk:
if (totalSize > MAX_MUTATION_SIZE)
{
throw new IllegalArgumentException(String.format("Mutation of
%s is too large for the maxiumum size of %s",
FBUtilities.prettyPrintMemory(totalSize),
FBUtilities.prettyPrintMemory(MAX_MUTATION_SIZE)));
}
The corrected code:
if (totalSize > MAX_MUTATION_SIZE)
{
throw new IllegalArgumentException(String.format("Mutation of
%s is too large for the maximum size of %s",
FBUtilities.prettyPrintMemory(totalSize),
FBUtilities.prettyPrintMemory(MAX_MUTATION_SIZE)));
}
-- Jack Krupansky
clustering columns IN relations when a collection is selected?
I am trying to understand the rationale for preventing IN relations when a collection is selected. Cassandra produces this error message: *"InvalidRequest: code=2200 [Invalid query] message="Cannot restrict clustering columns by IN relations when a collection is selected by the query"* Is this something people are open to relaxing in the future? Or is there a reason for preventing it. It seems that if the users provide a constraint on the partitioning key then this query could be efficient. It would also eliminate the element of surprise for new adopters. [image: Inline image 1] Thank you, Henry
[VOTE RESULT] Release Apache Cassandra 3.0.5
With 6 binding +1 and 3 non binding +1 the and no -1 the vote passes. I will publish On Fri, Apr 8, 2016 at 12:41 PM, Josh McKenzie wrote: > +1 > > On Thu, Apr 7, 2016 at 6:10 PM, Jake Luciani wrote: > > > I propose the following artifacts for release as 3.0.5. > > > > sha1: c6e6fa94d28c0d23a8154e3743c05b355dba710a > > Git: > > > > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.5-tentative > > Artifacts: > > > > > https://repository.apache.org/content/repositories/orgapachecassandra-1104/org/apache/cassandra/apache-cassandra/3.0.5/ > > Staging repository: > > > https://repository.apache.org/content/repositories/orgapachecassandra-1104/ > > > > 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/f2b0Di (CHANGES.txt) > > [2]: http://goo.gl/bHIeYj (NEWS.txt) > > [3]: https://goo.gl/noLkHT (DataStax Test Report) > > > -- http://twitter.com/tjake
