[
https://issues.apache.org/jira/browse/PHOENIX-3860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042886#comment-16042886
]
James Taylor commented on PHOENIX-3860:
---------------------------------------
bq. Does the coprocessor update the index with the tombstone information?
Yes. Our IndexMaintainer knows how to interpret the tombstone.
bq. I assume that Tephra uses tombstone and a delete operation during a
transaction is actually a put.
Yes, Tephra uses an empty byte array for the column qualifier to represent a
family delete marker to ensure it sorts first. This works well for Phoenix
because it's not possible to have an empty byte array as the column name.
You can see the code that implements the family delete marker in
TransactionVisibilityFilter. There's a compaction hook in TransactionProcessor
that uses this filter to cause the deleted rows to not be written.
> 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)
