[jira] [Commented] (CASSANDRA-3680) Add Support for Composite Secondary Indexes
[ https://issues.apache.org/jira/browse/CASSANDRA-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13431932#comment-13431932 ] Yuki Morishita commented on CASSANDRA-3680: --- lgtm, +1. Add Support for Composite Secondary Indexes --- Key: CASSANDRA-3680 URL: https://issues.apache.org/jira/browse/CASSANDRA-3680 Project: Cassandra Issue Type: Sub-task Reporter: T Jake Luciani Assignee: Sylvain Lebresne Labels: cql3, secondary_index Fix For: 1.2 Attachments: 0001-Secondary-indexes-on-composite-columns.txt CASSANDRA-2474 and CASSANDRA-3647 add the ability to transpose wide rows differently, for efficiency and functionality secondary index api needs to be altered to allow composite indexes. I think this will require the IndexManager api to have a maybeIndex(ByteBuffer column) method that SS can call and implement a PerRowSecondaryIndex per column, break the composite into parts and index specific bits, also including the base rowkey. Then a search against a TRANSPOSED row or DOCUMENT will be possible. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-3680) Add Support for Composite Secondary Indexes
[ https://issues.apache.org/jira/browse/CASSANDRA-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13430934#comment-13430934 ] Sylvain Lebresne commented on CASSANDRA-3680: - My bad, pushed a fixed version at https://github.com/pcmanus/cassandra/commits/3680-4. Add Support for Composite Secondary Indexes --- Key: CASSANDRA-3680 URL: https://issues.apache.org/jira/browse/CASSANDRA-3680 Project: Cassandra Issue Type: Sub-task Reporter: T Jake Luciani Assignee: Sylvain Lebresne Labels: cql3, secondary_index Fix For: 1.2 Attachments: 0001-Secondary-indexes-on-composite-columns.txt CASSANDRA-2474 and CASSANDRA-3647 add the ability to transpose wide rows differently, for efficiency and functionality secondary index api needs to be altered to allow composite indexes. I think this will require the IndexManager api to have a maybeIndex(ByteBuffer column) method that SS can call and implement a PerRowSecondaryIndex per column, break the composite into parts and index specific bits, also including the base rowkey. Then a search against a TRANSPOSED row or DOCUMENT will be possible. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-3680) Add Support for Composite Secondary Indexes
[ https://issues.apache.org/jira/browse/CASSANDRA-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13429141#comment-13429141 ] Sylvain Lebresne commented on CASSANDRA-3680: - You're right. Pushed a rebased and fixed version at https://github.com/pcmanus/cassandra/commits/3680-3. Add Support for Composite Secondary Indexes --- Key: CASSANDRA-3680 URL: https://issues.apache.org/jira/browse/CASSANDRA-3680 Project: Cassandra Issue Type: Sub-task Reporter: T Jake Luciani Assignee: Sylvain Lebresne Labels: cql3, secondary_index Fix For: 1.2 Attachments: 0001-Secondary-indexes-on-composite-columns.txt CASSANDRA-2474 and CASSANDRA-3647 add the ability to transpose wide rows differently, for efficiency and functionality secondary index api needs to be altered to allow composite indexes. I think this will require the IndexManager api to have a maybeIndex(ByteBuffer column) method that SS can call and implement a PerRowSecondaryIndex per column, break the composite into parts and index specific bits, also including the base rowkey. Then a search against a TRANSPOSED row or DOCUMENT will be possible. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-3680) Add Support for Composite Secondary Indexes
[
https://issues.apache.org/jira/browse/CASSANDRA-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13429377#comment-13429377
]
Yuki Morishita commented on CASSANDRA-3680:
---
hmm, filtering with key and 2I works, but this time I get wrong value for key.
{code}
cqlsh:3680 select * from blogs;
blog_id | posted_at| author | content
-+--++-
1 | 2012-11-11 00:00:00-0600 |foo | bar
2 | 2012-11-12 00:00:00-0600 |foo | baz
3 | 2012-11-11 00:00:00-0600 |qux |quux
cqlsh:3680 select * from blogs where author='foo' and posted_at = '2012-11-11';
blog_id | posted_at| author | content
-+--++-
2 | 2012-11-11 00:00:00-0600 |foo | bar
{code}
blog_id should be '1'.
{code}
cqlsh:3680 select * from blogs where author='foo';
blog_id | posted_at| author | content
-+--++-
2 | 2012-11-11 00:00:00-0600 |foo | bar
2 | 2012-11-12 00:00:00-0600 |foo | baz
{code}
Here, something is wrong with first row in result set.
Add Support for Composite Secondary Indexes
---
Key: CASSANDRA-3680
URL: https://issues.apache.org/jira/browse/CASSANDRA-3680
Project: Cassandra
Issue Type: Sub-task
Reporter: T Jake Luciani
Assignee: Sylvain Lebresne
Labels: cql3, secondary_index
Fix For: 1.2
Attachments: 0001-Secondary-indexes-on-composite-columns.txt
CASSANDRA-2474 and CASSANDRA-3647 add the ability to transpose wide rows
differently, for efficiency and functionality secondary index api needs to be
altered to allow composite indexes.
I think this will require the IndexManager api to have a
maybeIndex(ByteBuffer column) method that SS can call and implement a
PerRowSecondaryIndex per column, break the composite into parts and index
specific bits, also including the base rowkey.
Then a search against a TRANSPOSED row or DOCUMENT will be possible.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-3680) Add Support for Composite Secondary Indexes
[ https://issues.apache.org/jira/browse/CASSANDRA-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13427369#comment-13427369 ] Sylvain Lebresne commented on CASSANDRA-3680: - I've pushed a rebased version of the patch above at https://github.com/pcmanus/cassandra/commits/3680-2. The previous comments still applies though. Add Support for Composite Secondary Indexes --- Key: CASSANDRA-3680 URL: https://issues.apache.org/jira/browse/CASSANDRA-3680 Project: Cassandra Issue Type: Sub-task Reporter: T Jake Luciani Assignee: Sylvain Lebresne Labels: cql3, secondary_index Fix For: 1.2 Attachments: 0001-Secondary-indexes-on-composite-columns.txt CASSANDRA-2474 and CASSANDRA-3647 add the ability to transpose wide rows differently, for efficiency and functionality secondary index api needs to be altered to allow composite indexes. I think this will require the IndexManager api to have a maybeIndex(ByteBuffer column) method that SS can call and implement a PerRowSecondaryIndex per column, break the composite into parts and index specific bits, also including the base rowkey. Then a search against a TRANSPOSED row or DOCUMENT will be possible. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-3680) Add Support for Composite Secondary Indexes
[
https://issues.apache.org/jira/browse/CASSANDRA-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13427605#comment-13427605
]
Yuki Morishita commented on CASSANDRA-3680:
---
I ran couple of test with above _blogs_ CF(index is created on _author_).
First, insert 3 rows below:
{code}
cqlsh:3680 INSERT INTO blogs (blog_id, posted_at, author, content) VALUES (1,
'2012-11-11', 'foo', 'bar');
cqlsh:3680 INSERT INTO blogs (blog_id, posted_at, author, content) VALUES (2,
'2012-11-12', 'foo', 'baz');
cqlsh:3680 INSERT INTO blogs (blog_id, posted_at, author, content) VALUES (3,
'2012-11-11', 'gux', 'quux');
cqlsh:3680 SELECT * FROM blogs;
blog_id | posted_at| author | content
-+--++-
1 | 2012-11-11 00:00:00-0600 |foo | bar
2 | 2012-11-12 00:00:00-0600 |foo | baz
3 | 2012-11-11 00:00:00-0600 |gux |quux
{code}
Select on indexed column works fine:
{code}
cqlsh:3680 SELECT * FROM blogs WHERE author='foo';
blog_id | posted_at| author | content
-+--++-
1 | 2012-11-11 00:00:00-0600 |foo | bar
2 | 2012-11-12 00:00:00-0600 |foo | baz
{code}
But, query combined with primary key(2nd query below) is not working as
expected:
{code}
cqlsh:3680 SELECT * FROM blogs WHERE posted_at='2012-11-11';
blog_id | posted_at| author | content
-+--++-
1 | 2012-11-11 00:00:00-0600 |foo | bar
3 | 2012-11-11 00:00:00-0600 |gux |quux
cqlsh:3680 SELECT * FROM blogs WHERE posted_at='2012-11-11' AND author='foo';
blog_id | posted_at| author | content
-+--++-
1 | 2012-11-11 00:00:00-0600 |foo | bar
2 | 2012-11-12 00:00:00-0600 |foo | baz
{code}
Here, I expected only row with blog_id=1, but both 1 and 2 are returned.
Add Support for Composite Secondary Indexes
---
Key: CASSANDRA-3680
URL: https://issues.apache.org/jira/browse/CASSANDRA-3680
Project: Cassandra
Issue Type: Sub-task
Reporter: T Jake Luciani
Assignee: Sylvain Lebresne
Labels: cql3, secondary_index
Fix For: 1.2
Attachments: 0001-Secondary-indexes-on-composite-columns.txt
CASSANDRA-2474 and CASSANDRA-3647 add the ability to transpose wide rows
differently, for efficiency and functionality secondary index api needs to be
altered to allow composite indexes.
I think this will require the IndexManager api to have a
maybeIndex(ByteBuffer column) method that SS can call and implement a
PerRowSecondaryIndex per column, break the composite into parts and index
specific bits, also including the base rowkey.
Then a search against a TRANSPOSED row or DOCUMENT will be possible.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-3680) Add Support for Composite Secondary Indexes
[
https://issues.apache.org/jira/browse/CASSANDRA-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13193186#comment-13193186
]
Sylvain Lebresne commented on CASSANDRA-3680:
-
I think there is two things here: the composite parts and the transposed part.
I've created CASSANDRA-3782 to handle the transposed part and to keep this one
focused on the composite part. Both issues are not completely unrelated but I
feel are sufficiently orthogonal to warrant 2 separate tickets.
I'll note however that for this issue we may want to keep the sparse case in
mind. Typically, if I declare:
{noformat}
CREATE TABLE timeline (
userid uuid,
posted_at timestamp,
body text,
posted_by text,
PRIMARY KEY (userid, posted_at)
);
{noformat}
then we want to be able to create an index on say posted_by. Which means it's
really a PerColumnPrefixSecondaryIndex.
Add Support for Composite Secondary Indexes
---
Key: CASSANDRA-3680
URL: https://issues.apache.org/jira/browse/CASSANDRA-3680
Project: Cassandra
Issue Type: New Feature
Reporter: T Jake Luciani
Labels: secondary_index
CASSANDRA-2474 and CASSANDRA-3647 add the ability to transpose wide rows
differently, for efficiency and functionality secondary index api needs to be
altered to allow composite indexes.
I think this will require the IndexManager api to have a
maybeIndex(ByteBuffer column) method that SS can call and implement a
PerRowSecondaryIndex per column, break the composite into parts and index
specific bits, also including the base rowkey.
Then a search against a TRANSPOSED row or DOCUMENT will be possible.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
