[
https://issues.apache.org/jira/browse/PHOENIX-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14322252#comment-14322252
]
Jerry Chabot commented on PHOENIX-1619:
---------------------------------------
Our project was to far in development to change to using the Phoenix APIs.
Besides, we rely and CheckAndPut so I don't see how we could use the Phoenix
APIs and ensure an atomic write. If our code were to update the Phoenix index
(#3) doesn't that mean the operation is not atomic so we need to address
inconsistencies. I'd like to avoid this as it complexity.
Can you explain what is MutationState? Are there code example using it?
> 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)
