There is a German saying:
Sometimes you don't see the woods because of the lots of trees.
Am 05.03.2017 09:25 schrieb "DuyHai Doan" :
> No problem, distributed systems are hard to reason about, I got caught many
> times in the past
>
> On Sun, Mar 5, 2017 at 9:23 AM, benjamin roth wrote:
>
> >
Not maybe. You are absolutely right. Bad idea. Hmpf.
Am 05.03.2017 09:23 schrieb "benjamin roth" :
> Sorry. Answer was to fast. Maybe you are right.
>
> Am 05.03.2017 09:21 schrieb "benjamin roth" :
>
>> No. You just change the partitioner. That's all
>>
>> Am 05.03.2017 09:15 schrieb "DuyHai Doa
No problem, distributed systems are hard to reason about, I got caught many
times in the past
On Sun, Mar 5, 2017 at 9:23 AM, benjamin roth wrote:
> Sorry. Answer was to fast. Maybe you are right.
>
> Am 05.03.2017 09:21 schrieb "benjamin roth" :
>
> > No. You just change the partitioner. That's
Sorry. Answer was to fast. Maybe you are right.
Am 05.03.2017 09:21 schrieb "benjamin roth" :
> No. You just change the partitioner. That's all
>
> Am 05.03.2017 09:15 schrieb "DuyHai Doan" :
>
>> "How can that be achieved? I haven't done "scientific researches" yet but
>> I
>> guess a "MV partit
No. You just change the partitioner. That's all
Am 05.03.2017 09:15 schrieb "DuyHai Doan" :
> "How can that be achieved? I haven't done "scientific researches" yet but I
> guess a "MV partitioner" could do the trick. Instead of applying the
> regular partitioner, an MV partitioner would calculate
"How can that be achieved? I haven't done "scientific researches" yet but I
guess a "MV partitioner" could do the trick. Instead of applying the
regular partitioner, an MV partitioner would calculate the PK of the base
table (which is always possible) and then apply the regular partitioner."
The m
While I was reading the MV paragraph in your post, an idea popped up:
The problem with MV inconsistencies and inconsistent range movement is that
the "MV contract" is broken. This only happens because base data and
replica data reside on different hosts. If base data + replicas would stay
on the s
On Sat, Mar 4, 2017 at 10:26 AM, Jeff Jirsa wrote:
>
>
>
> > On Mar 4, 2017, at 7:06 AM, Edward Capriolo
> wrote:
> >
> >> On Fri, Mar 3, 2017 at 12:04 PM, Jeff Jirsa wrote:
> >>
> >> On Fri, Mar 3, 2017 at 5:40 AM, Edward Capriolo
> >> wrote:
> >>
> >>>
> >>> I used them. I built do it yourse
> On Mar 4, 2017, at 7:06 AM, Edward Capriolo wrote:
>
>> On Fri, Mar 3, 2017 at 12:04 PM, Jeff Jirsa wrote:
>>
>> On Fri, Mar 3, 2017 at 5:40 AM, Edward Capriolo
>> wrote:
>>
>>>
>>> I used them. I built do it yourself secondary indexes with them. They
>> have
>>> there gotchas, but so d
On Saturday, March 4, 2017, Edward Capriolo wrote:
>
>
> On Fri, Mar 3, 2017 at 12:04 PM, Jeff Jirsa > wrote:
>
>> On Fri, Mar 3, 2017 at 5:40 AM, Edward Capriolo > >
>> wrote:
>>
>> >
>> > I used them. I built do it yourself secondary indexes with them. They
>> have
>> > there gotchas, but so d
On Fri, Mar 3, 2017 at 12:04 PM, Jeff Jirsa wrote:
> On Fri, Mar 3, 2017 at 5:40 AM, Edward Capriolo
> wrote:
>
> >
> > I used them. I built do it yourself secondary indexes with them. They
> have
> > there gotchas, but so do all the secondary index implementations. Just
> > because datastax doe
Does Cassandra itself use triggers internally for something?
That would make a pretty good case for triggers being ready for production
use.
Otherwise, it would tend to be a neglected feature because active
developers would have no good reason to add features to it other than just
make the test su
On Fri, Mar 3, 2017 at 5:40 AM, Edward Capriolo
wrote:
>
> I used them. I built do it yourself secondary indexes with them. They have
> there gotchas, but so do all the secondary index implementations. Just
> because datastax does not write about something. Lets see like 5 years ago
> there was t
On Thu, Mar 2, 2017 at 2:10 PM, Kant Kodali wrote:
> +1
>
> On Thu, Mar 2, 2017 at 11:04 AM, S G wrote:
>
> > Hi,
> >
> > I am not able to find any documentation on the current state of triggers
> > being production ready.
> >
> > The post at
&
>
> On Thu, Mar 2, 2017 at 11:04 AM, S G wrote:
>
> > Hi,
> >
> > I am not able to find any documentation on the current state of triggers
> > being production ready.
> >
> > The post at
> > http://www.datastax.com/dev/blog/whats-new-in-cassandra-
As far as I know, I've never met anyone who wrote and used their own
triggers in production. I imagine the number of people doing so is very
small, regardless of version.
On Thu, Mar 2, 2017 at 11:04 AM, S G wrote:
> Hi,
>
> I am not able to find any documentation on the cu
+1
On Thu, Mar 2, 2017 at 11:04 AM, S G wrote:
> Hi,
>
> I am not able to find any documentation on the current state of triggers
> being production ready.
>
> The post at
> http://www.datastax.com/dev/blog/whats-new-in-cassandra-2-
> 0-prototype-triggers-support
Hi,
I am not able to find any documentation on the current state of triggers
being production ready.
The post at
http://www.datastax.com/dev/blog/whats-new-in-cassandra-2-0-prototype-triggers-support
says that "The current implementation is experimental, and there is some
work to do b
18 matches
Mail list logo