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, 15 Mar 2018 14:33:00 GMT

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

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

Hey [~giacomotaylor], could you please refer me to the code that populate the global index?
I would like to add a new TAL function for this direct write and use it to populate the global
index.

The local index population does not use the TAL and was fixed using OMID-93

Thx!

> 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
>            Priority: Major
>
> 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
(v7.6.3#76005)

Mime
View raw message