You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (JIRA)" <ji...@apache.org> on 2012/05/23 23:15:41 UTC
[jira] [Updated] (CASSANDRA-4238) Pig secondary index usage could
be improved
[ https://issues.apache.org/jira/browse/CASSANDRA-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon Williams updated CASSANDRA-4238:
----------------------------------------
Attachment: 4238.txt
Posting what I have here which seems to be complete, but I'm having a hard time testing it. I would think given an index on column 'name' something like 'filter rows by name.value eq "foo"' would work, but while I see getPartitionKeys called setPartitionFilter never does.
> Pig secondary index usage could be improved
> -------------------------------------------
>
> Key: CASSANDRA-4238
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4238
> Project: Cassandra
> Issue Type: Improvement
> Components: Hadoop
> Affects Versions: 1.1.0
> Reporter: Brandon Williams
> Assignee: Brandon Williams
> Attachments: 4238.txt
>
>
> As Dmitriy suggested on CASSANDRA-2246, CassandraStorage could implement LoadMetadata.getPartitionKeys and LoadMetadata.setPartitionFilter to automatically apply secondary indexes.
--
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