Re: [VOTE] remove the old wiki

2019-06-04 Thread Ben Bromhead
you only need couple pages, feel free to move the content to the > > documentation. I'm sure we can also export the wiki in its entirety and > > put it somewhere offline, if there's a concern about maybe needing some > of > > the content at some point in the future. > &g

Re: [VOTE] Change Jira Workflow

2018-12-17 Thread Ben Bromhead
be on vacation. > > Everyone is welcome to ignore the result until I get back in a couple of > > weeks, or if anybody is eager feel free to close the vote and take some > > steps towards implementation. > > > > > > > > > --

Re: CASSANDRA-13241 lower default chunk_length_in_kb

2018-10-11 Thread Ben Bromhead
hey are directly related. > > I'll wait a week for discussion and if there is consensus make the change. > > Regards, > Ariel > > - > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For addition

Re: [VOTE] Accept GoCQL driver donation and begin incubation process

2018-09-12 Thread Ben Bromhead
> >>> > > > >> > > > > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__incubator.apache.org_guides_ip-5Fclearance.html=DwIFAg=adz96Xi0w1RHqtPMowiL2g=CNZK3RiJDLqhsZDG6FQGnXn8WyPRCQhp4x_uBICNC0g=g-MlYFZVJ7j5Dj_ZfPfa0Ik8Nxco7QsJhTG1TnJH7xI=rk5T_t1HZY6PAhN5XgflBhfEtNrcZkVTIvQxixDlw9o= > > > >>>>>> > > > >>>>>> Pending the outcome of this vote, we will create the JIRA issues > > for > > > >>>>>> tracking and after we go through the process, and discuss adding > > > >>>>>> committers in a separate thread (we need to do this atomically > > > >> anyway > > > >>>>>> per general ASF committer adding processes). > > > >>>>>> > > > >>>>>> Thanks, > > > >>>>>> -Nate > > > >>>>>> > > > >>>>>> > > > >> > - > > > >>>>>> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > > > >>>>>> For additional commands, e-mail: dev-h...@cassandra.apache.org > > > >>>>>> > > > >>>>> > > > >>>>> > > - > > > >>>>> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > > > >>>>> For additional commands, e-mail: dev-h...@cassandra.apache.org > > > >>>>> > > > >>>> > > > >>>> > > > >>>> > > - > > > >>>> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > > > >>>> For additional commands, e-mail: dev-h...@cassandra.apache.org > > > >>>> > > > >>>> > > > >>> > > > >> > > > > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > > > For additional commands, e-mail: dev-h...@cassandra.apache.org > > > > > > > > > > > -- > Jon Haddad > http://www.rustyrazorblade.com > twitter: rustyrazorblade > -- Ben Bromhead CTO | Instaclustr <https://www.instaclustr.com/> +1 650 284 9692 Reliability at Scale Cassandra, Spark, Elasticsearch on AWS, Azure, GCP and Softlayer

Re: NGCC 2018?

2018-09-10 Thread Ben Bromhead
e > > > > may > > > > > also be able to provide space in bay area and help to organize it. > > > > (Please > > > > > let us know, so we could get final approval for that). > > > > > > > > > > On Fri, Jul 27, 2018 at

Re: NGCC 2018?

2018-07-26 Thread Ben Bromhead
; > > > Nate, now that I've spoken for you, you can clarify, :D > > > > Patrick > > > > - > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > > -- Ben Bromhead CTO | I

Re: NGCC 2018?

2018-07-24 Thread Ben Bromhead
t; > On Mon, Jul 23, 2018 at 2:25 PM Ben Bromhead wrote: > > > The year has gotten away from us a little bit, but now is as good a time > as > > any to put out a general call for interest in an NGCC this year. > > > > Last year Gary and Eric did an awesome job orga

NGCC 2018?

