[
https://issues.apache.org/jira/browse/PHOENIX-3860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021247#comment-16021247
]
Ohad Shacham commented on PHOENIX-3860:
---------------------------------------
Hi [~giacomotaylor], [~tdsilva] and [~samarthjain],
I am looking at function delete at PTableImpl and at function
getDeleteTypeOrNull at IndexMaintainer.
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? Is this related to
the secondary index access outside of the TPS api? if so, what is the
advantages of using the table directly v.s. the transaction processor api?
I am trying to understand how this works in order to be able to implement this
for Omid. Another issue that should be handled in this case is the shadow cells
update and the commit table access. In case the secondary index maintenance is
being done outside of the tps api then someone should be responsible to access
the commit table when needed and also update the shadow cells upon commit.
Thx,
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)
