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] [Updated] (PHOENIX-4099) Do not write table data again when replaying mutations for partial index rebuild
Date Fri, 18 Aug 2017 04:19:00 GMT

     [ https://issues.apache.org/jira/browse/PHOENIX-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

James Taylor updated PHOENIX-4099:
----------------------------------
    Attachment: PHOENIX-4099_v2.patch

When the REPLAY_AT connection property is used, we still need to write the data table mutations,
so v2 of the patch writes a 1 for this case (which was what was written before) or a 2 (when
replaying data writes for partial index rebuild). Backward compat is fine because we're using
the same value as before.

> Do not write table data again when replaying mutations for partial index rebuild
> --------------------------------------------------------------------------------
>
>                 Key: PHOENIX-4099
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4099
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: James Taylor
>            Assignee: James Taylor
>             Fix For: 4.12.0
>
>         Attachments: PHOENIX-4099.patch, PHOENIX-4099_v2.patch
>
>
> There's no need to re-write the data table mutations when we're replaying them to partially
rebuild the index.



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

Mime
View raw message