You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2015/02/01 22:35:34 UTC

[jira] [Comment Edited] (PHOENIX-1499) VIEW indexes are not kept in sync when physical table updated directly

    [ https://issues.apache.org/jira/browse/PHOENIX-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14300743#comment-14300743 ] 

James Taylor edited comment on PHOENIX-1499 at 2/1/15 9:35 PM:
---------------------------------------------------------------

[~jchabot] - this issue is not to maintain indexes when Phoenix APIs aren't used. You could potentially write some code to do this yourself - essentially you'd need to push the same metadata that Phoenix does through your CheckAndPut calls. I've opened PHOENIX-1619 for this.


was (Author: jamestaylor):
[~jchabot] - this issue is not to maintain indexes when Phoenix APIs aren't used. You could potentially write some code to do this yourself - essentially you'd need to push the same metadata that Phoenix does through your CheckAndPut calls. I'll open another JIRA for that - there was a lengthy discussion on how that might be possible to do and the various options.

> VIEW indexes are not kept in sync when physical table updated directly
> ----------------------------------------------------------------------
>
>                 Key: PHOENIX-1499
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1499
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: James Taylor
>
> If a physical table is updated directly then the indexes on views over the table will not be maintained.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)