Ohad Shacham commented on PHOENIX-3860:

{quote}For the issue with the garbage collector, can we determine in the 
coprocessor that the index is in a "building" state and make sure that no 
garbage collection is done? Or perhaps the commit table can be updated right 
before the index is moved to an active state?

We can add functions in the TAL, and Omid, to disable the data table's garbage 
collection when building an index. However, doing a commit at the end will also 
solve the correctness issue. Your option is still much better since when 
building an index to a large table the probability that the low water exceeds 
the fence id is high and the index creation might starve in this case..... 
Let's do it then, I'll add the functions.


> 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
>            Priority: Major
> Implement TAL functionality for Omid in order to be able to use Omid as 
> Phoenix's transaction processing engine. 
> To support the integration jira [OMID-82] was opened that encapsulates all 
> Omid related development for Phoenix.

This message was sent by Atlassian JIRA

Reply via email to