[
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
Updated patch to fix minor problems. What I've discovered is that pig wants to
match on the _tuple_ named 'name' and as far as I can tell, there's no way for
getPartitionKeys to specify anything deeper, such as name.value. This would
almost be ok, at the cost of silly syntax like "filter rows by name eq ('name',
'foo')" except when setPartitionFilter is called, we unsurprisingly get get the
string literal "(name, foo)" as the value to match against, which of course is
not in the index. I'm not sure what, if anything, can be done about this.
> 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
