[
https://issues.apache.org/jira/browse/PHOENIX-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-2286:
----------------------------------
Attachment: PHOENIX-2286_v2.patch
Patch that checkpoints when necessary. Changes include:
- adding a couple of methods on StatementPlan and MutationPlan to get the
necessary meta data to determine if checkpointing is necessary.
- pulling out transaction specific code and put it in PhoenixStatement so it
doesn't have to be repeated in each MutationPlan.
- encapsulate the Tephra Transaction object in MutationState. Checkpointing
causes the Transaction to change, so best to hide this detail and not have our
code accidentally hold on to stale Transaction objects
Please review [~tdsilva].
> Checkpoint transaction when necessary
> -------------------------------------
>
> Key: PHOENIX-2286
> URL: https://issues.apache.org/jira/browse/PHOENIX-2286
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Attachments: PHOENIX-2286_v1.patch, PHOENIX-2286_v2.patch,
> PHOENIX-2286_wip.patch, PHOENIX-2286_wip2.patch
>
>
> To handle a statement that reads from the same table being updated, we need
> to checkpoint the transaction and adjust the visibility so that it doesn't
> see the data being written. Otherwise, we can get into an infinite loop.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
