You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@phoenix.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2018/12/20 20:24:00 UTC

[jira] [Commented] (PHOENIX-3681) Store local indexes in a column family per index

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

Lars Hofhansl commented on PHOENIX-3681:
----------------------------------------

[~rajeshbabu] I somehow missed your comment above. I think your idea in PHOENIX-3566 is the right way to go about it. Are you still thinking about this?

> 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
>            Priority: Major
>
> 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
(v7.6.3#76005)