phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ohad Shacham (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-3860) Implement TAL functionality for Omid
Date Mon, 29 May 2017 14:16:04 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-3860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16028393#comment-16028393
] 

Ohad Shacham commented on PHOENIX-3860:
---------------------------------------


Thanks [~giacomotaylor], I will take a look at the coprocessor.

Omid adds a tombstone for each one of it columns while deleting a column family. I know that
this is inefficient, however, this is the current implementation and we can use it as a first
step.
If I will iterate over allColumns list and add a tombstone for each one of them. Won't it
preserve the same semantics as using the family delete marker in Tephra?

> 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)

Mime
View raw message