[
https://issues.apache.org/jira/browse/CASSANDRA-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-4238:
----------------------------------------
Attachment: 4238-v2.txt
v2 implements a workaround. If PIG_PARTITION_FILTER is enabled, then each
index (actual index, not plain validation) is appended as a top-level field to
the schema after the bag, and the name has '_index' appended. Thus, if there
is an index on a column called 'name', you can use it with a statement like
"filter rows by name_index eq 'foo'".
The caveat to this is that we have to relax the putNext function a bit to
ignore these fields, so if you have this enabled and are storing a completely
bad schema, it will just silently drop your bad fields as well. However this
is a small price to pay for the added functionality.
> 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-v2.txt, 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
