> On Aug 27, 2018, at 5:36 PM, Jonathan Haddad wrote:
> We're hoping to get some feedback on our side if that's something people
> are interested in. We've gone back and forth privately on our own
> preferences, hopes, dreams, etc, but I feel like a public discussion would
> be healthy at this po
Thanks everyone for the feedback. Looks like we will go with separate repo as
that is what majority of people prefer.
Also note that we can always change this approach later as we build the side
car.
> On Aug 24, 2018, at 07:00, Eric Evans wrote:
>
>> On Thu, Aug 23, 2018 at 3:01 PM sankalp
I’d be interested in contributing as well. I’ve been working on a skew review /
diagnostics tool which feeds off of cfstats/tbstats data (from TXT output to
CSV to conditionally formatted excel ) and am starting to store data in C* and
wrap a React based grid on it.
I have backlogged forking th
> Can you get all of the contributors cleared?
> What’s the architecture? Is it centralized? Is there a sidecar?
Working on it Jeff. Contributors are close to cleared. Copyright is either
Spotify or Stefan, both whom have CLAs in place with ASF.
Licenses of all npm dependencies are good. Still
Hi Cassandra users, Cassandra dev,
When recovering using SSTables from a snapshot, I want to know what are the
key differences between using:
1. Nodetool refresh and,
2. SSTableloader
Does nodetool refresh have restrictions that need to be met?
Does nodetool refresh work even if there is a change
> Is there a roadmap or release schedule, so we can get an idea of what
> the Reaper devs have planned for it?
Hi Murukesh,
there's no roadmap per se, as it's open-source and it's the contributions as
they come that make it.
What I know that's in progress or been discussed is:
- more thoro
As an aside, it’s frustrating that ya’ll would sit on this for months (first
e-mail was April); you folks have enough people that know the process to know
that communicating early and often helps avoid duplicating (expensive) work.
The best tech needs to go in and we need to leave ourselves wit
I don't believe #1 should be an issue, Mick has been reaching out.
Alex and Mick are putting together some architecture documentation, I won't
step on their toes. Currently you can run Reaper as a single instance that
connects to your entire cluster, multiple instances in HA mode, and we're
finis
Is there a roadmap or release schedule, so we can get an idea of what
the Reaper devs have planned for it?
Yours,
Murukesh Mohanan
On Tue, 28 Aug 2018 at 10:02, Jeff Jirsa wrote:
>
> Can you get all of the contributors cleared?
> What’s the architecture? Is it centralized? Is there a sidecar?
>
Can you get all of the contributors cleared?
What’s the architecture? Is it centralized? Is there a sidecar?
> On Aug 27, 2018, at 5:36 PM, Jonathan Haddad wrote:
>
> Hey folks,
>
> Mick brought this up in the sidecar thread, but I wanted to have a clear /
> separate discussion about what we'r
Hey folks,
Mick brought this up in the sidecar thread, but I wanted to have a clear /
separate discussion about what we're thinking with regard to contributing
Reaper to the C* project. In my mind, starting with Reaper is a great way
of having an admin right now, that we know works well at the ki
Hi all,
I wanted to give everyone an update on how development of Transient Replication
is going and where we are going to be as of 9/1. Blake Eggleston, Alex Petrov,
Benedict Elliott Smith, and myself have been working to get TR implemented for
4.0. Up to now we have avoided merging anything r
12 matches
Mail list logo
