Re: Time for a new 3.0/3.11 release?

2019-07-02 Thread Sam Tunnicliffe
It would also be good to include CASSANDRA-15193 (which I only just created, sorry), as the counterpart to CASSANDRA-15176. I have a patch for this mostly done and will post it in the next day or two. > On 2 Jul 2019, at 07:13, Mick Semb Wever wrote: > >> It would be nice to have time to get

Re: Java8 compatibility broken in 4.0

2019-06-11 Thread Sam Tunnicliffe
> On 11 Jun 2019, at 10:04, Tommy Stendahl wrote: > > Hi, > > I can't find a way to build 4.0 artifacts so I can run Cassandra using Java8. > Building the artifacts ("ant artifacts" or "ant mvn-install") requires > building with Java11 but since CASSANDRA-15108 the result is not Java8 >

Re: Jira Suggestion

2019-05-15 Thread Sam Tunnicliffe
+1 > On 14 May 2019, at 20:10, Benedict Elliott Smith wrote: > > It will be possible to insert n/a. It will simply be a text field - Jira > doesn’t know anything about the concept of a SHA, and I don’t intend to > introduce validation logic. It’s just a logical and consistent place for it

Re: Stabilising Internode Messaging in 4.0

2019-04-12 Thread Sam Tunnicliffe
+1 Thanks for articulating that so well Josh. Sam > On 12 Apr 2019, at 16:19, Blake Eggleston > wrote: > > Well said Josh. You’ve pretty much summarized my thoughts on this as well. > > +1 to moving forward with this > >> On Apr 11, 2019, at 10:15 PM, Joshua McKenzie wrote: >> >> As one

Re: Cassandra Integrated Auth for JMX

2019-01-21 Thread Sam Tunnicliffe
The built-in Cassandra auth for JMX works at the connector (i.e. RMI) level. If you try a direct JMX connection, such as jconsole, you should see the Cassandra access controls being enforced. As I understand it, Jolokia bypasses the connectors and so this auth config has no effect. In fact,

Re: Git Repo Migration

2019-01-09 Thread Sam Tunnicliffe
11:48, Sam Tunnicliffe wrote: > > https://issues.apache.org/jira/browse/INFRA-17593 > <https://issues.apache.org/jira/browse/INFRA-17593> > > Thanks, > Sam > >> On 4 Jan 2019, at 21:43, Jonathan Haddad wrote: >> >> Great news, we can also rem

Re: Git Repo Migration

2019-01-09 Thread Sam Tunnicliffe
gt;> >> On 1/4/19 2:00 PM, Jonathan Haddad wrote: >>> Silence can be interpreted either as non-awareness or implicit approval. >>> >>> I interpreted (and meant) +1 as "go for it now". >>> >>> On Fri, Jan 4, 2019 at 8:48 AM Sam Tunnicliffe wro

Re: Git Repo Migration

2019-01-04 Thread Sam Tunnicliffe
Let's do it Monday, for example, and we can work through > the config changes while most people are fresh from a break. > > The longer we wait, the more things people have in flight and they get > bothered about being interrupted. Just interrupt ASAP, IMO. > > Michael > >

Git Repo Migration

2019-01-04 Thread Sam Tunnicliffe
As per the announcement on 7th December 2018[1], ASF infra are planning to shutdown the service behind git-wip-us.apache.org and migrate all existing repos to gitbox.apache.org There are further details in the original mail, but apparently one of the benefits of the migration is that we'll

Re: [VOTE] Change Jira Workflow

2018-12-18 Thread Sam Tunnicliffe
+1 On Tue, 18 Dec 2018 at 13:47, Joshua McKenzie wrote: > +1 > > On Tue, Dec 18, 2018 at 7:30 AM Aleksey Yeshchenko > wrote: > > > Sure, +1 > > > > > On 18 Dec 2018, at 09:42, Joseph Lynch wrote: > > > > > > +1 non-binding > > > > > > On Tue, Dec 18, 2018 at 1:15 AM Sylvain Lebresne > >

Re: JIRA Workflow Proposals