2018-07-23 Thread Ben Bromhead
other sponsors (doesn't have to be monetary, can be space, resource etc) who want to get involved? If folks are generally happy with the end approach we'll post details as soon as possible (given its July right now)! Ben -- Ben Bromhead CTO | Instaclustr <https://www.instaclustr.com/> +1 6

Re: [VOTE] Branching Change for 4.0 Freeze

2018-07-13 Thread Ben Bromhead
t;> > > >> Vote will be open for 72 hours. > > >> > > >> Thanks, > > >> Sankalp > > >> > > >> [1] > > >> > > >> https://lists.apache.org/thread.html/494c3ced9e83ceeb53fa127e44eec6 > > e2588a01b769896b25867fd59f@%3Cdev.cassandra.apache.org%3E > > >> > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > > For additional commands, e-mail: dev-h...@cassandra.apache.org > > > > > -- Ben Bromhead CTO | Instaclustr <https://www.instaclustr.com/> +1 650 284 9692 Reliability at Scale Cassandra, Spark, Elasticsearch on AWS, Azure, GCP and Softlayer

Re: Testing 4.0 Post-Freeze

2018-07-10 Thread Ben Bromhead
, moving us towards an eventual goal of not needing to > feature-freeze at all. > > regards, > Mick > > - > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: Evolving the client protocol

2018-04-23 Thread Ben Bromhead
gt;> On Apr 22, 2018, at 8:26 AM, Avi Kivity <a...@scylladb.com> wrote: > >> > >> > >> > >>> On 2018-04-19 21:15, Ben Bromhead wrote: > >>> Re #3: > >>> > >>> Yup I was thinking each shard/port would appear a

Re: Evolving the client protocol

2018-04-19 Thread Ben Bromhead
ose > > packets delivered directly to the core that will service them. > > > > > > (also, some protocol changes are needed so the driver knows how tokens > > are distributed among shards) > > > > On 2018-04-19 19:46, Ben Bromhead wrote: > > > WRT to #3 &

Re: Evolving the client protocol

2018-04-19 Thread Ben Bromhead
ss of how they may look like. > > > > > > > > Do we have driver authors who wish to support both projects? > > > > > > Surely, but I imagine it would be a minority. ​ > > > > > > > -------

Re: Roadmap for 4.0

2018-04-12 Thread Ben Bromhead
I would also suggest if you can't commit to June 2 due to timing or feature set. If you could provide the absolute minimum date / features that would let you commit to testing, that would be useful. On Thu, Apr 12, 2018 at 3:49 PM Ben Bromhead <b...@instaclustr.com> wrote: > We (In

Re: Roadmap for 4.0

2018-04-12 Thread Ben Bromhead
;> Totally possible that there exist people who are willing and able to > find > >> and fix those bugs, who just haven't committed to it in this thread. > >> That's > >> probably why Sankalp keeps asking who's actually willing to do the > testing > >> on June 2 - if nobody's going to commit to doing real testing on June 2, > >> all we're doing is adding inconvenience to those of us who'd be willing > to > >> do it later in the year. > >> > > > -- Ben Bromhead CTO | Instaclustr <https://www.instaclustr.com/> +1 650 284 9692 Reliability at Scale Cassandra, Spark, Elasticsearch on AWS, Azure, GCP and Softlayer

Re: Roadmap for 4.0

2018-04-11 Thread Ben Bromhead
new stuff, and things we've gotten close on can still go in 4.0 > > > (Virtual tables). I guess I'm asking here if we want to > disambiguate > > > "feature freeze" from "branch point?" I feel like this makes sense. > > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > > > For additional commands, e-mail: dev-h...@cassandra.apache.org > > > > > > > > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > > -- Ben Bromhead CTO | Instaclustr <https://www.instaclustr.com/> +1 650 284 9692 Reliability at Scale Cassandra, Spark, Elasticsearch on AWS, Azure, GCP and Softlayer

Re: Roadmap for 4.0

2018-04-09 Thread Ben Bromhead
tive would help. Otherwise if no one chimes in I would propose sticking with June 1. > > - > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.

Re: Roadmap for 4.0

2018-04-04 Thread Ben Bromhead
unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > > -- Ben Bromhead CTO | Instaclustr <https://www.instaclustr.com/> +1 650 284 9692 Reliability at Scale Cassandra, Spark, Elasticsearch on AWS, Azure, GCP and Softlayer

Re: Roadmap for 4.0

2018-04-04 Thread Ben Bromhead
ffect developers > >> more so than users. I'm really interested in why people believe there > is an > >> actual benefit in pumping out feature releases on a yearly basis. Who > >> exactly does that benefit? From what I know, the majority of "major" > user

Re: Repair scheduling tools

2018-04-04 Thread Ben Bromhead
>> that users opt into (table by table or cluster by cluster) with the > >>>>>>> understanding that it might not fully work out of the box the first > >>>>>>> time we ship it. We have to be willing to take risks but we also > >>> have > &

Re: Roadmap for 4.0

2018-04-03 Thread Ben Bromhead
te management using Vault > > > > - Stefan's Vault integration work. A sub-ticket, CASSANDRA-14102, > > > addresses > > > > encryption at-rest, subsumes CASSANDRA-9633 (SSTable encryption) - > > which > > > I > > > > doub

Re: A Simple List of New Major Features Desired for Apache Cassandra Version 4.0

2018-03-31 Thread Ben Bromhead
ons. Add > your suggestions for new major features you desire to be added for version > 4.0 only. Keep it simple, not detailed yet. That comes a few steps from > now. What we have is a basic collaboration challenge. No problem. > > Kenneth Brotman > > > > > > -- Ben Brom

Re: Roadmap for 4.0

2018-03-31 Thread Ben Bromhead
eplacement node with same >> address <https://issues.apache.org/jira/browse/CASSANDRA-12344> >> CASSANDRA-8119 - More expressive Consistency Levels >> <https://issues.apache.org/jira/browse/CASSANDRA-8119> >> CASSANDRA-14210 - Optimise SSTables upgrade task scheduling >> <https://issues.apache.org/jira/browse/CASSANDRA-14210> >> CASSANDRA-10540 - RangeAwareCompaction >> <https://issues.apache.org/jira/browse/CASSANDRA-10540> >> >> >> 2: >> CASSANDRA-10726 - Read repair inserts should not be blocking >> <https://issues.apache.org/jira/browse/CASSANDRA-10726> >> CASSANDRA-9754 - Make index info heap friendly for large CQL partitions >> <https://issues.apache.org/jira/browse/CASSANDRA-9754> >> CASSANDRA-12294 - LDAP auth >> <https://issues.apache.org/jira/browse/CASSANDRA-12294> >> CASSANDRA-12151 - Audit logging >> <https://issues.apache.org/jira/browse/CASSANDRA-12151> >> CASSANDRA-10495 - Fix streaming with vnodes >> <https://issues.apache.org/jira/browse/CASSANDRA-10495> >> >> Also, here's some handy JQL to start you off: >> project = CASSANDRA AND fixVersion in (4.x, 4.0) AND issue in >> watchedIssues() AND status != Resolved >> >> > -- Ben Bromhead CTO | Instaclustr <https://www.instaclustr.com/> +1 650 284 9692 Reliability at Scale Cassandra, Spark, Elasticsearch on AWS, Azure, GCP and Softlayer

Re: Proposal to retroactively mark materialized views experimental

2017-10-02 Thread Ben Bromhead
set, but we > > >> need > > >>>>> to be careful here. We need to make sure we don’t cause a problem > for > > >>>>> someone that is using them currently, even with all the edge cases > > >>> issues > > >>>>> they have now. > > >>>>> > > >>>>> -Jeremiah > > >>>>> > > >>>>> > > >>>>>> On Oct 2, 2017, at 2:01 PM, Blake Eggleston <beggles...@apple.com > > > > >>>>> wrote: > > >>>>>> > > >>>>>> Yeah, I'm not proposing that we disable MVs in existing clusters. > > >>>>>> > > >>>>>> > > >>>>>> On October 2, 2017 at 10:58:11 AM, Aleksey Yeshchenko ( > > >>> alek...@apple.com) > > >>>>> wrote: > > >>>>>> > > >>>>>> The idea is to check the flag in CreateViewStatement, so creation > of > > >>> new > > >>>>> MVs doesn’t succeed without that flag flipped. > > >>>>>> > > >>>>>> Obviously, just disabling existing MVs working in a minor would be > > >>> silly. > > >>>>>> > > >>>>>> As for the warning - yes, that should also be emitted. > > >> Unconditionally. > > >>>>>> > > >>>>>> — > > >>>>>> AY > > >>>>>> > > >>>>>> On 2 October 2017 at 18:18:52, Jeremiah D Jordan ( > > >>>>> jeremiah.jor...@gmail.com) wrote: > > >>>>>> > > >>>>>> These things are live on clusters right now, and I would not want > > >>>>> someone to upgrade their cluster to a new *patch* release and > > suddenly > > >>>>> something that may have been working for them now does not > function. > > >>>>> Anyway, we need to be careful about how this gets put into practice > > if > > >>> we > > >>>>> are going to do it retroactively. > > >>>>> > > >>>>> > > >>>>> > > - > > >>>>> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > > >>>>> For additional commands, e-mail: dev-h...@cassandra.apache.org > > >>>>> > > >>>>> > > >>> > > >>> > > >>> - > > >>> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > > >>> For additional commands, e-mail: dev-h...@cassandra.apache.org > > >>> > > >>> > > >> > > > > > -- Ben Bromhead CTO | Instaclustr <https://www.instaclustr.com/> +1 650 284 9692 Reliability at Scale Cassandra, Spark, Elasticsearch on AWS, Azure, GCP and Softlayer

Re: Proposal to retroactively mark materialized views experimental

2017-09-29 Thread Ben Bromhead
ake > > > ----- > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > > -- Ben Bromhead CTO | Instaclustr <https://www.instaclustr.com/> +1 650 284 9692 Reliability at Scale Cassandra, Spark, Elasticsearch on AWS, Azure, GCP and Softlayer

Re: NGCC?

2017-06-02 Thread Ben Bromhead
+1 On Fri, 2 Jun 2017 at 13:17 Eric Evans <john.eric.ev...@gmail.com> wrote: > On Fri, Jun 2, 2017 at 2:34 PM, Ben Bromhead <b...@instaclustr.com> wrote: > > We are more than happy to donate some resources (both people and > materials) > > to putting on NGCC. >

Re: NGCC?

2017-06-02 Thread Ben Bromhead
ght, of course. I was (clumsily) trying to create a > > distinction between this and a regular user conference. > > > > -- > > Eric Evans > > john.eric.ev...@gmail.com > > > > --------- > > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > > For additional commands, e-mail: dev-h...@cassandra.apache.org > > > > > -- Ben Bromhead CTO | Instaclustr <https://www.instaclustr.com/> +1 650 284 9692 Managed Cassandra / Spark on AWS, Azure and Softlayer

Re: Cassandra on RocksDB experiment result

2017-04-19 Thread Ben Bromhead
a log structured merge tree. RocksDB does it's own thing. Again this is an implementation detail about where the storage engine interface line is drawn, but from the above example compaction I think it is a non issue? > And not even mentioning the other operations to handle like streaming and

Re: New committers announcement

2017-02-14 Thread Ben Bromhead
gt; > Branimir Lambov > > > Paulo Motta > > > Stefan Pokowinski > > > Ariel Weisberg > > > Blake Eggleston > > > Alex Petrov > > > Joel Knighton > > > > > > Congratulations all! Please keep the excellent contributions coming. > > > > > > Thanks, > > > > > > -Jason Brown > > > > > > -- Ben Bromhead CTO | Instaclustr <https://www.instaclustr.com/> +1 650 284 9692 Managed Cassandra / Spark on AWS, Azure and Softlayer

Re: Instaclustr Masters scholarship

2017-02-09 Thread Ben Bromhead
rfc677.txt.pdf - lol, 1975 :) > > -Jason > > On Tue, Feb 7, 2017 at 7:26 PM, Ben Bromhead <b...@instaclustr.com> wrote: > > > As part of our commitment to contributing back to the Apache Cassandra > open > > source project and the wider community we are alway

