+1
On Tue, 21 Mar 2017 at 9:36 AM, Jonathan Haddad wrote:
> +1
> On Mon, Mar 20, 2017 at 6:33 PM Jason Brown wrote:
>
> > +1
> > On Mon, Mar 20, 2017 at 18:21 Anthony Grasso
> > wrote:
> >
> > > +1
> > >
> > > On 21 March 2017 at 09:32, Jeff Jirsa wrote:
> > >
> > > > There's no reason for the
Hi,
Will we still use tick-tock release for 4.x and 4.0.x ?
Stefan Podkowinski 于2016年11月16日周三 下午4:52写道：
> From my understanding, this will also effect EOL dates of other branches.
>
> "We will maintain the 2.2 stability series until 4.0 is released, and 3.0
> for six months after that.".
>
>
> O
quest(eg. insert a blo to collection column),
it will be awful.
Thank you.
jason zhao yang 于2016年8月6日周六 下午12:33写道：
> We consider splitting by Keypspace or tables before, but Cassandra's table
> is a costly structure(more cpu, flush, memory..).
>
> In our use case, it's
paces. This will also help with server resource isolation and
> most of the issues you've raised.
>
>
> On Fri, Jul 15, 2016 at 10:10 AM Romain Hardouin
> wrote:
>
> > I don't use C* in such a context but out of curiosity did you set
> > the request_schedu
Hi,
May I ask is there any plan of extending functionalities related to
Multi-Tenant?
Our current approach is to define an extra PartitionKey called "tenant_id".
In my use cases, all tenants will have the same table schemas.
* For security isolation: we customized GRANT statement to be able to
r
Hi,
Recently I am checking the performance of creating tables.
I found that MigrationStage thread spent most of the time in "
mergeColumnFamilies(oldColumnFamilies, newColumnFamilies);" method.
Can someone explain the purpose of merging oldCFs and newCFs to find the
diff between old and new whe
