cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jack Krupansky (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10922) Inconsistent query results
Date Fri, 15 Jan 2016 16:50:39 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-10922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15102056#comment-15102056
] 

Jack Krupansky commented on CASSANDRA-10922:
--------------------------------------------

Normally this kind of investigation should be pursued on the user list before assuming that
there is an actual bug, but now that we are here...

1. Describe how you got to this situation - did you upgrade the old cluster or copy and import
sstables, or... exactly what?
2. Provide the schema. Anxious to know the type of that column and exactly why you are using
hex.
3. Create a dummy table with exactly the same schema and compose INSERT statements that insert
the data you are querying. Does the query work fine on that dummy table? Post that schema,
INSERTS, SELECTs, and output here.
4. Create that same dummy table in a single-node test cluster running C* 2.2.3, execute those
dummy INSERTs, see that the query works the way it used to, "upgrade" that test database to
C* 3.0.2 the same way you did your main cluster and see if the query fails in the way you
have reported. If it doesn't... then nobody here will have much to go on. IN any case, be
sure to post the exact steps you used.

That's a lot of work to do, but start by posting the schema and the output of the query that
shows both rows.


> Inconsistent query results
> --------------------------
>
>                 Key: CASSANDRA-10922
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10922
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Maxim Podkolzine
>            Priority: Critical
>
> I have a DB created with Cassandra 2.2.3. And currently I'm running it by Cassandra 3.0.2.
> The value of a particular cell is returned depending on the query I run (in cqlsh):
> - returned when iterate all columns, i.e.
> SELECT value FROM "3xupsource".Content WHERE databaseid=0x21120000 LIMIT 2
> (I can see the columns 0x00000000 and 0x01000000 there, the values seem correct)
> - not returned when I specify a particular column
> SELECT value FROM "3xupsource".Content WHERE databaseid=0x21120000 AND columnid=0x01000000
> Other queries like SELECT value FROM "3xupsource".Content WHERE databaseid=0x21120000
AND columnid=0x00000000 work consistently.
> There is nothing in Cassandra error log, so it does not look like a corruption.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message