[
https://issues.apache.org/jira/browse/PHOENIX-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15480923#comment-15480923
]
Lars Hofhansl commented on PHOENIX-3262:
----------------------------------------
PHOENIX-1590 is cool.
Note, it takes 17 seconds when we can throw 4000 core on over 500 machines at a
1/2 TB table :)
Causing massive DML is "bad" design if it can be avoided. Can we change the
design to have a column family per local index? [~chrajeshbab...@gmail.com].
That would also isolate IO of indexes from each other. I guess index
maintainance on split would become less efficient.
Curious, why a separate column family for each main table's column family?
It's still same the row-keys, etc, so the same APIs, just the column family
used would be changed.
There will be times when delete markers are needed, for indexes on views, etc.
> When dropping a local index, delete the column family instead of individual
> rows.
> ---------------------------------------------------------------------------------
>
> Key: PHOENIX-3262
> URL: https://issues.apache.org/jira/browse/PHOENIX-3262
> Project: Phoenix
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Fix For: 4.9.0
>
>
> Currently when Phoenix drops a local index it places a delete marker for
> every single row, instead we can just drop the L#<x> column family.
> {{HBaseAdmin.deleteColumn}} in 0.98. And {{HBaseAdmin.deleteColumnFamily}} in
> 1.0+.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
