Hi Sean,
Thanks for reply,
I'm agree with you about uniquness but when the output of sstabledump show
that we have the same value for the column g => "clustering" : [ "",
"Token", "abcd", "" ],
and when we select with the whole primary key with the valuers wich I see
in the sstable, cqlsh
effectively, this was written in 2.1.14 and we upgrade to 3.11.3 so we
should not be impacted by this issue ?!
thanks
Uniqueness is determined by the partition key PLUS the clustering columns. Hard
to tell from your data below, but is it possible that one of the clustering
columns (perhaps g) has different values? That would easily explain the 2 rows
returned – because they ARE different rows in the same
https://issues.apache.org/jira/browse/CASSANDRA-14008
If this was written in 2.1/2.2 and you upgraded to 3.0.x (x < 16) or
3.1-3.11.1, could be this issue.
--
Jeff Jirsa
> On May 15, 2019, at 8:43 AM, Ahmed Eljami wrote:
>
> What about this part of the dump:
>
> "type" : "row",
>
Hi guys,
We have a strange problem with the data in cassandra, after inserting twice
the same partition with differents columns, we see that cassandra returns 2
rows on cqlsh rather than one...:
a| b| c| d| f| g| h| i| j| k| l
What about this part of the dump:
"type" : "row",
"position" : 4123,
"clustering" : [ "", "Token", "abcd", "" ],
"cells" : [
{ "name" : "dvalue", "value" : "", "tstamp" :
"2019-04-26T17:20:39.910Z", "ttl" : 31708792, "expires_at" :
"2020-04-27T17:20:31Z",
Jeff, In this case is there any solution to resolve that directly in the
sstable (compact, scrub...) or we have to apply a batch on the client level
(delete a partition and re write it)?
Thank you for your reply.
Le mer. 15 mai 2019 à 18:09, Ahmed Eljami a écrit :
> effectively, this was
I don’t have a good answer for you - I don’t know if scrub will fix this (you
could copy an sstable offline and try it locally in ccm) - you may need to
delete and reinsert, though I’m really interested in knowing how this happened
if you weren’t ever exposed to #14008.
Can you open a JIRA?
which exact version you saw this?
On Wed, May 15, 2019 at 12:03 PM keshava wrote:
> I gave a try with changing java version , and it worked. seems to be some
> issue with java version of choice.
>
> On 10-May-2019 14:48, "keshava" wrote:
>
>> i will try with changing java version.
>> w.r.t
The java version that we were using and which turns out to be causing this
issue was OpenJdk 1.7 u191
On 16-May-2019 06:02, "sankalp kohli" wrote:
> which exact version you saw this?
>
> On Wed, May 15, 2019 at 12:03 PM keshava
> wrote:
>
>> I gave a try with changing java version , and it
Hi Bharat
As already pointed out below, there are some limitations and issues with
Materialized views (depending upon your version). This blog post also
summarizes some issues/caveats with MV
https://www.instaclustr.com/apache-cassandra-materialized-view-instaclustr-support/
Thanks
Alok Dwivedi
I gave a try with changing java version , and it worked. seems to be some
issue with java version of choice.
On 10-May-2019 14:48, "keshava" wrote:
> i will try with changing java version.
> w.r.t other point about hardware, i have this issue in multiple setups. so
> i really doubt if hardware
12 matches
Mail list logo
