phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-3860) Implement TAL functionality for Omid
Date Wed, 31 May 2017 21:20:04 GMT

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

James Taylor commented on PHOENIX-3860:
---------------------------------------

I'm not sure that's feasible. To be reliable, you'd need to read all cells across all column
families in a row in order to issue a delete against every column qualifier. You'd have a
race condition then too against an upsert (i.e. Put) coming in on that row while the delete
is happening. You could sometimes know in advance what possible column qualifiers a row would
have, but unfortunately not always.

Maybe you could borrow the Tephra filter that enforces column and family deletes through their
own tombstone markers?


> 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