[jira] [Commented] (CASSANDRA-6151) CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
[
https://issues.apache.org/jira/browse/CASSANDRA-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427547#comment-15427547
]
nicerobot commented on CASSANDRA-6151:
--
Hypothetically, i can create lots of single-node results, join them, and
hopefully the partitioning is retained for processing the data further.
> CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
>
>
> Key: CASSANDRA-6151
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6151
> Project: Cassandra
> Issue Type: Bug
>Reporter: Russell Spitzer
>Assignee: Alex Liu
>Priority: Minor
> Attachments: 6151-1.2-branch.txt, 6151-v2-1.2-branch.txt,
> 6151-v3-1.2-branch.txt, 6151-v4-1.2.10-branch.txt
>
>
> From
> http://stackoverflow.com/questions/19189649/composite-key-in-cassandra-with-pig/19211546#19211546
> The user was attempting to load a single partition using a where clause in a
> pig load statement.
> CQL Table
> {code}
> CREATE table data (
> occurday text,
> seqnumber int,
> occurtimems bigint,
> unique bigint,
> fields map,
> primary key ((occurday, seqnumber), occurtimems, unique)
> )
> {code}
> Pig Load statement Query
> {code}
> data = LOAD
> 'cql://ks/data?where_clause=seqnumber%3D10%20AND%20occurday%3D%272013-10-01%27'
> USING CqlStorage();
> {code}
> This results in an exception when processed by the the CqlPagingRecordReader
> which attempts to page this query even though it contains at most one
> partition key. This leads to an invalid CQL statement.
> CqlPagingRecordReader Query
> {code}
> SELECT * FROM "data" WHERE token("occurday","seqnumber") > ? AND
> token("occurday","seqnumber") <= ? AND occurday='A Great Day'
> AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
> {code}
> Exception
> {code}
> InvalidRequestException(why:occurday cannot be restricted by more than one
> relation if it includes an Equal)
> {code}
> I'm not sure it is worth the special case but, a modification to not use the
> paging record reader when the entire partition key is specified would solve
> this issue.
> h3. Solution
> If it have EQUAL clauses for all the partitioning keys, we use Query
> {code}
> SELECT * FROM "data"
> WHERE occurday='A Great Day'
>AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
> {code}
> instead of
> {code}
> SELECT * FROM "data"
> WHERE token("occurday","seqnumber") > ?
>AND token("occurday","seqnumber") <= ?
>AND occurday='A Great Day'
>AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
> {code}
> The base line implementation is to retrieve all data of all rows around the
> ring. This new feature is to retrieve all data of a wide row. It's a one
> level lower than the base line. It helps for the use case where user is only
> interested in a specific wide row, so the user doesn't spend whole job to
> retrieve all the rows around the ring.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-6151) CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
[
https://issues.apache.org/jira/browse/CASSANDRA-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858462#comment-13858462
]
Dumitru Pascu commented on CASSANDRA-6151:
--
As a conclusion for the current ticket and / or CASSANDRA-6311, is CqlStorage
going to allow single partition retrieval from a column family?
In my case, I am keeping daily account snapshots in a column family like the
following:
CREATE TABLE snapshots (
snapshot_date timestamp,
account_id text,
account_type text,
...other columns here...
PRIMARY KEY (snapshot_date, account_id)
)
Each day contains ~10 million records, filtering a partition at PIG level
doesn't really seem an option in several use cases...
CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
Key: CASSANDRA-6151
URL: https://issues.apache.org/jira/browse/CASSANDRA-6151
Project: Cassandra
Issue Type: Bug
Components: Hadoop
Reporter: Russell Alexander Spitzer
Assignee: Alex Liu
Priority: Minor
Attachments: 6151-1.2-branch.txt, 6151-v2-1.2-branch.txt,
6151-v3-1.2-branch.txt, 6151-v4-1.2.10-branch.txt
From
http://stackoverflow.com/questions/19189649/composite-key-in-cassandra-with-pig/19211546#19211546
The user was attempting to load a single partition using a where clause in a
pig load statement.
CQL Table
{code}
CREATE table data (
occurday text,
seqnumber int,
occurtimems bigint,
unique bigint,
fields maptext, text,
primary key ((occurday, seqnumber), occurtimems, unique)
)
{code}
Pig Load statement Query
{code}
data = LOAD
'cql://ks/data?where_clause=seqnumber%3D10%20AND%20occurday%3D%272013-10-01%27'
USING CqlStorage();
{code}
This results in an exception when processed by the the CqlPagingRecordReader
which attempts to page this query even though it contains at most one
partition key. This leads to an invalid CQL statement.
CqlPagingRecordReader Query
{code}
SELECT * FROM data WHERE token(occurday,seqnumber) ? AND
token(occurday,seqnumber) = ? AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
Exception
{code}
InvalidRequestException(why:occurday cannot be restricted by more than one
relation if it includes an Equal)
{code}
I'm not sure it is worth the special case but, a modification to not use the
paging record reader when the entire partition key is specified would solve
this issue.
h3. Solution
If it have EQUAL clauses for all the partitioning keys, we use Query
{code}
SELECT * FROM data
WHERE occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
instead of
{code}
SELECT * FROM data
WHERE token(occurday,seqnumber) ?
AND token(occurday,seqnumber) = ?
AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
The base line implementation is to retrieve all data of all rows around the
ring. This new feature is to retrieve all data of a wide row. It's a one
level lower than the base line. It helps for the use case where user is only
interested in a specific wide row, so the user doesn't spend whole job to
retrieve all the rows around the ring.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (CASSANDRA-6151) CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
[
https://issues.apache.org/jira/browse/CASSANDRA-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13848964#comment-13848964
]
Akshay DM commented on CASSANDRA-6151:
--
@Shridhar The patch seems to be working for 1.2.12 too. Thanks a lot...
CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
Key: CASSANDRA-6151
URL: https://issues.apache.org/jira/browse/CASSANDRA-6151
Project: Cassandra
Issue Type: Bug
Components: Hadoop
Reporter: Russell Alexander Spitzer
Assignee: Alex Liu
Priority: Minor
Attachments: 6151-1.2-branch.txt, 6151-v2-1.2-branch.txt,
6151-v3-1.2-branch.txt, 6151-v4-1.2.10-branch.txt
From
http://stackoverflow.com/questions/19189649/composite-key-in-cassandra-with-pig/19211546#19211546
The user was attempting to load a single partition using a where clause in a
pig load statement.
CQL Table
{code}
CREATE table data (
occurday text,
seqnumber int,
occurtimems bigint,
unique bigint,
fields maptext, text,
primary key ((occurday, seqnumber), occurtimems, unique)
)
{code}
Pig Load statement Query
{code}
data = LOAD
'cql://ks/data?where_clause=seqnumber%3D10%20AND%20occurday%3D%272013-10-01%27'
USING CqlStorage();
{code}
This results in an exception when processed by the the CqlPagingRecordReader
which attempts to page this query even though it contains at most one
partition key. This leads to an invalid CQL statement.
CqlPagingRecordReader Query
{code}
SELECT * FROM data WHERE token(occurday,seqnumber) ? AND
token(occurday,seqnumber) = ? AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
Exception
{code}
InvalidRequestException(why:occurday cannot be restricted by more than one
relation if it includes an Equal)
{code}
I'm not sure it is worth the special case but, a modification to not use the
paging record reader when the entire partition key is specified would solve
this issue.
h3. Solution
If it have EQUAL clauses for all the partitioning keys, we use Query
{code}
SELECT * FROM data
WHERE occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
instead of
{code}
SELECT * FROM data
WHERE token(occurday,seqnumber) ?
AND token(occurday,seqnumber) = ?
AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
The base line implementation is to retrieve all data of all rows around the
ring. This new feature is to retrieve all data of a wide row. It's a one
level lower than the base line. It helps for the use case where user is only
interested in a specific wide row, so the user doesn't spend whole job to
retrieve all the rows around the ring.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
[jira] [Commented] (CASSANDRA-6151) CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
[
https://issues.apache.org/jira/browse/CASSANDRA-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13847341#comment-13847341
]
devThoughts commented on CASSANDRA-6151:
@Shridhar thanks a ton. its working.
CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
Key: CASSANDRA-6151
URL: https://issues.apache.org/jira/browse/CASSANDRA-6151
Project: Cassandra
Issue Type: Bug
Components: Hadoop
Reporter: Russell Alexander Spitzer
Assignee: Alex Liu
Priority: Minor
Attachments: 6151-1.2-branch.txt, 6151-v2-1.2-branch.txt,
6151-v3-1.2-branch.txt, 6151-v4-1.2.10-branch.txt
From
http://stackoverflow.com/questions/19189649/composite-key-in-cassandra-with-pig/19211546#19211546
The user was attempting to load a single partition using a where clause in a
pig load statement.
CQL Table
{code}
CREATE table data (
occurday text,
seqnumber int,
occurtimems bigint,
unique bigint,
fields maptext, text,
primary key ((occurday, seqnumber), occurtimems, unique)
)
{code}
Pig Load statement Query
{code}
data = LOAD
'cql://ks/data?where_clause=seqnumber%3D10%20AND%20occurday%3D%272013-10-01%27'
USING CqlStorage();
{code}
This results in an exception when processed by the the CqlPagingRecordReader
which attempts to page this query even though it contains at most one
partition key. This leads to an invalid CQL statement.
CqlPagingRecordReader Query
{code}
SELECT * FROM data WHERE token(occurday,seqnumber) ? AND
token(occurday,seqnumber) = ? AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
Exception
{code}
InvalidRequestException(why:occurday cannot be restricted by more than one
relation if it includes an Equal)
{code}
I'm not sure it is worth the special case but, a modification to not use the
paging record reader when the entire partition key is specified would solve
this issue.
h3. Solution
If it have EQUAL clauses for all the partitioning keys, we use Query
{code}
SELECT * FROM data
WHERE occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
instead of
{code}
SELECT * FROM data
WHERE token(occurday,seqnumber) ?
AND token(occurday,seqnumber) = ?
AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
The base line implementation is to retrieve all data of all rows around the
ring. This new feature is to retrieve all data of a wide row. It's a one
level lower than the base line. It helps for the use case where user is only
interested in a specific wide row, so the user doesn't spend whole job to
retrieve all the rows around the ring.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
[jira] [Commented] (CASSANDRA-6151) CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
[
https://issues.apache.org/jira/browse/CASSANDRA-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13846157#comment-13846157
]
Shridhar commented on CASSANDRA-6151:
-
[~devP] I have modified already existing patch(V3) which works for IN clause on
partition keys. It seems to be working for us for 1.2.10 version. Attached is
the modified patch(V4) which should be applied on top of V3 patch.
CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
Key: CASSANDRA-6151
URL: https://issues.apache.org/jira/browse/CASSANDRA-6151
Project: Cassandra
Issue Type: Bug
Components: Hadoop
Reporter: Russell Alexander Spitzer
Assignee: Alex Liu
Priority: Minor
Attachments: 6151-1.2-branch.txt, 6151-v2-1.2-branch.txt,
6151-v3-1.2-branch.txt, 6151-v4-1.2.10-branch.txt
From
http://stackoverflow.com/questions/19189649/composite-key-in-cassandra-with-pig/19211546#19211546
The user was attempting to load a single partition using a where clause in a
pig load statement.
CQL Table
{code}
CREATE table data (
occurday text,
seqnumber int,
occurtimems bigint,
unique bigint,
fields maptext, text,
primary key ((occurday, seqnumber), occurtimems, unique)
)
{code}
Pig Load statement Query
{code}
data = LOAD
'cql://ks/data?where_clause=seqnumber%3D10%20AND%20occurday%3D%272013-10-01%27'
USING CqlStorage();
{code}
This results in an exception when processed by the the CqlPagingRecordReader
which attempts to page this query even though it contains at most one
partition key. This leads to an invalid CQL statement.
CqlPagingRecordReader Query
{code}
SELECT * FROM data WHERE token(occurday,seqnumber) ? AND
token(occurday,seqnumber) = ? AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
Exception
{code}
InvalidRequestException(why:occurday cannot be restricted by more than one
relation if it includes an Equal)
{code}
I'm not sure it is worth the special case but, a modification to not use the
paging record reader when the entire partition key is specified would solve
this issue.
h3. Solution
If it have EQUAL clauses for all the partitioning keys, we use Query
{code}
SELECT * FROM data
WHERE occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
instead of
{code}
SELECT * FROM data
WHERE token(occurday,seqnumber) ?
AND token(occurday,seqnumber) = ?
AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
The base line implementation is to retrieve all data of all rows around the
ring. This new feature is to retrieve all data of a wide row. It's a one
level lower than the base line. It helps for the use case where user is only
interested in a specific wide row, so the user doesn't spend whole job to
retrieve all the rows around the ring.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
[jira] [Commented] (CASSANDRA-6151) CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
[
https://issues.apache.org/jira/browse/CASSANDRA-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13845461#comment-13845461
]
devP commented on CASSANDRA-6151:
-
@Alex Liu the V3 patch is working fine on 1.2.10 branch except one problem. We
are not able to use IN clause on partition column still. EQ works fine. Please
let us know if we can expect another patch to solve this issue?
CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
Key: CASSANDRA-6151
URL: https://issues.apache.org/jira/browse/CASSANDRA-6151
Project: Cassandra
Issue Type: Bug
Components: Hadoop
Reporter: Russell Alexander Spitzer
Assignee: Alex Liu
Priority: Minor
Attachments: 6151-1.2-branch.txt, 6151-v2-1.2-branch.txt,
6151-v3-1.2-branch.txt
From
http://stackoverflow.com/questions/19189649/composite-key-in-cassandra-with-pig/19211546#19211546
The user was attempting to load a single partition using a where clause in a
pig load statement.
CQL Table
{code}
CREATE table data (
occurday text,
seqnumber int,
occurtimems bigint,
unique bigint,
fields maptext, text,
primary key ((occurday, seqnumber), occurtimems, unique)
)
{code}
Pig Load statement Query
{code}
data = LOAD
'cql://ks/data?where_clause=seqnumber%3D10%20AND%20occurday%3D%272013-10-01%27'
USING CqlStorage();
{code}
This results in an exception when processed by the the CqlPagingRecordReader
which attempts to page this query even though it contains at most one
partition key. This leads to an invalid CQL statement.
CqlPagingRecordReader Query
{code}
SELECT * FROM data WHERE token(occurday,seqnumber) ? AND
token(occurday,seqnumber) = ? AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
Exception
{code}
InvalidRequestException(why:occurday cannot be restricted by more than one
relation if it includes an Equal)
{code}
I'm not sure it is worth the special case but, a modification to not use the
paging record reader when the entire partition key is specified would solve
this issue.
h3. Solution
If it have EQUAL clauses for all the partitioning keys, we use Query
{code}
SELECT * FROM data
WHERE occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
instead of
{code}
SELECT * FROM data
WHERE token(occurday,seqnumber) ?
AND token(occurday,seqnumber) = ?
AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
The base line implementation is to retrieve all data of all rows around the
ring. This new feature is to retrieve all data of a wide row. It's a one
level lower than the base line. It helps for the use case where user is only
interested in a specific wide row, so the user doesn't spend whole job to
retrieve all the rows around the ring.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
[jira] [Commented] (CASSANDRA-6151) CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
[
https://issues.apache.org/jira/browse/CASSANDRA-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13845554#comment-13845554
]
Alex Liu commented on CASSANDRA-6151:
-
[~devP] Since this is resolved as won't fix, I don't expect there is new patch
for IN clause which could be done by multiple EQ queries as work around.
CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
Key: CASSANDRA-6151
URL: https://issues.apache.org/jira/browse/CASSANDRA-6151
Project: Cassandra
Issue Type: Bug
Components: Hadoop
Reporter: Russell Alexander Spitzer
Assignee: Alex Liu
Priority: Minor
Attachments: 6151-1.2-branch.txt, 6151-v2-1.2-branch.txt,
6151-v3-1.2-branch.txt
From
http://stackoverflow.com/questions/19189649/composite-key-in-cassandra-with-pig/19211546#19211546
The user was attempting to load a single partition using a where clause in a
pig load statement.
CQL Table
{code}
CREATE table data (
occurday text,
seqnumber int,
occurtimems bigint,
unique bigint,
fields maptext, text,
primary key ((occurday, seqnumber), occurtimems, unique)
)
{code}
Pig Load statement Query
{code}
data = LOAD
'cql://ks/data?where_clause=seqnumber%3D10%20AND%20occurday%3D%272013-10-01%27'
USING CqlStorage();
{code}
This results in an exception when processed by the the CqlPagingRecordReader
which attempts to page this query even though it contains at most one
partition key. This leads to an invalid CQL statement.
CqlPagingRecordReader Query
{code}
SELECT * FROM data WHERE token(occurday,seqnumber) ? AND
token(occurday,seqnumber) = ? AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
Exception
{code}
InvalidRequestException(why:occurday cannot be restricted by more than one
relation if it includes an Equal)
{code}
I'm not sure it is worth the special case but, a modification to not use the
paging record reader when the entire partition key is specified would solve
this issue.
h3. Solution
If it have EQUAL clauses for all the partitioning keys, we use Query
{code}
SELECT * FROM data
WHERE occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
instead of
{code}
SELECT * FROM data
WHERE token(occurday,seqnumber) ?
AND token(occurday,seqnumber) = ?
AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
The base line implementation is to retrieve all data of all rows around the
ring. This new feature is to retrieve all data of a wide row. It's a one
level lower than the base line. It helps for the use case where user is only
interested in a specific wide row, so the user doesn't spend whole job to
retrieve all the rows around the ring.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
[jira] [Commented] (CASSANDRA-6151) CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
[
https://issues.apache.org/jira/browse/CASSANDRA-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13829462#comment-13829462
]
Alex Liu commented on CASSANDRA-6151:
-
If hadoop doesn't support single-partition job, the work around for Pig is to
create a pig script to retrieve all partitions (where clause is empty for the
partition keys)over the network then it filters out other partitions at client
side. It's very slow if there are many partitions.
The patch pushes down the filtering work to CFIF, so that there is only one
mapper on the split having the partition. It provides a fast way for Pig/Hive
and other higher level clients to retrieve only one partition (which has wide
rows). I am not sure how common the use case are.
CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
Key: CASSANDRA-6151
URL: https://issues.apache.org/jira/browse/CASSANDRA-6151
Project: Cassandra
Issue Type: Bug
Components: Hadoop
Reporter: Russell Alexander Spitzer
Assignee: Alex Liu
Priority: Minor
Attachments: 6151-1.2-branch.txt, 6151-v2-1.2-branch.txt,
6151-v3-1.2-branch.txt
From
http://stackoverflow.com/questions/19189649/composite-key-in-cassandra-with-pig/19211546#19211546
The user was attempting to load a single partition using a where clause in a
pig load statement.
CQL Table
{code}
CREATE table data (
occurday text,
seqnumber int,
occurtimems bigint,
unique bigint,
fields maptext, text,
primary key ((occurday, seqnumber), occurtimems, unique)
)
{code}
Pig Load statement Query
{code}
data = LOAD
'cql://ks/data?where_clause=seqnumber%3D10%20AND%20occurday%3D%272013-10-01%27'
USING CqlStorage();
{code}
This results in an exception when processed by the the CqlPagingRecordReader
which attempts to page this query even though it contains at most one
partition key. This leads to an invalid CQL statement.
CqlPagingRecordReader Query
{code}
SELECT * FROM data WHERE token(occurday,seqnumber) ? AND
token(occurday,seqnumber) = ? AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
Exception
{code}
InvalidRequestException(why:occurday cannot be restricted by more than one
relation if it includes an Equal)
{code}
I'm not sure it is worth the special case but, a modification to not use the
paging record reader when the entire partition key is specified would solve
this issue.
h3. Solution
If it have EQUAL clauses for all the partitioning keys, we use Query
{code}
SELECT * FROM data
WHERE occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
instead of
{code}
SELECT * FROM data
WHERE token(occurday,seqnumber) ?
AND token(occurday,seqnumber) = ?
AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
The base line implementation is to retrieve all data of all rows around the
ring. This new feature is to retrieve all data of a wide row. It's a one
level lower than the base line. It helps for the use case where user is only
interested in a specific wide row, so the user doesn't spend whole job to
retrieve all the rows around the ring.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CASSANDRA-6151) CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
[
https://issues.apache.org/jira/browse/CASSANDRA-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13829442#comment-13829442
]
Jonathan Ellis commented on CASSANDRA-6151:
---
Brandon says that the equivalent here works in the Thrift CassandraStorage Pig
LoadFunc. I know CFIF doesn't do anything fancy for single-partition jobs, so
I assume it's doing something simpler. [~alexliu68]?
CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
Key: CASSANDRA-6151
URL: https://issues.apache.org/jira/browse/CASSANDRA-6151
Project: Cassandra
Issue Type: Bug
Components: Hadoop
Reporter: Russell Alexander Spitzer
Assignee: Alex Liu
Priority: Minor
Attachments: 6151-1.2-branch.txt, 6151-v2-1.2-branch.txt,
6151-v3-1.2-branch.txt
From
http://stackoverflow.com/questions/19189649/composite-key-in-cassandra-with-pig/19211546#19211546
The user was attempting to load a single partition using a where clause in a
pig load statement.
CQL Table
{code}
CREATE table data (
occurday text,
seqnumber int,
occurtimems bigint,
unique bigint,
fields maptext, text,
primary key ((occurday, seqnumber), occurtimems, unique)
)
{code}
Pig Load statement Query
{code}
data = LOAD
'cql://ks/data?where_clause=seqnumber%3D10%20AND%20occurday%3D%272013-10-01%27'
USING CqlStorage();
{code}
This results in an exception when processed by the the CqlPagingRecordReader
which attempts to page this query even though it contains at most one
partition key. This leads to an invalid CQL statement.
CqlPagingRecordReader Query
{code}
SELECT * FROM data WHERE token(occurday,seqnumber) ? AND
token(occurday,seqnumber) = ? AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
Exception
{code}
InvalidRequestException(why:occurday cannot be restricted by more than one
relation if it includes an Equal)
{code}
I'm not sure it is worth the special case but, a modification to not use the
paging record reader when the entire partition key is specified would solve
this issue.
h3. Solution
If it have EQUAL clauses for all the partitioning keys, we use Query
{code}
SELECT * FROM data
WHERE occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
instead of
{code}
SELECT * FROM data
WHERE token(occurday,seqnumber) ?
AND token(occurday,seqnumber) = ?
AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
The base line implementation is to retrieve all data of all rows around the
ring. This new feature is to retrieve all data of a wide row. It's a one
level lower than the base line. It helps for the use case where user is only
interested in a specific wide row, so the user doesn't spend whole job to
retrieve all the rows around the ring.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CASSANDRA-6151) CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
[
https://issues.apache.org/jira/browse/CASSANDRA-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13806823#comment-13806823
]
Chad Johnston commented on CASSANDRA-6151:
--
Everything seems to be working as expected now.
CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
Key: CASSANDRA-6151
URL: https://issues.apache.org/jira/browse/CASSANDRA-6151
Project: Cassandra
Issue Type: Bug
Components: Hadoop
Reporter: Russell Alexander Spitzer
Assignee: Alex Liu
Priority: Minor
Attachments: 6151-1.2-branch.txt, 6151-v2-1.2-branch.txt,
6151-v3-1.2-branch.txt
From
http://stackoverflow.com/questions/19189649/composite-key-in-cassandra-with-pig/19211546#19211546
The user was attempting to load a single partition using a where clause in a
pig load statement.
CQL Table
{code}
CREATE table data (
occurday text,
seqnumber int,
occurtimems bigint,
unique bigint,
fields maptext, text,
primary key ((occurday, seqnumber), occurtimems, unique)
)
{code}
Pig Load statement Query
{code}
data = LOAD
'cql://ks/data?where_clause=seqnumber%3D10%20AND%20occurday%3D%272013-10-01%27'
USING CqlStorage();
{code}
This results in an exception when processed by the the CqlPagingRecordReader
which attempts to page this query even though it contains at most one
partition key. This leads to an invalid CQL statement.
CqlPagingRecordReader Query
{code}
SELECT * FROM data WHERE token(occurday,seqnumber) ? AND
token(occurday,seqnumber) = ? AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
Exception
{code}
InvalidRequestException(why:occurday cannot be restricted by more than one
relation if it includes an Equal)
{code}
I'm not sure it is worth the special case but, a modification to not use the
paging record reader when the entire partition key is specified would solve
this issue.
h3. Solution
If it have EQUAL clauses for all the partitioning keys, we use Query
{code}
SELECT * FROM data
WHERE occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
instead of
{code}
SELECT * FROM data
WHERE token(occurday,seqnumber) ?
AND token(occurday,seqnumber) = ?
AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
The base line implementation is to retrieve all data of all rows around the
ring. This new feature is to retrieve all data of a wide row. It's a one
level lower than the base line. It helps for the use case where user is only
interested in a specific wide row, so the user doesn't spend whole job to
retrieve all the rows around the ring.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CASSANDRA-6151) CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
[
https://issues.apache.org/jira/browse/CASSANDRA-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13807238#comment-13807238
]
Alex Liu commented on CASSANDRA-6151:
-
Thanks for the testing.
CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
Key: CASSANDRA-6151
URL: https://issues.apache.org/jira/browse/CASSANDRA-6151
Project: Cassandra
Issue Type: Bug
Components: Hadoop
Reporter: Russell Alexander Spitzer
Assignee: Alex Liu
Priority: Minor
Attachments: 6151-1.2-branch.txt, 6151-v2-1.2-branch.txt,
6151-v3-1.2-branch.txt
From
http://stackoverflow.com/questions/19189649/composite-key-in-cassandra-with-pig/19211546#19211546
The user was attempting to load a single partition using a where clause in a
pig load statement.
CQL Table
{code}
CREATE table data (
occurday text,
seqnumber int,
occurtimems bigint,
unique bigint,
fields maptext, text,
primary key ((occurday, seqnumber), occurtimems, unique)
)
{code}
Pig Load statement Query
{code}
data = LOAD
'cql://ks/data?where_clause=seqnumber%3D10%20AND%20occurday%3D%272013-10-01%27'
USING CqlStorage();
{code}
This results in an exception when processed by the the CqlPagingRecordReader
which attempts to page this query even though it contains at most one
partition key. This leads to an invalid CQL statement.
CqlPagingRecordReader Query
{code}
SELECT * FROM data WHERE token(occurday,seqnumber) ? AND
token(occurday,seqnumber) = ? AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
Exception
{code}
InvalidRequestException(why:occurday cannot be restricted by more than one
relation if it includes an Equal)
{code}
I'm not sure it is worth the special case but, a modification to not use the
paging record reader when the entire partition key is specified would solve
this issue.
h3. Solution
If it have EQUAL clauses for all the partitioning keys, we use Query
{code}
SELECT * FROM data
WHERE occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
instead of
{code}
SELECT * FROM data
WHERE token(occurday,seqnumber) ?
AND token(occurday,seqnumber) = ?
AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
The base line implementation is to retrieve all data of all rows around the
ring. This new feature is to retrieve all data of a wide row. It's a one
level lower than the base line. It helps for the use case where user is only
interested in a specific wide row, so the user doesn't spend whole job to
retrieve all the rows around the ring.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CASSANDRA-6151) CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
[
https://issues.apache.org/jira/browse/CASSANDRA-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13805437#comment-13805437
]
Chad Johnston commented on CASSANDRA-6151:
--
I'm having issues running my tests against the 1.2 branch. If I give a {{load}}
statement with no {{where_clause}}, I get the error {{consistency level
LOCAL_ONE not compatible with replication strategy
(org.apache.cassandra.locator.SimpleStrategy)}}.
When I try the query with the {{where_clause}}, I get an error saying that the
keyspace does not exist, even though I can query the keyspace with no issues in
cqlsh.
CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
Key: CASSANDRA-6151
URL: https://issues.apache.org/jira/browse/CASSANDRA-6151
Project: Cassandra
Issue Type: Bug
Components: Hadoop
Reporter: Russell Alexander Spitzer
Assignee: Alex Liu
Priority: Minor
Attachments: 6151-1.2-branch.txt
From
http://stackoverflow.com/questions/19189649/composite-key-in-cassandra-with-pig/19211546#19211546
The user was attempting to load a single partition using a where clause in a
pig load statement.
CQL Table
{code}
CREATE table data (
occurday text,
seqnumber int,
occurtimems bigint,
unique bigint,
fields maptext, text,
primary key ((occurday, seqnumber), occurtimems, unique)
)
{code}
Pig Load statement Query
{code}
data = LOAD
'cql://ks/data?where_clause=seqnumber%3D10%20AND%20occurday%3D%272013-10-01%27'
USING CqlStorage();
{code}
This results in an exception when processed by the the CqlPagingRecordReader
which attempts to page this query even though it contains at most one
partition key. This leads to an invalid CQL statement.
CqlPagingRecordReader Query
{code}
SELECT * FROM data WHERE token(occurday,seqnumber) ? AND
token(occurday,seqnumber) = ? AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
Exception
{code}
InvalidRequestException(why:occurday cannot be restricted by more than one
relation if it includes an Equal)
{code}
I'm not sure it is worth the special case but, a modification to not use the
paging record reader when the entire partition key is specified would solve
this issue.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CASSANDRA-6151) CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
[
https://issues.apache.org/jira/browse/CASSANDRA-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13805443#comment-13805443
]
Alex Liu commented on CASSANDRA-6151:
-
It's related to CASSANDRA-6238, you can cassandra.consistencylevel.read to
ONE in Pig as a workaround.
CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
Key: CASSANDRA-6151
URL: https://issues.apache.org/jira/browse/CASSANDRA-6151
Project: Cassandra
Issue Type: Bug
Components: Hadoop
Reporter: Russell Alexander Spitzer
Assignee: Alex Liu
Priority: Minor
Attachments: 6151-1.2-branch.txt
From
http://stackoverflow.com/questions/19189649/composite-key-in-cassandra-with-pig/19211546#19211546
The user was attempting to load a single partition using a where clause in a
pig load statement.
CQL Table
{code}
CREATE table data (
occurday text,
seqnumber int,
occurtimems bigint,
unique bigint,
fields maptext, text,
primary key ((occurday, seqnumber), occurtimems, unique)
)
{code}
Pig Load statement Query
{code}
data = LOAD
'cql://ks/data?where_clause=seqnumber%3D10%20AND%20occurday%3D%272013-10-01%27'
USING CqlStorage();
{code}
This results in an exception when processed by the the CqlPagingRecordReader
which attempts to page this query even though it contains at most one
partition key. This leads to an invalid CQL statement.
CqlPagingRecordReader Query
{code}
SELECT * FROM data WHERE token(occurday,seqnumber) ? AND
token(occurday,seqnumber) = ? AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
Exception
{code}
InvalidRequestException(why:occurday cannot be restricted by more than one
relation if it includes an Equal)
{code}
I'm not sure it is worth the special case but, a modification to not use the
paging record reader when the entire partition key is specified would solve
this issue.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CASSANDRA-6151) CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
[
https://issues.apache.org/jira/browse/CASSANDRA-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13805460#comment-13805460
]
Chad Johnston commented on CASSANDRA-6151:
--
That works around the consistency error. I still get the error saying the
keyspace was not found whenever I specify a {{where_clause}}.
CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
Key: CASSANDRA-6151
URL: https://issues.apache.org/jira/browse/CASSANDRA-6151
Project: Cassandra
Issue Type: Bug
Components: Hadoop
Reporter: Russell Alexander Spitzer
Assignee: Alex Liu
Priority: Minor
Attachments: 6151-1.2-branch.txt
From
http://stackoverflow.com/questions/19189649/composite-key-in-cassandra-with-pig/19211546#19211546
The user was attempting to load a single partition using a where clause in a
pig load statement.
CQL Table
{code}
CREATE table data (
occurday text,
seqnumber int,
occurtimems bigint,
unique bigint,
fields maptext, text,
primary key ((occurday, seqnumber), occurtimems, unique)
)
{code}
Pig Load statement Query
{code}
data = LOAD
'cql://ks/data?where_clause=seqnumber%3D10%20AND%20occurday%3D%272013-10-01%27'
USING CqlStorage();
{code}
This results in an exception when processed by the the CqlPagingRecordReader
which attempts to page this query even though it contains at most one
partition key. This leads to an invalid CQL statement.
CqlPagingRecordReader Query
{code}
SELECT * FROM data WHERE token(occurday,seqnumber) ? AND
token(occurday,seqnumber) = ? AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
Exception
{code}
InvalidRequestException(why:occurday cannot be restricted by more than one
relation if it includes an Equal)
{code}
I'm not sure it is worth the special case but, a modification to not use the
paging record reader when the entire partition key is specified would solve
this issue.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CASSANDRA-6151) CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
[
https://issues.apache.org/jira/browse/CASSANDRA-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13805478#comment-13805478
]
Alex Liu commented on CASSANDRA-6151:
-
v2 patch set default CL to ONE. My unit test is in the patch.
{code}
CREATE KEYSPACE cql3ks WITH replication = {'class': 'SimpleStrategy',
'replication_factor' : 1}
CREATE TABLE compositekeytable (key1 text, key2 int, key3 int, key4 int,
column1 int, column2 float, primary key((key1, key2), key3, key4))
CREATE INDEX column1 on compositekeytable (column1);
INSERT INTO compositekeytable (key1, key2, key3, key4, column1, column2) values
('key1', 111, 100, 100, 100, 10.1)
INSERT INTO compositekeytable (key1, key2, key3, key4, column1, column2)
values ('key1', 111, 100, 101, 100, 10.1)
INSERT INTO compositekeytable (key1, key2, key3, key4, column1, column2)
values ('key1', 111, 100, 102, 100, 10.1)
INSERT INTO compositekeytable (key1, key2, key3, key4, column1, column2)
values ('key1', 111, 100, 103, 100, 10.1)
INSERT INTO compositekeytable (key1, key2, key3, key4, column1, column2)
values ('key1', 111, 100, 104, 100, 10.1)
INSERT INTO compositekeytable (key1, key2, key3, key4, column1, column2)
values ('key1', 111, 100, 105, 100, 10.1)
composite_rows = LOAD
'cql://cql3ks/compositekeytable?where_clause=key1%20%3D%20%27key1%27%20and%20key2%20%3D%20111%20and%20column1%3D100page_size=2'
USING CqlStorage();
dump composite_rows;
{code}
Can you check your test settings to mine?
CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
Key: CASSANDRA-6151
URL: https://issues.apache.org/jira/browse/CASSANDRA-6151
Project: Cassandra
Issue Type: Bug
Components: Hadoop
Reporter: Russell Alexander Spitzer
Assignee: Alex Liu
Priority: Minor
Attachments: 6151-1.2-branch.txt, 6151-v2-1.2-branch.txt
From
http://stackoverflow.com/questions/19189649/composite-key-in-cassandra-with-pig/19211546#19211546
The user was attempting to load a single partition using a where clause in a
pig load statement.
CQL Table
{code}
CREATE table data (
occurday text,
seqnumber int,
occurtimems bigint,
unique bigint,
fields maptext, text,
primary key ((occurday, seqnumber), occurtimems, unique)
)
{code}
Pig Load statement Query
{code}
data = LOAD
'cql://ks/data?where_clause=seqnumber%3D10%20AND%20occurday%3D%272013-10-01%27'
USING CqlStorage();
{code}
This results in an exception when processed by the the CqlPagingRecordReader
which attempts to page this query even though it contains at most one
partition key. This leads to an invalid CQL statement.
CqlPagingRecordReader Query
{code}
SELECT * FROM data WHERE token(occurday,seqnumber) ? AND
token(occurday,seqnumber) = ? AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
Exception
{code}
InvalidRequestException(why:occurday cannot be restricted by more than one
relation if it includes an Equal)
{code}
I'm not sure it is worth the special case but, a modification to not use the
paging record reader when the entire partition key is specified would solve
this issue.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CASSANDRA-6151) CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
[
https://issues.apache.org/jira/browse/CASSANDRA-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13805541#comment-13805541
]
Chad Johnston commented on CASSANDRA-6151:
--
I still get the keyspace does not exist error. This makes me wonder if I have
something wrong in my environment. Is there a way I can turn on some debugging
or other diagnostics?
CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
Key: CASSANDRA-6151
URL: https://issues.apache.org/jira/browse/CASSANDRA-6151
Project: Cassandra
Issue Type: Bug
Components: Hadoop
Reporter: Russell Alexander Spitzer
Assignee: Alex Liu
Priority: Minor
Attachments: 6151-1.2-branch.txt, 6151-v2-1.2-branch.txt
From
http://stackoverflow.com/questions/19189649/composite-key-in-cassandra-with-pig/19211546#19211546
The user was attempting to load a single partition using a where clause in a
pig load statement.
CQL Table
{code}
CREATE table data (
occurday text,
seqnumber int,
occurtimems bigint,
unique bigint,
fields maptext, text,
primary key ((occurday, seqnumber), occurtimems, unique)
)
{code}
Pig Load statement Query
{code}
data = LOAD
'cql://ks/data?where_clause=seqnumber%3D10%20AND%20occurday%3D%272013-10-01%27'
USING CqlStorage();
{code}
This results in an exception when processed by the the CqlPagingRecordReader
which attempts to page this query even though it contains at most one
partition key. This leads to an invalid CQL statement.
CqlPagingRecordReader Query
{code}
SELECT * FROM data WHERE token(occurday,seqnumber) ? AND
token(occurday,seqnumber) = ? AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
Exception
{code}
InvalidRequestException(why:occurday cannot be restricted by more than one
relation if it includes an Equal)
{code}
I'm not sure it is worth the special case but, a modification to not use the
paging record reader when the entire partition key is specified would solve
this issue.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CASSANDRA-6151) CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
[
https://issues.apache.org/jira/browse/CASSANDRA-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13805566#comment-13805566
]
Alex Liu commented on CASSANDRA-6151:
-
Follow this link
http://stackoverflow.com/questions/16627748/pig-batch-mode-how-to-set-logging-level-to-hide-info-log-messages
{code}
Step1: copy the log4j config file to the folder where my pig scripts are
located.
cp /etc/pig/conf.dist/log4j.properties log4j_WARN
Step2: Edit log4j_WARN file and make sure these two lines are present
log4j.logger.org.apache.pig=WARN, A
log4j.logger.org.apache.hadoop = WARN, A
log4j.logger.org.apache.cassandra = WARN, A
Step3: Run pig script and instruct it to use the custom log4j
pig -x local -4 log4j_WARN MyScript.pig
{code}
You can set level to DEBUG
CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
Key: CASSANDRA-6151
URL: https://issues.apache.org/jira/browse/CASSANDRA-6151
Project: Cassandra
Issue Type: Bug
Components: Hadoop
Reporter: Russell Alexander Spitzer
Assignee: Alex Liu
Priority: Minor
Attachments: 6151-1.2-branch.txt, 6151-v2-1.2-branch.txt
From
http://stackoverflow.com/questions/19189649/composite-key-in-cassandra-with-pig/19211546#19211546
The user was attempting to load a single partition using a where clause in a
pig load statement.
CQL Table
{code}
CREATE table data (
occurday text,
seqnumber int,
occurtimems bigint,
unique bigint,
fields maptext, text,
primary key ((occurday, seqnumber), occurtimems, unique)
)
{code}
Pig Load statement Query
{code}
data = LOAD
'cql://ks/data?where_clause=seqnumber%3D10%20AND%20occurday%3D%272013-10-01%27'
USING CqlStorage();
{code}
This results in an exception when processed by the the CqlPagingRecordReader
which attempts to page this query even though it contains at most one
partition key. This leads to an invalid CQL statement.
CqlPagingRecordReader Query
{code}
SELECT * FROM data WHERE token(occurday,seqnumber) ? AND
token(occurday,seqnumber) = ? AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
Exception
{code}
InvalidRequestException(why:occurday cannot be restricted by more than one
relation if it includes an Equal)
{code}
I'm not sure it is worth the special case but, a modification to not use the
paging record reader when the entire partition key is specified would solve
this issue.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CASSANDRA-6151) CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
[
https://issues.apache.org/jira/browse/CASSANDRA-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13805570#comment-13805570
]
Alex Liu commented on CASSANDRA-6151:
-
Or change test/conf/log4j-junit.properties to remove
log4j.logger.org.apache.hadoop=ERROR
then run the unit test
{code}
ant pig-test
{code}
where CqlTableTest has the unit for this ticket.
CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
Key: CASSANDRA-6151
URL: https://issues.apache.org/jira/browse/CASSANDRA-6151
Project: Cassandra
Issue Type: Bug
Components: Hadoop
Reporter: Russell Alexander Spitzer
Assignee: Alex Liu
Priority: Minor
Attachments: 6151-1.2-branch.txt, 6151-v2-1.2-branch.txt
From
http://stackoverflow.com/questions/19189649/composite-key-in-cassandra-with-pig/19211546#19211546
The user was attempting to load a single partition using a where clause in a
pig load statement.
CQL Table
{code}
CREATE table data (
occurday text,
seqnumber int,
occurtimems bigint,
unique bigint,
fields maptext, text,
primary key ((occurday, seqnumber), occurtimems, unique)
)
{code}
Pig Load statement Query
{code}
data = LOAD
'cql://ks/data?where_clause=seqnumber%3D10%20AND%20occurday%3D%272013-10-01%27'
USING CqlStorage();
{code}
This results in an exception when processed by the the CqlPagingRecordReader
which attempts to page this query even though it contains at most one
partition key. This leads to an invalid CQL statement.
CqlPagingRecordReader Query
{code}
SELECT * FROM data WHERE token(occurday,seqnumber) ? AND
token(occurday,seqnumber) = ? AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
Exception
{code}
InvalidRequestException(why:occurday cannot be restricted by more than one
relation if it includes an Equal)
{code}
I'm not sure it is worth the special case but, a modification to not use the
paging record reader when the entire partition key is specified would solve
this issue.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CASSANDRA-6151) CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
[
https://issues.apache.org/jira/browse/CASSANDRA-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13805622#comment-13805622
]
Chad Johnston commented on CASSANDRA-6151:
--
Okay - I re-cloned the repo and applied the patch again. All of the
{{pig-test}} tests pass, but I still get keyspace does not exist from within
Pig.
CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
Key: CASSANDRA-6151
URL: https://issues.apache.org/jira/browse/CASSANDRA-6151
Project: Cassandra
Issue Type: Bug
Components: Hadoop
Reporter: Russell Alexander Spitzer
Assignee: Alex Liu
Priority: Minor
Attachments: 6151-1.2-branch.txt, 6151-v2-1.2-branch.txt
From
http://stackoverflow.com/questions/19189649/composite-key-in-cassandra-with-pig/19211546#19211546
The user was attempting to load a single partition using a where clause in a
pig load statement.
CQL Table
{code}
CREATE table data (
occurday text,
seqnumber int,
occurtimems bigint,
unique bigint,
fields maptext, text,
primary key ((occurday, seqnumber), occurtimems, unique)
)
{code}
Pig Load statement Query
{code}
data = LOAD
'cql://ks/data?where_clause=seqnumber%3D10%20AND%20occurday%3D%272013-10-01%27'
USING CqlStorage();
{code}
This results in an exception when processed by the the CqlPagingRecordReader
which attempts to page this query even though it contains at most one
partition key. This leads to an invalid CQL statement.
CqlPagingRecordReader Query
{code}
SELECT * FROM data WHERE token(occurday,seqnumber) ? AND
token(occurday,seqnumber) = ? AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
Exception
{code}
InvalidRequestException(why:occurday cannot be restricted by more than one
relation if it includes an Equal)
{code}
I'm not sure it is worth the special case but, a modification to not use the
paging record reader when the entire partition key is specified would solve
this issue.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CASSANDRA-6151) CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
[
https://issues.apache.org/jira/browse/CASSANDRA-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13805660#comment-13805660
]
Alex Liu commented on CASSANDRA-6151:
-
thanks, I can reproduce it.
CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
Key: CASSANDRA-6151
URL: https://issues.apache.org/jira/browse/CASSANDRA-6151
Project: Cassandra
Issue Type: Bug
Components: Hadoop
Reporter: Russell Alexander Spitzer
Assignee: Alex Liu
Priority: Minor
Attachments: 6151-1.2-branch.txt, 6151-v2-1.2-branch.txt
From
http://stackoverflow.com/questions/19189649/composite-key-in-cassandra-with-pig/19211546#19211546
The user was attempting to load a single partition using a where clause in a
pig load statement.
CQL Table
{code}
CREATE table data (
occurday text,
seqnumber int,
occurtimems bigint,
unique bigint,
fields maptext, text,
primary key ((occurday, seqnumber), occurtimems, unique)
)
{code}
Pig Load statement Query
{code}
data = LOAD
'cql://ks/data?where_clause=seqnumber%3D10%20AND%20occurday%3D%272013-10-01%27'
USING CqlStorage();
{code}
This results in an exception when processed by the the CqlPagingRecordReader
which attempts to page this query even though it contains at most one
partition key. This leads to an invalid CQL statement.
CqlPagingRecordReader Query
{code}
SELECT * FROM data WHERE token(occurday,seqnumber) ? AND
token(occurday,seqnumber) = ? AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
Exception
{code}
InvalidRequestException(why:occurday cannot be restricted by more than one
relation if it includes an Equal)
{code}
I'm not sure it is worth the special case but, a modification to not use the
paging record reader when the entire partition key is specified would solve
this issue.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CASSANDRA-6151) CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
[
https://issues.apache.org/jira/browse/CASSANDRA-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13805854#comment-13805854
]
Alex Liu commented on CASSANDRA-6151:
-
v3 patch is attached which fixes the keyspace can't be found issue.
CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
Key: CASSANDRA-6151
URL: https://issues.apache.org/jira/browse/CASSANDRA-6151
Project: Cassandra
Issue Type: Bug
Components: Hadoop
Reporter: Russell Alexander Spitzer
Assignee: Alex Liu
Priority: Minor
Attachments: 6151-1.2-branch.txt, 6151-v2-1.2-branch.txt,
6151-v3-1.2-branch.txt
From
http://stackoverflow.com/questions/19189649/composite-key-in-cassandra-with-pig/19211546#19211546
The user was attempting to load a single partition using a where clause in a
pig load statement.
CQL Table
{code}
CREATE table data (
occurday text,
seqnumber int,
occurtimems bigint,
unique bigint,
fields maptext, text,
primary key ((occurday, seqnumber), occurtimems, unique)
)
{code}
Pig Load statement Query
{code}
data = LOAD
'cql://ks/data?where_clause=seqnumber%3D10%20AND%20occurday%3D%272013-10-01%27'
USING CqlStorage();
{code}
This results in an exception when processed by the the CqlPagingRecordReader
which attempts to page this query even though it contains at most one
partition key. This leads to an invalid CQL statement.
CqlPagingRecordReader Query
{code}
SELECT * FROM data WHERE token(occurday,seqnumber) ? AND
token(occurday,seqnumber) = ? AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
Exception
{code}
InvalidRequestException(why:occurday cannot be restricted by more than one
relation if it includes an Equal)
{code}
I'm not sure it is worth the special case but, a modification to not use the
paging record reader when the entire partition key is specified would solve
this issue.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CASSANDRA-6151) CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
[
https://issues.apache.org/jira/browse/CASSANDRA-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13802677#comment-13802677
]
Alex Liu commented on CASSANDRA-6151:
-
[~c-chad.johns...@wcom.com] Do you have time to test the patch? Only allow
EQUAL clauses for partition keys. e.g. occurday and seqnumber
CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
Key: CASSANDRA-6151
URL: https://issues.apache.org/jira/browse/CASSANDRA-6151
Project: Cassandra
Issue Type: Bug
Components: Hadoop
Reporter: Russell Alexander Spitzer
Assignee: Alex Liu
Priority: Minor
Attachments: 6151-1.2-branch.txt
From
http://stackoverflow.com/questions/19189649/composite-key-in-cassandra-with-pig/19211546#19211546
The user was attempting to load a single partition using a where clause in a
pig load statement.
CQL Table
{code}
CREATE table data (
occurday text,
seqnumber int,
occurtimems bigint,
unique bigint,
fields maptext, text,
primary key ((occurday, seqnumber), occurtimems, unique)
)
{code}
Pig Load statement Query
{code}
data = LOAD
'cql://ks/data?where_clause=seqnumber%3D10%20AND%20occurday%3D%272013-10-01%27'
USING CqlStorage();
{code}
This results in an exception when processed by the the CqlPagingRecordReader
which attempts to page this query even though it contains at most one
partition key. This leads to an invalid CQL statement.
CqlPagingRecordReader Query
{code}
SELECT * FROM data WHERE token(occurday,seqnumber) ? AND
token(occurday,seqnumber) = ? AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
Exception
{code}
InvalidRequestException(why:occurday cannot be restricted by more than one
relation if it includes an Equal)
{code}
I'm not sure it is worth the special case but, a modification to not use the
paging record reader when the entire partition key is specified would solve
this issue.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CASSANDRA-6151) CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
[
https://issues.apache.org/jira/browse/CASSANDRA-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13803341#comment-13803341
]
Chad Johnston commented on CASSANDRA-6151:
--
Alex - I'll try to get to it in the next day or so.
CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
Key: CASSANDRA-6151
URL: https://issues.apache.org/jira/browse/CASSANDRA-6151
Project: Cassandra
Issue Type: Bug
Components: Hadoop
Reporter: Russell Alexander Spitzer
Assignee: Alex Liu
Priority: Minor
Attachments: 6151-1.2-branch.txt
From
http://stackoverflow.com/questions/19189649/composite-key-in-cassandra-with-pig/19211546#19211546
The user was attempting to load a single partition using a where clause in a
pig load statement.
CQL Table
{code}
CREATE table data (
occurday text,
seqnumber int,
occurtimems bigint,
unique bigint,
fields maptext, text,
primary key ((occurday, seqnumber), occurtimems, unique)
)
{code}
Pig Load statement Query
{code}
data = LOAD
'cql://ks/data?where_clause=seqnumber%3D10%20AND%20occurday%3D%272013-10-01%27'
USING CqlStorage();
{code}
This results in an exception when processed by the the CqlPagingRecordReader
which attempts to page this query even though it contains at most one
partition key. This leads to an invalid CQL statement.
CqlPagingRecordReader Query
{code}
SELECT * FROM data WHERE token(occurday,seqnumber) ? AND
token(occurday,seqnumber) = ? AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
Exception
{code}
InvalidRequestException(why:occurday cannot be restricted by more than one
relation if it includes an Equal)
{code}
I'm not sure it is worth the special case but, a modification to not use the
paging record reader when the entire partition key is specified would solve
this issue.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CASSANDRA-6151) CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
[
https://issues.apache.org/jira/browse/CASSANDRA-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13802484#comment-13802484
]
Alex Liu commented on CASSANDRA-6151:
-
We need find the split having the partition keys, and only submit that split to
the task, otherwise there will be duplicate results.
CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
Key: CASSANDRA-6151
URL: https://issues.apache.org/jira/browse/CASSANDRA-6151
Project: Cassandra
Issue Type: Bug
Components: Hadoop
Reporter: Russell Alexander Spitzer
Assignee: Alex Liu
Priority: Minor
From
http://stackoverflow.com/questions/19189649/composite-key-in-cassandra-with-pig/19211546#19211546
The user was attempting to load a single partition using a where clause in a
pig load statement.
CQL Table
{code}
CREATE table data (
occurday text,
seqnumber int,
occurtimems bigint,
unique bigint,
fields maptext, text,
primary key ((occurday, seqnumber), occurtimems, unique)
)
{code}
Pig Load statement Query
{code}
data = LOAD
'cql://ks/data?where_clause=seqnumber%3D10%20AND%20occurday%3D%272013-10-01%27'
USING CqlStorage();
{code}
This results in an exception when processed by the the CqlPagingRecordReader
which attempts to page this query even though it contains at most one
partition key. This leads to an invalid CQL statement.
CqlPagingRecordReader Query
{code}
SELECT * FROM data WHERE token(occurday,seqnumber) ? AND
token(occurday,seqnumber) = ? AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
Exception
{code}
InvalidRequestException(why:occurday cannot be restricted by more than one
relation if it includes an Equal)
{code}
I'm not sure it is worth the special case but, a modification to not use the
paging record reader when the entire partition key is specified would solve
this issue.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CASSANDRA-6151) CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
[
https://issues.apache.org/jira/browse/CASSANDRA-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13801039#comment-13801039
]
Alex Liu commented on CASSANDRA-6151:
-
[~jbellis] To fix this one, we can modify CqlPagingReader to check the where
clauses. If it have EQUAL clauses for all the partitioning keys, we use Query
{code}
SELECT * FROM data
WHERE occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
instead of
{code}
SELECT * FROM data
WHERE token(occurday,seqnumber) ?
AND token(occurday,seqnumber) = ?
AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
Any comments before I proceed.
CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
Key: CASSANDRA-6151
URL: https://issues.apache.org/jira/browse/CASSANDRA-6151
Project: Cassandra
Issue Type: Bug
Components: Hadoop
Reporter: Russell Alexander Spitzer
Assignee: Alex Liu
Priority: Minor
From
http://stackoverflow.com/questions/19189649/composite-key-in-cassandra-with-pig/19211546#19211546
The user was attempting to load a single partition using a where clause in a
pig load statement.
CQL Table
{code}
CREATE table data (
occurday text,
seqnumber int,
occurtimems bigint,
unique bigint,
fields maptext, text,
primary key ((occurday, seqnumber), occurtimems, unique)
)
{code}
Pig Load statement Query
{code}
data = LOAD
'cql://ks/data?where_clause=seqnumber%3D10%20AND%20occurday%3D%272013-10-01%27'
USING CqlStorage();
{code}
This results in an exception when processed by the the CqlPagingRecordReader
which attempts to page this query even though it contains at most one
partition key. This leads to an invalid CQL statement.
CqlPagingRecordReader Query
{code}
SELECT * FROM data WHERE token(occurday,seqnumber) ? AND
token(occurday,seqnumber) = ? AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
Exception
{code}
InvalidRequestException(why:occurday cannot be restricted by more than one
relation if it includes an Equal)
{code}
I'm not sure it is worth the special case but, a modification to not use the
paging record reader when the entire partition key is specified would solve
this issue.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CASSANDRA-6151) CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
[
https://issues.apache.org/jira/browse/CASSANDRA-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13801072#comment-13801072
]
Russell Alexander Spitzer commented on CASSANDRA-6151:
--
I like that solution, but if we special case this shouldn't we also add a case
for 'IN (tuple)' statements?
Example:
{code}
Select key from table where key in ('keyvalue1','keyvalue2','keyvalue3')
{code}
CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
Key: CASSANDRA-6151
URL: https://issues.apache.org/jira/browse/CASSANDRA-6151
Project: Cassandra
Issue Type: Bug
Components: Hadoop
Reporter: Russell Alexander Spitzer
Assignee: Alex Liu
Priority: Minor
From
http://stackoverflow.com/questions/19189649/composite-key-in-cassandra-with-pig/19211546#19211546
The user was attempting to load a single partition using a where clause in a
pig load statement.
CQL Table
{code}
CREATE table data (
occurday text,
seqnumber int,
occurtimems bigint,
unique bigint,
fields maptext, text,
primary key ((occurday, seqnumber), occurtimems, unique)
)
{code}
Pig Load statement Query
{code}
data = LOAD
'cql://ks/data?where_clause=seqnumber%3D10%20AND%20occurday%3D%272013-10-01%27'
USING CqlStorage();
{code}
This results in an exception when processed by the the CqlPagingRecordReader
which attempts to page this query even though it contains at most one
partition key. This leads to an invalid CQL statement.
CqlPagingRecordReader Query
{code}
SELECT * FROM data WHERE token(occurday,seqnumber) ? AND
token(occurday,seqnumber) = ? AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
Exception
{code}
InvalidRequestException(why:occurday cannot be restricted by more than one
relation if it includes an Equal)
{code}
I'm not sure it is worth the special case but, a modification to not use the
paging record reader when the entire partition key is specified would solve
this issue.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CASSANDRA-6151) CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
[
https://issues.apache.org/jira/browse/CASSANDRA-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13801209#comment-13801209
]
Alex Liu commented on CASSANDRA-6151:
-
{code}
select * from data where occurday in ('dd', 'd2');
Bad Request: Partition KEY part occurday cannot be restricted by IN relation
(only the last part of the partition key can)
{code}
This is good
{code}
select * from data where occurday ='d' and seqnumber in (1,2);
{code}
CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
Key: CASSANDRA-6151
URL: https://issues.apache.org/jira/browse/CASSANDRA-6151
Project: Cassandra
Issue Type: Bug
Components: Hadoop
Reporter: Russell Alexander Spitzer
Assignee: Alex Liu
Priority: Minor
From
http://stackoverflow.com/questions/19189649/composite-key-in-cassandra-with-pig/19211546#19211546
The user was attempting to load a single partition using a where clause in a
pig load statement.
CQL Table
{code}
CREATE table data (
occurday text,
seqnumber int,
occurtimems bigint,
unique bigint,
fields maptext, text,
primary key ((occurday, seqnumber), occurtimems, unique)
)
{code}
Pig Load statement Query
{code}
data = LOAD
'cql://ks/data?where_clause=seqnumber%3D10%20AND%20occurday%3D%272013-10-01%27'
USING CqlStorage();
{code}
This results in an exception when processed by the the CqlPagingRecordReader
which attempts to page this query even though it contains at most one
partition key. This leads to an invalid CQL statement.
CqlPagingRecordReader Query
{code}
SELECT * FROM data WHERE token(occurday,seqnumber) ? AND
token(occurday,seqnumber) = ? AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
Exception
{code}
InvalidRequestException(why:occurday cannot be restricted by more than one
relation if it includes an Equal)
{code}
I'm not sure it is worth the special case but, a modification to not use the
paging record reader when the entire partition key is specified would solve
this issue.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CASSANDRA-6151) CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
[
https://issues.apache.org/jira/browse/CASSANDRA-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13801220#comment-13801220
]
Alex Liu commented on CASSANDRA-6151:
-
We now check
{code}
1. all partition keys are in user defined where clauses
2. all partition keys where clauses are EQUAL except for the last partition
key can be IN clause
{code}
CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
Key: CASSANDRA-6151
URL: https://issues.apache.org/jira/browse/CASSANDRA-6151
Project: Cassandra
Issue Type: Bug
Components: Hadoop
Reporter: Russell Alexander Spitzer
Assignee: Alex Liu
Priority: Minor
From
http://stackoverflow.com/questions/19189649/composite-key-in-cassandra-with-pig/19211546#19211546
The user was attempting to load a single partition using a where clause in a
pig load statement.
CQL Table
{code}
CREATE table data (
occurday text,
seqnumber int,
occurtimems bigint,
unique bigint,
fields maptext, text,
primary key ((occurday, seqnumber), occurtimems, unique)
)
{code}
Pig Load statement Query
{code}
data = LOAD
'cql://ks/data?where_clause=seqnumber%3D10%20AND%20occurday%3D%272013-10-01%27'
USING CqlStorage();
{code}
This results in an exception when processed by the the CqlPagingRecordReader
which attempts to page this query even though it contains at most one
partition key. This leads to an invalid CQL statement.
CqlPagingRecordReader Query
{code}
SELECT * FROM data WHERE token(occurday,seqnumber) ? AND
token(occurday,seqnumber) = ? AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
Exception
{code}
InvalidRequestException(why:occurday cannot be restricted by more than one
relation if it includes an Equal)
{code}
I'm not sure it is worth the special case but, a modification to not use the
paging record reader when the entire partition key is specified would solve
this issue.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CASSANDRA-6151) CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
[
https://issues.apache.org/jira/browse/CASSANDRA-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13801318#comment-13801318
]
Alex Liu commented on CASSANDRA-6151:
-
For paging, we can't use IN clauses.
CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
Key: CASSANDRA-6151
URL: https://issues.apache.org/jira/browse/CASSANDRA-6151
Project: Cassandra
Issue Type: Bug
Components: Hadoop
Reporter: Russell Alexander Spitzer
Assignee: Alex Liu
Priority: Minor
From
http://stackoverflow.com/questions/19189649/composite-key-in-cassandra-with-pig/19211546#19211546
The user was attempting to load a single partition using a where clause in a
pig load statement.
CQL Table
{code}
CREATE table data (
occurday text,
seqnumber int,
occurtimems bigint,
unique bigint,
fields maptext, text,
primary key ((occurday, seqnumber), occurtimems, unique)
)
{code}
Pig Load statement Query
{code}
data = LOAD
'cql://ks/data?where_clause=seqnumber%3D10%20AND%20occurday%3D%272013-10-01%27'
USING CqlStorage();
{code}
This results in an exception when processed by the the CqlPagingRecordReader
which attempts to page this query even though it contains at most one
partition key. This leads to an invalid CQL statement.
CqlPagingRecordReader Query
{code}
SELECT * FROM data WHERE token(occurday,seqnumber) ? AND
token(occurday,seqnumber) = ? AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
Exception
{code}
InvalidRequestException(why:occurday cannot be restricted by more than one
relation if it includes an Equal)
{code}
I'm not sure it is worth the special case but, a modification to not use the
paging record reader when the entire partition key is specified would solve
this issue.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CASSANDRA-6151) CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
[
https://issues.apache.org/jira/browse/CASSANDRA-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13798253#comment-13798253
]
Alex Liu commented on CASSANDRA-6151:
-
I will check whether we could fix this issue at CQL side.
CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
Key: CASSANDRA-6151
URL: https://issues.apache.org/jira/browse/CASSANDRA-6151
Project: Cassandra
Issue Type: Bug
Components: Hadoop
Reporter: Russell Alexander Spitzer
Assignee: Alex Liu
Priority: Minor
From
http://stackoverflow.com/questions/19189649/composite-key-in-cassandra-with-pig/19211546#19211546
The user was attempting to load a single partition using a where clause in a
pig load statement.
CQL Table
{code}
CREATE table data (
occurday text,
seqnumber int,
occurtimems bigint,
unique bigint,
fields maptext, text,
primary key ((occurday, seqnumber), occurtimems, unique)
)
{code}
Pig Load statement Query
{code}
data = LOAD
'cql://ks/data?where_clause=seqnumber%3D10%20AND%20occurday%3D%272013-10-01%27'
USING CqlStorage();
{code}
This results in an exception when processed by the the CqlPagingRecordReader
which attempts to page this query even though it contains at most one
partition key. This leads to an invalid CQL statement.
CqlPagingRecordReader Query
{code}
SELECT * FROM data WHERE token(occurday,seqnumber) ? AND
token(occurday,seqnumber) = ? AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
Exception
{code}
InvalidRequestException(why:occurday cannot be restricted by more than one
relation if it includes an Equal)
{code}
I'm not sure it is worth the special case but, a modification to not use the
paging record reader when the entire partition key is specified would solve
this issue.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CASSANDRA-6151) CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
[
https://issues.apache.org/jira/browse/CASSANDRA-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13797290#comment-13797290
]
Chad Johnston commented on CASSANDRA-6151:
--
For what it's worth, our use case involves looking up data mostly by
{{occurday}}, since we're partitioning by day. Leaving off {{seqnumber}} from
the query isn't allowed, hence my example of a single value. In reality, we'd
really want to use {{IN()}} for {{seqnumber}} but that fails as well.
CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
Key: CASSANDRA-6151
URL: https://issues.apache.org/jira/browse/CASSANDRA-6151
Project: Cassandra
Issue Type: Bug
Components: Hadoop
Reporter: Russell Alexander Spitzer
Assignee: Alex Liu
Priority: Minor
From
http://stackoverflow.com/questions/19189649/composite-key-in-cassandra-with-pig/19211546#19211546
The user was attempting to load a single partition using a where clause in a
pig load statement.
CQL Table
{code}
CREATE table data (
occurday text,
seqnumber int,
occurtimems bigint,
unique bigint,
fields maptext, text,
primary key ((occurday, seqnumber), occurtimems, unique)
)
{code}
Pig Load statement Query
{code}
data = LOAD
'cql://ks/data?where_clause=seqnumber%3D10%20AND%20occurday%3D%272013-10-01%27'
USING CqlStorage();
{code}
This results in an exception when processed by the the CqlPagingRecordReader
which attempts to page this query even though it contains at most one
partition key. This leads to an invalid CQL statement.
CqlPagingRecordReader Query
{code}
SELECT * FROM data WHERE token(occurday,seqnumber) ? AND
token(occurday,seqnumber) = ? AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
Exception
{code}
InvalidRequestException(why:occurday cannot be restricted by more than one
relation if it includes an Equal)
{code}
I'm not sure it is worth the special case but, a modification to not use the
paging record reader when the entire partition key is specified would solve
this issue.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CASSANDRA-6151) CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
[
https://issues.apache.org/jira/browse/CASSANDRA-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13797332#comment-13797332
]
Alex Liu commented on CASSANDRA-6151:
-
A workaround is not using where clause of occurday in the url
{code}
LOAD
'cql://ks/data?where_clause=seqnumber%3D10%20AND%20occurday%3D%272013-10-01%27'
{code}
Filter/group the result of occurday at pig script side
CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
Key: CASSANDRA-6151
URL: https://issues.apache.org/jira/browse/CASSANDRA-6151
Project: Cassandra
Issue Type: Bug
Components: Hadoop
Reporter: Russell Alexander Spitzer
Assignee: Alex Liu
Priority: Minor
From
http://stackoverflow.com/questions/19189649/composite-key-in-cassandra-with-pig/19211546#19211546
The user was attempting to load a single partition using a where clause in a
pig load statement.
CQL Table
{code}
CREATE table data (
occurday text,
seqnumber int,
occurtimems bigint,
unique bigint,
fields maptext, text,
primary key ((occurday, seqnumber), occurtimems, unique)
)
{code}
Pig Load statement Query
{code}
data = LOAD
'cql://ks/data?where_clause=seqnumber%3D10%20AND%20occurday%3D%272013-10-01%27'
USING CqlStorage();
{code}
This results in an exception when processed by the the CqlPagingRecordReader
which attempts to page this query even though it contains at most one
partition key. This leads to an invalid CQL statement.
CqlPagingRecordReader Query
{code}
SELECT * FROM data WHERE token(occurday,seqnumber) ? AND
token(occurday,seqnumber) = ? AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
Exception
{code}
InvalidRequestException(why:occurday cannot be restricted by more than one
relation if it includes an Equal)
{code}
I'm not sure it is worth the special case but, a modification to not use the
paging record reader when the entire partition key is specified would solve
this issue.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CASSANDRA-6151) CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
[
https://issues.apache.org/jira/browse/CASSANDRA-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13788231#comment-13788231
]
Brandon Williams commented on CASSANDRA-6151:
-
To be fair, I'm not sure why you'd use M/R for a single partition, but I'll let
Alex decide what to do based on difficulty here.
CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
Key: CASSANDRA-6151
URL: https://issues.apache.org/jira/browse/CASSANDRA-6151
Project: Cassandra
Issue Type: Bug
Components: Hadoop
Reporter: Russell Alexander Spitzer
Assignee: Alex Liu
Priority: Minor
From
http://stackoverflow.com/questions/19189649/composite-key-in-cassandra-with-pig/19211546#19211546
The user was attempting to load a single partition using a where clause in a
pig load statement.
CQL Table
{code}
CREATE table data (
occurday text,
seqnumber int,
occurtimems bigint,
unique bigint,
fields maptext, text,
primary key ((occurday, seqnumber), occurtimems, unique)
)
{code}
Pig Load statement Query
{code}
data = LOAD
'cql://ks/data?where_clause=seqnumber%3D10%20AND%20occurday%3D%272013-10-01%27'
USING CqlStorage();
{code}
This results in an exception when processed by the the CqlPagingRecordReader
which attempts to page this query even though it contains at most one
partition key. This leads to an invalid CQL statement.
CqlPagingRecordReader Query
{code}
SELECT * FROM data WHERE token(occurday,seqnumber) ? AND
token(occurday,seqnumber) = ? AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
Exception
{code}
InvalidRequestException(why:occurday cannot be restricted by more than one
relation if it includes an Equal)
{code}
I'm not sure it is worth the special case but, a modification to not use the
paging record reader when the entire partition key is specified would solve
this issue.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CASSANDRA-6151) CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
[
https://issues.apache.org/jira/browse/CASSANDRA-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13788245#comment-13788245
]
Russell Alexander Spitzer commented on CASSANDRA-6151:
--
[~brandon.williams], I agree, but we should at least have a better error
message then.
CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
Key: CASSANDRA-6151
URL: https://issues.apache.org/jira/browse/CASSANDRA-6151
Project: Cassandra
Issue Type: Bug
Components: Hadoop
Reporter: Russell Alexander Spitzer
Assignee: Alex Liu
Priority: Minor
From
http://stackoverflow.com/questions/19189649/composite-key-in-cassandra-with-pig/19211546#19211546
The user was attempting to load a single partition using a where clause in a
pig load statement.
CQL Table
{code}
CREATE table data (
occurday text,
seqnumber int,
occurtimems bigint,
unique bigint,
fields maptext, text,
primary key ((occurday, seqnumber), occurtimems, unique)
)
{code}
Pig Load statement Query
{code}
data = LOAD
'cql://ks/data?where_clause=seqnumber%3D10%20AND%20occurday%3D%272013-10-01%27'
USING CqlStorage();
{code}
This results in an exception when processed by the the CqlPagingRecordReader
which attempts to page this query even though it contains at most one
partition key. This leads to an invalid CQL statement.
CqlPagingRecordReader Query
{code}
SELECT * FROM data WHERE token(occurday,seqnumber) ? AND
token(occurday,seqnumber) = ? AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
Exception
{code}
InvalidRequestException(why:occurday cannot be restricted by more than one
relation if it includes an Equal)
{code}
I'm not sure it is worth the special case but, a modification to not use the
paging record reader when the entire partition key is specified would solve
this issue.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CASSANDRA-6151) CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
[
https://issues.apache.org/jira/browse/CASSANDRA-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13788362#comment-13788362
]
Alex Liu commented on CASSANDRA-6151:
-
I think it's better not implement this to keep paging algorithm simple. Let
Pig/Hive to filter the result by using partition key clause at Hive/Pig side,
CqlPagingRecordReader paging through the rows with only user defined where
clauses on none-partition keys. Let's document this somewhere.
The paging algorithm of CqlPagingRecordReader is based on token range.
CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
Key: CASSANDRA-6151
URL: https://issues.apache.org/jira/browse/CASSANDRA-6151
Project: Cassandra
Issue Type: Bug
Components: Hadoop
Reporter: Russell Alexander Spitzer
Assignee: Alex Liu
Priority: Minor
From
http://stackoverflow.com/questions/19189649/composite-key-in-cassandra-with-pig/19211546#19211546
The user was attempting to load a single partition using a where clause in a
pig load statement.
CQL Table
{code}
CREATE table data (
occurday text,
seqnumber int,
occurtimems bigint,
unique bigint,
fields maptext, text,
primary key ((occurday, seqnumber), occurtimems, unique)
)
{code}
Pig Load statement Query
{code}
data = LOAD
'cql://ks/data?where_clause=seqnumber%3D10%20AND%20occurday%3D%272013-10-01%27'
USING CqlStorage();
{code}
This results in an exception when processed by the the CqlPagingRecordReader
which attempts to page this query even though it contains at most one
partition key. This leads to an invalid CQL statement.
CqlPagingRecordReader Query
{code}
SELECT * FROM data WHERE token(occurday,seqnumber) ? AND
token(occurday,seqnumber) = ? AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
Exception
{code}
InvalidRequestException(why:occurday cannot be restricted by more than one
relation if it includes an Equal)
{code}
I'm not sure it is worth the special case but, a modification to not use the
paging record reader when the entire partition key is specified would solve
this issue.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (CASSANDRA-6151) CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
[
https://issues.apache.org/jira/browse/CASSANDRA-6151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13788365#comment-13788365
]
Alex Liu commented on CASSANDRA-6151:
-
Or we can add a validate method to validate the user defined where clauses.
CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
Key: CASSANDRA-6151
URL: https://issues.apache.org/jira/browse/CASSANDRA-6151
Project: Cassandra
Issue Type: Bug
Components: Hadoop
Reporter: Russell Alexander Spitzer
Assignee: Alex Liu
Priority: Minor
From
http://stackoverflow.com/questions/19189649/composite-key-in-cassandra-with-pig/19211546#19211546
The user was attempting to load a single partition using a where clause in a
pig load statement.
CQL Table
{code}
CREATE table data (
occurday text,
seqnumber int,
occurtimems bigint,
unique bigint,
fields maptext, text,
primary key ((occurday, seqnumber), occurtimems, unique)
)
{code}
Pig Load statement Query
{code}
data = LOAD
'cql://ks/data?where_clause=seqnumber%3D10%20AND%20occurday%3D%272013-10-01%27'
USING CqlStorage();
{code}
This results in an exception when processed by the the CqlPagingRecordReader
which attempts to page this query even though it contains at most one
partition key. This leads to an invalid CQL statement.
CqlPagingRecordReader Query
{code}
SELECT * FROM data WHERE token(occurday,seqnumber) ? AND
token(occurday,seqnumber) = ? AND occurday='A Great Day'
AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
{code}
Exception
{code}
InvalidRequestException(why:occurday cannot be restricted by more than one
relation if it includes an Equal)
{code}
I'm not sure it is worth the special case but, a modification to not use the
paging record reader when the entire partition key is specified would solve
this issue.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
