representative of the committee. A
> list of Apache Cassandra PMC members can be found on:
> https://cassandra.apache.org/_/community.html
>
> Kind regards,
>
> Paulo
>
>
--
Ben Bromhead
Instaclustr | www.instaclustr.com | @instaclustr
<http://twitter.com/instaclustr> | +64 27 383 8975
t; Given that criteria, Professional Support and Education might be on the
> > chopping
> > block as well.
> >
>
> +1 would definitely make my life easier when I'm reviewing/pushing updates
> to the site.
>
--
Ben Bromhead
Instaclustr | www.instaclustr.com | @instaclustr
<http://twitter.com/instaclustr> | +64 27 383 8975
On Thu, Jun 24, 2021 at 2:38 AM Joshua McKenzie
wrote:
>
> The obvious core responsibility of the website should be to ASLv2
> permissively licensed Apache Cassandra and secondarily to CQL as a protocol
> IMO. I don't think we as a project should be tracking derivative works,
> forks, or other
xt:
> > > >>>>
> > > >>>>
> > > >>
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-rc2-tentative
> > > >>>> [3]: The maven artifacts were accidentally prematurely made
> public.
> > Docs
> > > >>>> have been updated to prevent this happening again.
> > > >>>>
> > > >>
> > > >>
> > > >>
> -
> > > >> 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
> >
> >
>
--
Ben Bromhead
Instaclustr | www.instaclustr.com | @instaclustr
<http://twitter.com/instaclustr> | +64 27 383 8975
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
--
Ben Bromhead
Instaclustr | www.instaclustr.com | @instaclustr
<http://twitter.com/instaclustr> | +64 27 383 8975
org/ecosystem/
> > .
> >
> > If you have edits or know of other third-party Cassandra projects, tools,
> > products, etc that may be useful to others -- please get in touch and
> we'll
> > add to the next round of site updates in July.
> >
> > Thanks!
> >
> > Melissa
> > Apache Cassandra Contributor
> >
>
--
Ben Bromhead
Instaclustr | www.instaclustr.com | @instaclustr
<http://twitter.com/instaclustr> | +64 27 383 8975
gt;>>>> On Fri, May 14, 2021, 8:03 AM Mick Semb Wever
> > >>>> wrote:
> > >>>>>>>>>
> > >>>>>>>>> The PMC members are pleased to announce that Caleb Rackliffe
> has
> > >>>>>>>>> accepted the invitation to become
ional 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
>
> --
Ben Bromhead
Instaclustr | www.instaclustr.com | @instaclustr
<http://twitter.com/instaclustr> | +64 27 383 8975
---
> > 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
Instaclustr | www.instaclustr.com | @instaclustr
<http://twitter.com/instaclustr> | +64 27 383 8975
>
> The LICENSE and NOTICE issues remain unassigned, if you are keen!
>
--
Ben Bromhead
Instaclustr | www.instaclustr.com | @instaclustr
<http://twitter.com/instaclustr> | +64 27 383 8975
oking at impacting QA or touching any
> compatibility aspect of the code.
>
--
Ben Bromhead
Instaclustr | www.instaclustr.com | @instaclustr
<http://twitter.com/instaclustr> | +64 27 383 8975
; [1]: CHANGES.txt:
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-rc1-tentative
> > [2]: NEWS.txt:
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-rc1-tentative
>
>>> Y(n-2): Supported for high severity correctness/bugs for 1 more
> year
> > (1
> > > >> bugfix)
> > > >>
> > > >> This sounds excellent to me, +1.
> > > >>
> > > >>
> -
> > > >> 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
Instaclustr | www.instaclustr.com | @instaclustr
<http://twitter.com/instaclustr> | +64 27 383 8975
rces -- or community photos --
> > please reply to me and we'll add.
> >
> > Site for review: https://cassandra.staged.apache.org/
> >
> > https://issues.apache.org/jira/browse/CASSANDRA-16115
> >
> > Melissa Logan
> >
>
--
Ben Bromhead
Instaclustr | www.instaclustr.com | @instaclustr
<http://twitter.com/instaclustr> | +64 27 383 8975
Cluster-level Stop / Resume - stop all running instances while keeping
> > persistent storage. Allows for scaling compute down to zero. Bringing the
> > cluster back up follows expected startup procedures
> >
> > Road Map / Inflight
> >
> > 1.
> >
> &
know of for any of the approaches anyone's taken, so the
> > > discussions
> > > remain stalled.
> > >
> > > On Wed, Sep 23, 2020 at 7:18 AM, Benedict Elliott Smith <
> benedict@apache.
> > > org<mailto:bened...@apache.org> wrote:
> > >
> >
> ones meet the needs of end users before talking about adopting one into the
> foundation.
>
> Great to hear that you folks are joining forces though! Bodes well for C*
> users that are wanting to run things on k8s.
>
>
>
> On Tue, Sep 22, 2020 at 4:26 AM, Ben Brom
ment what functionality an operator should
> include at level 0, level 1, etc. We did discuss this a good bit during
> some of the initial SIG meetings, but I guess it wasn't really a focal
> point at the time. I think we should also provide references to existing
> operator projects and possibly
looking
forward to folks other suggestions!
Cheers
--
Ben Bromhead
Instaclustr | www.instaclustr.com | @instaclustr
<http://twitter.com/instaclustr> | (650) 284 9692
n-allocation-algorithm-cassandra-30
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
>
--
Ben Bromhead
Instaclustr | www.instaclustr.com | @instaclustr
<http://twitter.com/instaclustr> | (650) 284 9692
+1
On Mon, Nov 4, 2019 at 10:56 AM Vinay Chella
wrote:
> +1
>
> -Vinay Chella
>
> On Sat, Nov 2, 2019 at 5:09 PM Jeff Carpenter
> wrote:
>
> > FYI the audio of the session with Ben Bromhead / Scott Andreas is
> > available:
> >
> >
> https://fe
>>>
> >>>> Hey guys,
> >>>>
> >>>> I heard that at the last summit there were discussions about providing
> >> an
> >>>> official docker image to run Cassandra on Kubernetes. Is it something
> >> that
> >>>> you’ve started to work on ? We have our own at
> >>>> https://github.com/Orange-OpenSource/cassandra-image <
> >>>> https://github.com/Orange-OpenSource/cassandra-image> but I think
> >>>> providing an official image makes sense. As long as we can easily do
> >>>> everything we do today. We could also collaborate.
> >>>>
> >>>> Thank you
> >>>> —
> >>>> Cyril Scetbon
> >>>>
> >>>>
> >>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
>
--
Ben Bromhead
Instaclustr | www.instaclustr.com | @instaclustr
<http://twitter.com/instaclustr> | (650) 284 9692
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
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.
> > >
> >
> >
> > --
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
> >>>
> > > >>
> > >
> >
> 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
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
; >
> > 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
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
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
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
, 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
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
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
&
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.
> > >
> >
> > -------
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
;> 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
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.
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
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
>> 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
> &
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
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
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
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
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
+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.
>
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
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
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
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
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
6 at 06:47:12, sankalp kohli (kohlisank...@gmail.com)
> wrote:
>
> The point Ben is saying is that for auth keyspace, default of 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
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
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
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
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
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
[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
> 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
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
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
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
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
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
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
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
67 matches
Mail list logo