Instaclustr Masters scholarship

2017-02-07 Thread Ben Bromhead
and is welcoming of foreign students. We are also open to sponsoring a PhD project with a more in depth focus for the right candidate. For more details please don't hesitate to get in touch with myself or reach out to i...@instaclustr.com. Cheers Ben -- Ben Bromhead CTO | Instaclustr <ht

Re: Wrapping up tick-tock

2017-01-10 Thread Ben Bromhead
3. only 2 releases (current and previous) to do bug fix support at any > > given time. > > The third reason is particularly appealing. > > +1 on six months. > +1 on killing tick/tock at 3.10 (with a potential bugfix follow up per > the other thread). > -- Ben Bromhead

Re: Where do I find EverywhereStrategy?

2016-12-03 Thread Ben Bromhead
6 at 06:47:12, sankalp kohli (kohlisank...@gmail.com) > wrote: > > The point Ben is saying is that for auth keyspace, default o​f RF=1 is not > good for any type of cluster whether it is small or large. > -- Ben Bromhead CTO | Instaclustr <https://www.instaclustr.com/> +1 650 284 9692 Managed Cassandra / Spark on AWS, Azure and Softlayer

Re: Where do I find EverywhereStrategy?

2016-11-30 Thread Ben Bromhead
ike that > (imagine a single digest mismatch triggering a blocking read repair on a > hundred nodes, and what that does to the various thread pools). > > > > -- Ben Bromhead CTO | Instaclustr <https://www.instaclustr.com/> +1 650 284 9692 Managed Cassandra / Spark on AWS, Azure and Softlayer

