Re: results differ on two queries, based on secondary index key and partition key

model. Have you looked >> at DSE Graph as a possibility? >> >> >> >> >> >> Sean Durity >> >> *From:* ferit baver elhuseyni [mailto:feritba...@gmail.com] >> *Sent:* Tuesday, March 14, 2017 11:40 AM >> *To:* user@cassandra.apache.org >>

Re: results differ on two queries, based on secondary index key and partition key

for a graph-based model. Have you looked at > DSE Graph as a possibility? > > > > > > Sean Durity > > *From:* ferit baver elhuseyni [mailto:feritba...@gmail.com] > *Sent:* Tuesday, March 14, 2017 11:40 AM > *To:* user@cassandra.apache.org > *Subject:* results di

Re: results differ on two queries, based on secondary index key and partition key

graph-based model. Have you looked at > DSE Graph as a possibility? > > > > > > Sean Durity > > *From:* ferit baver elhuseyni [mailto:feritba...@gmail.com] > *Sent:* Tuesday, March 14, 2017 11:40 AM > *To:* user@cassandra.apache.org > *Subject:* results differ

RE: results differ on two queries, based on secondary index key and partition key

This looks more like a problem for a graph-based model. Have you looked at DSE Graph as a possibility? Sean Durity From: ferit baver elhuseyni [mailto:feritba...@gmail.com] Sent: Tuesday, March 14, 2017 11:40 AM To: user@cassandra.apache.org Subject: results differ on two queries, based on

results differ on two queries, based on secondary index key and partition key

Hi all, We are using a C* 2.2.8 cluster in our production system, composed of 5 nodes in 1 DC with RF=3. Our clients mostly write with CL.ALL and read with CL.ONE (both will be switched to quorum soon). We face several problems while trying to persist classical "follow relationship". Did anyone