[
https://issues.apache.org/jira/browse/PHOENIX-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15872814#comment-15872814
]
Lars Hofhansl commented on PHOENIX-3681:
----------------------------------------
Even better would be if at local index creation time one could declare which
column family an index should be stored in. Phoenix would have to have a little
smarts to know when it can drop an index by dropping the column family and when
to place delete markers instead, but that's doable.
That way it's the application that makes these decisions.
> Store local indexes in a column family per index
> ------------------------------------------------
>
> Key: PHOENIX-3681
> URL: https://issues.apache.org/jira/browse/PHOENIX-3681
> Project: Phoenix
> Issue Type: Bug
> Reporter: Lars Hofhansl
>
> Currently all local indexes are stored in a single column family. That makes
> maintenance (such as dropping an index) more expensive than necessary.
> Let's have each local index in its own column family (or be able to declare
> which column family an index should go into).
> As [~jamestaylor] points out, this won't work for indexes on views as there
> might be 1000's of them.
> Another issue are covered local indexes, but I'd argue that local indexes
> would benefit little from being covered. (that also needs to be
> experimentally verified)
> Local indexes in individual column families would be great to isolate any
> maintenance and even usage from each other.
> [~rajeshbabu], [~mujtabachohan]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
