Re: [VOTE] Release Apache Cassandra 3.0.10 (Take 2)

2016-11-10 Thread Tommy Stendahl
+1 (non-binding) On 2016-11-08 21:08, Michael Shuler wrote: I propose the following artifacts for release as 3.0.10. sha1: 4e0bced5e6a82ebd22b074b8ef96d930c5f3159d Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.10-tentative Artifacts:

Re: Broader community involvement in 4.0 (WAS Re: Rough roadmap for 4.0)

2016-11-10 Thread Jeremy Hanna
Regarding low hanging fruit, on the How To Contribute page [1] we’ve tried to keep a list of lhf tickets [2] linked to help people get started. They are usually good starting points and don’t require much context. I rarely see duplicates from lhf tickets. Regarding duplicates, in my

spark-cassandra-connector support for Spark 2.0.1 Structured Streaming

2016-11-10 Thread shyla deshpande
Hello everyone, Anyone able to use Cassandra with structured streaming. Please help Thanks

Re: Broader community involvement in 4.0 (WAS Re: Rough roadmap for 4.0)

2016-11-10 Thread Anuj Wadehra
Hi, We need to understand that time is precious for all of us. Even if a developer has intentions to contribute, he may take months to contribute his first patch or may be longer. Some common entry barriers are: 1. Difficult to identify low hanging fruits. 30 JIRA comments on a ticket and a

[GitHub] cassandra issue #83: 12796 2.2

2016-11-10 Thread ifesdjeen
Github user ifesdjeen commented on the issue: https://github.com/apache/cassandra/pull/83 Cassandra does't take pull requests via github (as the primary repository is hosted elsewhere), you have to create an issue and submit a patch via

[GitHub] cassandra pull request #83: 12796 2.2

2016-11-10 Thread mmajercik
GitHub user mmajercik opened a pull request: https://github.com/apache/cassandra/pull/83 12796 2.2 This is a proposed patch for CASSANDRA-12796 You can merge this pull request into a Git repository by running: $ git pull https://github.com/mmajercik/cassandra 12796-2.2

[GitHub] cassandra pull request #82: 12796 2.2

2016-11-10 Thread mmajercik
Github user mmajercik closed the pull request at: https://github.com/apache/cassandra/pull/82 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[GitHub] cassandra issue #82: 12796 2.2

2016-11-10 Thread ifesdjeen
Github user ifesdjeen commented on the issue: https://github.com/apache/cassandra/pull/82 It looks like the branch is based on top of Cassandra trunk rather than current apollo master. --- If your project is set up for it, you can reply to this email and have your reply appear on

[GitHub] cassandra pull request #82: 12796 2.2

2016-11-10 Thread mmajercik
GitHub user mmajercik opened a pull request: https://github.com/apache/cassandra/pull/82 12796 2.2 This is a proposed fix for CASSANDRA-12796 You can merge this pull request into a Git repository by running: $ git pull https://github.com/mmajercik/cassandra 12796-2.2