[
https://issues.apache.org/jira/browse/PHOENIX-3583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889845#comment-15889845
]
Ankit Singhal commented on PHOENIX-3583:
----------------------------------------
bq. We have logic on the client-side in MutationState that detects this
condition. We also have logic in our index building code for this (and tests as
well). If there's a known issue, we should fix it.
can you please point me to the code where we are checking for new Index before
building Index mutations at server?
> Prepare IndexMaintainer on server itself
> ----------------------------------------
>
> Key: PHOENIX-3583
> URL: https://issues.apache.org/jira/browse/PHOENIX-3583
> Project: Phoenix
> Issue Type: Bug
> Reporter: Ankit Singhal
> Assignee: Ankit Singhal
> Attachments: PHOENIX-3583.patch
>
>
> -- reuse the cache of PTable and it's lifecycle.
> -- With the new implementation, we will be doing RPC to meta table per mini
> batch which could be an overhead, but the same configuration
> "updateCacheFrequency" can be used to control a frequency of touching
> SYSTEM.CATALOG endpoint for updated Ptable or index maintainers.
> -- It is expected that 99% of the time the table is old and RPC will be
> returned with an empty result(so it may be less costly), as opposed to the
> current implementation where we have to send the index maintainer payload to
> each region server per upsert batch.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
