[
https://issues.apache.org/jira/browse/PHOENIX-2742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15184368#comment-15184368
]
ramkrishna.s.vasudevan commented on PHOENIX-2742:
-------------------------------------------------
[~enis]
Thanks for the explanation. Ya my thought was based on the fact that different
rows cannot be added in the same mutation is what I thought atleast when it
comes to doMiniBatchMutation. There are some areas where we expect rows to be
same, if not there were some exceptions thrown. In case we need to make this
work without hooks then the best part is like you need to change some of the
core doMiniBatchMutation() area such that it can be overridden or plugin new
way of adding mutations. I remember some time back for initial local indexes we
had some private changes (not very sure now). [~rajeshbabu]?
> Add new batchmutate APIs in HRegion without mvcc and region level locks
> -----------------------------------------------------------------------
>
> Key: PHOENIX-2742
> URL: https://issues.apache.org/jira/browse/PHOENIX-2742
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: Rajeshbabu Chintaguntla
> Assignee: Enis Soztutar
> Fix For: 4.8.0
>
>
> Currently we cannot write mutations to same table in (pre/post)BatchMutate
> hooks because of mvcc. It would be better to add new API to Region which
> allows to write to table without locks and also with out memstore size check.
> Need to see how sequence id's going to effect when the API used in
> coprocessor hooks.
> Just raising here to track it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
