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

ASF GitHub Bot commented on PHOENIX-5018:
-----------------------------------------

GitHub user kadirozde opened a pull request:

    https://github.com/apache/phoenix/pull/414

    PHOENIX-5018 Index mutations created by IndexTool will have wrong tim…

    …estamps

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/kadirozde/phoenix PHOENIX-5018

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/phoenix/pull/414.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #414
    
----
commit 3e316ddc4a63a1474245a220e0a3b60cad52c008
Author: Kadir <kozdemir@...>
Date:   2018-12-11T21:10:09Z

    PHOENIX-5018 Index mutations created by IndexTool will have wrong timestamps

----


> Index mutations created by IndexTool will have wrong timestamps
> ---------------------------------------------------------------
>
>                 Key: PHOENIX-5018
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5018
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.14.0, 5.0.0
>            Reporter: Geoffrey Jacoby
>            Assignee: Kadir OZDEMIR
>            Priority: Major
>
> When doing a full rebuild (or initial async build) on an index using the 
> IndexTool and PhoenixIndexImportDirectMapper, we generate the index mutations 
> by creating an UPSERT SELECT query from the base table to the index, then 
> taking the Mutations from it and inserting it directly into the index via an 
> HBase HTable. 
> The timestamps of the Mutations use the default HBase behavior, which is to 
> take the current wall clock. However, the timestamp of an index KeyValue 
> should use the timestamp of the initial KeyValue in the base table.
> Having base table and index timestamps out of sync can cause all sorts of 
> weird side effects, such as if the base table has data with an expired TTL 
> that isn't expired in the index yet. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to