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-4484) Write directly to HBase when creating an index for transactional table
Date Thu, 21 Dec 2017 14:48:00 GMT

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

Ohad Shacham commented on PHOENIX-4484:
---------------------------------------

[~giacomotaylor], [~tdsilva].

Guys, this is what we have discuss to write the data directly to HBase when creating an index
for a non-empty table.

> Write directly to HBase when creating an index for transactional table
> ----------------------------------------------------------------------
>
>                 Key: PHOENIX-4484
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4484
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: Ohad Shacham
>            Assignee: Ohad Shacham
>
> Today, when creating an index table for a non empty data table. The writes are performed
using the transaction api and both consumes client side memory, for storing the writeset,
and checks for conflict analysis upon commit. This is redundant and can be replaced by direct
write to HBase. For this reason, a new function in the transaction abstraction layer should
be added that writes directly to HBase at the Tephra's case and adds shadow cells with the
fence id at the Omid case. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message