Re: Where do I find EverywhereStrategy?

2016-11-30 Thread Ben Bromhead
ilto:ja...@carmanconsulting.com] > > >> Sent: mercredi 30 novembre 2016 15:30 > > >> To: dev@cassandra.apache.org > > >> Subject: Where do I find EverywhereStrategy? > > >> > > >> I came across the class name > > >> "org.apache.cassandra.locator.EverywhereStrategy" in an error message, > > so I > > >> started searching through the code for it. I can't seem to find it. > Any > > >> pointers? > > >> > > >> > > >> Thanks, > > >> > > >> > > >> James > > >> > > > -- Ben Bromhead CTO | Instaclustr <https://www.instaclustr.com/> +1 650 284 9692 Managed Cassandra / Spark on AWS, Azure and Softlayer

Re: Summary of 4.0 Large Features/Breaking Changes (Was: Rough roadmap for 4.0)

2016-11-17 Thread Ben Bromhead
e same shop in Cupertino. I'm nervous about that. Not > that that ya'll are not capable, I'm solely looking at it from the > "that is a big list of some pretty hard shit" perspective. > > So what else do we need to discuss to get these completed? How and > where can other folks

Re: Rough roadmap for 4.0

2016-11-17 Thread Ben Bromhead
s/materialised views/aggregates/ also we expect to have our first larger production 3.7 LTS cluster in the next few months. On Thu, 17 Nov 2016 at 15:38 Ben Bromhead <b...@instaclustr.com> wrote: > We have a few small customers clusters running on our 3.7 LTS release... &g

