[
https://issues.apache.org/jira/browse/PHOENIX-4026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16116154#comment-16116154
]
Lars Hofhansl edited comment on PHOENIX-4026 at 8/7/17 6:57 AM:
----------------------------------------------------------------
We can try to keep the current logic, but do the Puts on the region server
holding the index region as ASYNC writes. But I think that does not solve the
main problem when the index region is temporarily unavailable due to split or
move, so probably won't help much.
was (Author: lhofhansl):
We can try to keep the current logic, but the Puts on the region server holding
the index region with ASYNC puts. But I think that does not solve the main
problem when the index region is temporarily unavailable due to split or move,
so probably won't help much.
> Option to not wait on global mutable index write to complete
> ------------------------------------------------------------
>
> Key: PHOENIX-4026
> URL: https://issues.apache.org/jira/browse/PHOENIX-4026
> Project: Phoenix
> Issue Type: Bug
> Reporter: Samarth Jain
> Attachments: PHOENIX-4026_wip.patch
>
>
> Today, a data table update synchronously waits for the index update to
> complete. While some users may want that kind of strong consistency, some may
> be ok with the call to return once the data table write is done.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
