You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Istvan Toth (Jira)" <ji...@apache.org> on 2021/03/04 18:40:00 UTC

[jira] [Updated] (PHOENIX-6405) Disallow bulk loading into non-empty tables with global secondary indexes

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

Istvan Toth updated PHOENIX-6405:
---------------------------------
    Description: 
It is very easy to end up with inconsistent indexes when bulk loading data into non-empty tables with global secondary indexes.

Checking if the table is empty, and refusing to do the bulk load if it is not, unless a sufficiently scary override like *--corruptindexes* is also provided would probably reduce the risk.

We should also check if the same problem exists for local indexes.

  was:
It is very easy to end up with inconsistent indexes when bulk loading data into non-empty tables with secondary indexes.

Checking if the table is empty, and refusing to do the bulk load if it is not, unless a sufficiently scary override like *--corruptindexes* is also provided would probably reduce the risk.

        Summary: Disallow bulk loading into non-empty tables with global secondary indexes  (was: Disallow bulk loading into non-empty tables with secondary indexes)

> Disallow bulk loading into non-empty tables with global secondary indexes
> -------------------------------------------------------------------------
>
>                 Key: PHOENIX-6405
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-6405
>             Project: Phoenix
>          Issue Type: New Feature
>          Components: core
>            Reporter: Istvan Toth
>            Priority: Major
>
> It is very easy to end up with inconsistent indexes when bulk loading data into non-empty tables with global secondary indexes.
> Checking if the table is empty, and refusing to do the bulk load if it is not, unless a sufficiently scary override like *--corruptindexes* is also provided would probably reduce the risk.
> We should also check if the same problem exists for local indexes.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)