Re: Rough roadmap for 4.0

2016-11-17 Thread Ben Bromhead
this should be "new stuff that could/will > break > > > >> things" > > > >> > > > > given we are upping > > > >> > > > > the major version. > > > >> > > > > > > > >> > > > > > > >> > > > > > > >> > > > How does this co-ordinate with the tick-tock versioning¹ > leading > > > up > > > >> to > > > >> > > the > > > >> > > > 4.0 release? > > > >> > > > > > > >> > > > To just stop tick-tock and then say yeehaa let's jam in all > the > > > >> > breaking > > > >> > > > changes we really want seems to be throwing away some of the > > > learnt > > > >> > > wisdom, > > > >> > > > and not doing a very sane transition from tick-tock to > > > >> > > > features/testing/stable². I really hope all this is done in a > > way > > > >> that > > > >> > > > continues us down the path towards a stable-master. > > > >> > > > > > > >> > > > For example, are we fixing the release of 4.0 to November? or > > > >> > continuing > > > >> > > > tick-tocks until we complete the 4.0 roadmap? or starting the > > > >> > > > features/testing/stable branching approach with 3.11? > > > >> > > > > > > >> > > > > > > >> > > > Background: > > > >> > > > ¹) Sylvain wrote in an earlier thread titled "A Home for 4.0" > > > >> > > > > > > >> > > > > And as 4.0 was initially supposed to come after 3.11, which > is > > > >> > coming, > > > >> > > > it's probably time to have a home for those tickets. > > > >> > > > > > > >> > > > ²) The new versioning scheme slated for 4.0, per the > "Proposal - > > > >> 3.5.1" > > > >> > > > thread > > > >> > > > > > > >> > > > > three branch plan with “features”, “testing”, and “stable” > > > >starting > > > >> > > with > > > >> > > > 4.0? > > > >> > > > > > > >> > > > > > > >> > > > Mick > > > >> > > > > > > >> > > > > > >> > > > > >> > > > > > > > -- > > > -- > > > > -- Ben Bromhead CTO | Instaclustr <https://www.instaclustr.com/> +1 650 284 9692 Managed Cassandra / Spark on AWS, Azure and Softlayer

Re: Board report and feedback from such.