2018-12-12 Thread Sam Tunnicliffe
1: D C B A E 2: B C A 3: A 4: -1 (get rid of Wish entirely) Thanks, Sam > On 11 Dec 2018, at 22:01, Joseph Lynch wrote: > > Just my 2c > > 1. D C B E A > 2. B, C, A > 3. A > 4. +0.5 > > -Joey > > On Tue, Dec 11, 2018 at 8:28 AM Benedict Elliott Smith > wrote: > >> Just to re-summarise

Re: JIRA Workflow Proposals

2018-12-06 Thread Sam Tunnicliffe
1: A 2: +1 3: +1 4: +1 5: +0 6: +1 On the question of keeping the contributors-only restriction on moving from Triage->Open, I tend to agree with Benedict that a low barrier can be useful in deterring bogus transitions (accidental or malicious) which keeps the general noise down. I’m thinking

Request for post-freeze merge exception

2018-09-04 Thread Sam Tunnicliffe
Hey all, On 2018-31-08 CASSANDRA-14145 had been +1'd by two reviewers and CI was green, and so it was marked Ready To Commit. This was before the 4.0 feature freeze but before it landed, CASSANDRA-14408, which touched a few common areas of the code, was merged. I didn't have chance to finish the

Re: Side Car New Repo vs not

2018-08-24 Thread Sam Tunnicliffe
+1 for a separate repo On Fri, 24 Aug 2018 at 06:40, Michael Shuler wrote: > +1 for a separate repository. > > Michael > > On 08/23/2018 07:30 PM, Murukesh Mohanan wrote: > > FWIW, I think it's possible to merge in a separate repository into a > > subdirectory while keeping git history, but I

Re: [VOTE] Release Apache Cassandra 2.2.13

2018-07-26 Thread Sam Tunnicliffe
+1 On 25 July 2018 at 08:17, Michael Shuler wrote: > I propose the following artifacts for release as 2.2.13. > > sha1: 3482370df5672c9337a16a8a52baba53b70a4fe8 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/2.2.13-tentative > Artifacts: >

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

2018-07-26 Thread Sam Tunnicliffe
+1 On 25 July 2018 at 08:16, Michael Shuler wrote: > I propose the following artifacts for release as 3.11.3. > > sha1: 31d5d870f9f5b56391db46ba6cdf9e0882d8a5c0 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/3.11.3-tentative > Artifacts: >

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

2018-07-26 Thread Sam Tunnicliffe
+1 On 25 July 2018 at 08:17, Michael Shuler wrote: > I propose the following artifacts for release as 3.0.17. > > sha1: d52c7b8c595cc0d06fc3607bf16e3f595f016bb6 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/3.0.17-tentative > Artifacts: >

Re: [VOTE] Branching Change for 4.0 Freeze

2018-07-12 Thread Sam Tunnicliffe
+1 On 12 July 2018 at 08:49, Mick Semb Wever wrote: > > > Vote will be open for 72 hours. > > > +1 (non-binding) > > - > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail:

Re: Testing 4.0 Post-Freeze

2018-07-10 Thread Sam Tunnicliffe
+1 here too On Tue, 10 Jul 2018 at 18:52, Marcus Eriksson wrote: > +1 here as well > > On Tue, Jul 10, 2018 at 7:06 PM Aleksey Yeshchenko > wrote: > > > +1 from me too. > > > > — > > AY > > > > On 10 July 2018 at 04:17:26, Mick Semb Wever (m...@apache.org) wrote: > > > > > > > We have done all

Re: [VOTE] Release Apache Cassandra 3.11.3

2018-07-03 Thread Sam Tunnicliffe
-1 I think CASSANDRA-14252 should be reverted from 3.0 & 3.11, at least the effect on streaming is verified. The concern is that the snitch change could make cross DC streaming more likely. I’ve opened CASSANDRA-14555 for this. On 3 July 2018 at 04:02, Nate McCall wrote: > +1 > > On Tue, Jul

Re: [VOTE] Release Apache Cassandra 3.0.13

