[
https://issues.apache.org/jira/browse/PHOENIX-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-1619:
----------------------------------
Description: A read-only/mapped view does not maintain its secondary
indexes. This is by design currently, as the Phoenix APIs are being bypassed so
there's not much Phoenix can do. However, it would be possible for a client to
push the same metadata that Phoenix does through the HBase API for this to
occur. Phoenix may be able to provide some APIs to make this easier. (was: A
read-only/mapped view does not maintain its secondary indexes. This is by
design currently, as the Phoenix APIs are being bypassed so there's not much
Phoenix can do. However, it would be possible for a client to push the same
metadata that Phoenix does through the HBase API for this to occur.)
> Read-only/mapped views directly on HBase tables do not maintain secondary
> indexes
> ---------------------------------------------------------------------------------
>
> Key: PHOENIX-1619
> URL: https://issues.apache.org/jira/browse/PHOENIX-1619
> Project: Phoenix
> Issue Type: New Feature
> Reporter: James Taylor
>
> A read-only/mapped view does not maintain its secondary indexes. This is by
> design currently, as the Phoenix APIs are being bypassed so there's not much
> Phoenix can do. However, it would be possible for a client to push the same
> metadata that Phoenix does through the HBase API for this to occur. Phoenix
> may be able to provide some APIs to make this easier.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