2016-11-16 Thread Ben Bromhead
[4] > > https://lists.apache.org/list.html?priv...@cassandra.apache.org:lte=1M:Apache%20trademark%20and%20Spring%20project%20names > [5] https://mesosphere.github.io/cassandra-mesos/ > [6] https://github.com/riptano/cassandra-dtest > [7] > > https://lists.apache.org/thread.html/d43300016d3871587c43eea8cd4223221904fddc7916d9d6d858bd29@%3Cprivate.cassandra.apache.org%3E > [8] > > https://lists.apache.org/thread.html/d9e694ba8eaac8e8c70cbfd3f6ee249d43f8c67279882ffc65e56cac@%3Cdev.cassandra.apache.org%3E > -- Ben Bromhead CTO | Instaclustr <https://www.instaclustr.com/> +1 650 284 9692 Managed Cassandra / Spark on AWS, Azure and Softlayer

Re: [VOTE] Close client-...@cassandra.apache.org mailing list

2016-11-08 Thread Ben Bromhead
> served if it were directed at dev@, which is more active. > > > > This vote will remain open for 72 hours. > > > > 0: https://lists.apache.org/list.html?client-...@cassandra.apache.org > > > > > > > -- Ben Bromhead CTO | Instaclustr <https://www.instaclustr.com/> +1 650 284 9692 Managed Cassandra / Spark on AWS, Azure and Softlayer

Re: Backports to 2.1.16

2016-10-20 Thread Ben Bromhead
SANDRA-10446 > 26. Include table name in "Cannot get comparator" > exception(CASSANDRA-12181) > 27. Collect metrics on queries by consistency level (CASSANDRA-7384) > 28. processs restarts are failing becase native port and jmx ports are in > use(CASSANDRA-11093) > > Thanks, > Sankalp > -- Ben Bromhead CTO | Instaclustr <https://www.instaclustr.com/> +1 650 284 9692 Managed Cassandra / Spark on AWS, Azure and Softlayer

Re: Proposal - 3.5.1

2016-10-20 Thread Ben Bromhead
of the 4 types affected in any of their schema. > >>> > >>> I have cherry picked & merged the patch back to here and will put it > in a > >>> JIRA as well tonight, I just wanted to get the ball rolling asap on > this. > >>> > >>> > >> > https://github.com/rustyrazorblade/cassandra/tree/fix_commitlog_exception > >>> > >>> Jon > >>> > >> > >> > > -- Ben Bromhead CTO | Instaclustr <https://www.instaclustr.com/> +1 650 284 9692 Managed Cassandra / Spark on AWS, Azure and Softlayer

Re: Proprietary Replication Strategies: Cassandra Driver Support

2016-10-10 Thread Ben Bromhead
amp;gt; I'm gt;gt; amp;gt; amp;gt; fairly new here and would like to understand the dynamics. gt;gt; amp;gt; amp;gt; gt;gt; amp;gt; amp;gt; Thanks, gt;gt; amp;gt; amp;gt; Prasenjit gt;gt; amp;gt; gt;gt; amp;gt; gt;gt; gt;gt; gt;gt; gt;gt; gt;gt; gt;gt; -- Ben Bromh

Re: Multitanency in Cassandra

2014-08-30 Thread Ben Bromhead
tickets around this as well as our in-progress multi-tennant solution just uses containers, namespaces et al for isolation. Cheers Ben Bromhead Instaclustr | www.instaclustr.com | @instaclustr | +61 415 936 359 On 31/08/2014, at 10:06 AM, Jay Patel pateljay3...@gmail.com wrote: Hi Folks

Best avenue for reporting security issues

2013-12-17 Thread Ben Bromhead
that the Cassandra project should have secur...@cassandra.apache.org mailing address, where sensitive issues can be reported to the core dev team without it being made public. Regards Ben Bromhead Instaclustr | www.instaclustr.com | @instaclustr | +61 415 936 359

Re: Best avenue for reporting security issues

2013-12-17 Thread Ben Bromhead
No worries, message sent Ben Bromhead Instaclustr | www.instaclustr.com | @instaclustr | +61 415 936 359 On 18 Dec 2013, at 10:35 am, Aleksey Yeschenko alek...@apache.org wrote: Hi Ben, Send it to me, I'll handle it. Thanks On Wed, Dec 18, 2013 at 2:30 AM, Ben Bromhead b

Re: JNA to activate cassandra row cache

2013-08-21 Thread Ben Bromhead
limits.conf. Under other OS's that use RBAC style permissions, for example Solaris, where capabilities are often specified according to project, role, service etc the capability may need to be explicitly set. Ben Bromhead Instaclustr | www.instaclustr.com | @instaclustr On 22/08/2013, at 5:47