[
https://issues.apache.org/jira/browse/PHOENIX-3860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16022877#comment-16022877
]
Ohad Shacham commented on PHOENIX-3860:
---------------------------------------
Thanks for your answer [~giacomotaylor].
In Omid the information of a transaction commit is located at first place in a
table, name commit table, where the transaction manager atomically persists the
commit (transaction id mapped to commit id). Then, the client as a post commit
procedure, adds cells (shadow cells) to the data table. These cells contain the
commit timestamp and denote that the transaction was committed. These cells
version is the transaction id and their value is the commit timestamp. This
stage is an optimization step to refrain access the commit table in every read.
Just to make sure we understand the flow and see that the shadow cells info is
updated and used correctly.
Will the coprocessor update the secondary index table with the shadow cell
information once the post commit procedure adds these to the data table?
I assume that reading always use the tps api? Otherwise, how can we know that
the data was committed? This is also true for reading from the secondary index?
Regarding: "These functions use Tephra's family delete marker directly and not
using the tps api. Could you please let me know what is the reason for that?"
For now I can use Omid's deletion mark to mark deletion. It is a little
different than Tephra's because we are marking the value as opposed to adding a
special qualifier but I guess it has the same semantics. Does this also related
to update the secondary index upon deletion? guess not?
Thanks,
Ohad
> Implement TAL functionality for Omid
> ------------------------------------
>
> Key: PHOENIX-3860
> URL: https://issues.apache.org/jira/browse/PHOENIX-3860
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: Ohad Shacham
> Assignee: Ohad Shacham
>
> Implement TAL functionality for Omid in order to be able to use Omid as
> Phoenix's transaction processing engine.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
