phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-3681) Store local indexes in a column family per index
Date Fri, 07 Apr 2017 00:11:41 GMT


Lars Hofhansl commented on PHOENIX-3681:

I think the right thing is to make this declarable. When you create a local index you simply
specify the column family it would go into (the default could remain multiplexing into #0).
That way user have all options to set this up the way they want.

> Store local indexes in a column family per index
> ------------------------------------------------
>                 Key: PHOENIX-3681
>                 URL:
>             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

View raw message