2017-04-13 Thread Sam Tunnicliffe
> > One dtest failed on the standard and "novnode" jobs, which we > have an existing JIRA for, CASSANDRA-13113 The initial dtest failure that 13113 was opened for is not worth blocking the release for IMO. In the comments of that ticket, Alex has identified a more pressing, user facing

Re: [VOTE] Release Apache Cassandra 3.10 (Take 3)

2016-11-25 Thread Sam Tunnicliffe
I'll register another (non-binding) -1 due to the failing tests. In particular, CASSANDRA-12651 is due to a legit bug with potential corruption and data loss (albeit in indexes only). The same bug is also the likely cause of CASSANDRA-12590, so it'd be good to include the fix in 3.10. On Mon, Nov

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

2016-11-09 Thread Sam Tunnicliffe
-1 from me too due to #12877. I also agree with Alex's suggestion of reverting #11990 and re-rolling. On Wed, Nov 9, 2016 at 1:20 PM, Oleksandr Petrov wrote: > -1 > > Sorry but I have to -1 that one, with the following explanation > > One of the features in 3.10

Re: [VOTE] Release Apache Cassandra 3.8

2016-09-27 Thread Sam Tunnicliffe
+1 On Mon, Sep 26, 2016 at 3:52 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.8. > > sha1: ce609d19fd130e16184d9e6d37ffee4a1ebad607 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/3.8-tentative >

Re: [VOTE] Release Apache Cassandra 3.9

2016-09-27 Thread Sam Tunnicliffe
+1 On Mon, Sep 26, 2016 at 4:12 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.9. > > sha1: c1fa21458777b51a9b21795330ed6f298103b436 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/3.9-tentative >

Re: [VOTE] Release Apache Cassandra 3.0.9

2016-09-15 Thread Sam Tunnicliffe
+1 On 15 Sep 2016 19:58, "Jake Luciani" wrote: > I propose the following artifacts for release as 3.0.9. > > sha1: d600f51ee1a3eb7b30ce3c409129567b70c22012 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/3.0.9-tentative > Artifacts: >

Re: Failing tests 2016-08-22 [cassandra-3.9]

2016-08-23 Thread Sam Tunnicliffe
I've opened https://issues.apache.org/jira/browse/CASSANDRA-12523 for the new flaky failure. Thanks, Sam On Tue, Aug 23, 2016 at 6:44 AM, Joel Knighton wrote: > === > testall: All passed! > >

Re: [VOTE] Release Apache Cassandra 2.2.7

2016-07-01 Thread Sam Tunnicliffe
+1 On Fri, Jul 1, 2016 at 3:58 PM, Jake Luciani wrote: > I propose the following artifacts for release as 2.2.7. > > sha1: 092054170ec3daf92ec494a0db295037d3563229 > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.7-tentative >

Re: [VOTE] Release Apache Cassandra 2.1.15

2016-07-01 Thread Sam Tunnicliffe
+1 On Fri, Jul 1, 2016 at 4:44 PM, Jonathan Ellis wrote: > +1 on the release, but let's get those fixed for next time. > > On Thu, Jun 30, 2016 at 6:02 PM, Dave Brosius > wrote: > > > nits > > > > snappy-java and thrift-server's license files have

Re: [VOTE] Release Apache Cassandra 3.0.8

2016-07-01 Thread Sam Tunnicliffe
+1 On Fri, Jul 1, 2016 at 4:40 PM, Jake Luciani wrote: > I propose the following artifacts for release as 3.0.8. > > sha1: 8b21d9e9e975ea07023ae6ec4c04d997006c1a0a > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.8-tentative >

Re: Error running 'ant test'

2016-05-19 Thread Sam Tunnicliffe
CassandraIndexTest is intermittently failing on trunk & 3.0 at the moment: http://cassci.datastax.com/view/trunk/job/trunk_utest/1378/testReport/ http://cassci.datastax.com/view/cassandra-3.0/job/cassandra-3.0_utest/747/testReport/ On Thu, May 19, 2016 at 3:24 PM, Oleksandr Petrov <

Re: [VOTE] Release Apache Cassandra 3.6

2016-05-11 Thread Sam Tunnicliffe
+1 On Wed, May 11, 2016 at 9:51 AM, Aleksey Yeschenko wrote: > +1 > > -- > AY > > On 11 May 2016 at 02:55:10, Jake Luciani (j...@apache.org) wrote: > > I propose the following artifacts for release as 3.6. > > sha1: c17cbe1875a974a00822ffbfad716abde363c8da > Git: > >

Re: [VOTE] Release Apache Cassandra 3.0.6

2016-05-11 Thread Sam Tunnicliffe
+1 On Wed, May 11, 2016 at 9:51 AM, Aleksey Yeschenko wrote: > +1 > > -- > AY > > On 11 May 2016 at 02:55:11, Jake Luciani (j...@apache.org) wrote: > > I propose the following artifacts for release as 3.0.6. > > sha1: 52447873a361647a5e80c547adea9cf5ee85254a > Git: > >

Re: TTL rows with 2i

2016-03-09 Thread Sam Tunnicliffe
checked the only two calls to Indexer.removeRows in > o.a.c.index.SecondaryIndexManager.IndexGCTransaction.commit in the > followings releases and it seems that has not changed at all. > > Sam Tunnicliffe, any ideas about this?? > > Regards > > > Eduardo Alonso > Vía d

Re: Custom Java class for secondary index implementation

2016-03-06 Thread Sam Tunnicliffe
You might find o.a.c.i.StubIndex in the test source tree useful. On 6 Mar 2016 19:24, "Henry Manasseh" wrote: > Hello, > I was wondering if anyone is aware of a minimal reference implementation > for a java class implementing a secondary index or some documentation of >

Re: [VOTE] Release Apache Cassandra 3.3

2016-02-06 Thread Sam Tunnicliffe
+1 On Sat, Feb 6, 2016 at 3:11 AM, Jake Luciani wrote: > I propose the following artifacts for release as 3.3. > > sha1: 5669c6967bbdd540f27aeebf5a2c258bc4defbe3 > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.3-tentative > Artifacts:

Re: [VOTE] Release Apache Cassandra 2.1.13

2016-02-03 Thread Sam Tunnicliffe
+1 On Wed, Feb 3, 2016 at 1:44 PM, Jake Luciani wrote: > I propose the following artifacts for release as 2.1.13. > > sha1: d5b6d1b634f69709d2b3caa17cba52696ed2033d > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.13-tentative >

Re: [VOTE] Release Apache Cassandra 2.2.5

2016-02-03 Thread Sam Tunnicliffe
+1 On Wed, Feb 3, 2016 at 1:51 PM, Jake Luciani wrote: > I propose the following artifacts for release as 2.2.5. > > sha1: dd76858c7652541c7b137323f7b9e154686d6fba > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.5-tentative >

Re: [VOTE] Release Apache Cassandra 3.2.1

2016-01-15 Thread Sam Tunnicliffe
+1 On Fri, Jan 15, 2016 at 3:03 AM, Jake Luciani wrote: > I propose the following artifacts for release as 3.2.1. > > sha1: 2ac95bd6c5699a605e6f4256cb17b016c99e6dda > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.2.1-tentative >

Re: [VOTE] Release Apache Cassandra 3.0.1

2015-12-07 Thread Sam Tunnicliffe
+1 I propose the following artifacts for release as 3.0.1. sha1: cf567703db2cc6859731405322f19f55345b5c57 Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.1-tentative Artifacts:

Re: [VOTE] Release Apache Cassandra 3.1

2015-12-07 Thread Sam Tunnicliffe
+1 On 4 Dec 2015 22:07, "Jake Luciani" wrote: > I propose the following artifacts for release as 3.1. > > sha1: e092873728dc88aebc6ee10153b9bd3cd90cd858 > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.1-tentative > Artifacts: > >

PerRowSecondaryIndex

2012-05-26 Thread Sam Tunnicliffe
I'm looking at https://issues.apache.org/jira/browse/CASSANDRA-2897 and poking around in the secondary indexes code, I see PerRowSecondaryIndex. I found some relevant JIRAs [1][2][3] but can anyone point me towards implementations which extend this abstract class? Cheers, Sam