[
https://issues.apache.org/jira/browse/PHOENIX-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133143#comment-14133143
]
James Taylor commented on PHOENIX-1249:
---------------------------------------
bq. I think currently the indexing for tables with immutable rows is managed
entirely on the client. so no incremental index maintenance is required. Same
thing applicable for local indexes also.
This will give you the worst of both worlds: same write performance as with
current global immutable indexes and the local index read hit for scanning
every region.
bq. Now I have made some changes such that when table is marked as immutable
then preparing local index updates at server side and write to local index
table in the coprocessors without any index maintenance.
+1. This is what [~sunfl] is asking for.
> Support local immutable index
> ------------------------------
>
> Key: PHOENIX-1249
> URL: https://issues.apache.org/jira/browse/PHOENIX-1249
> Project: Phoenix
> Issue Type: Sub-task
> Affects Versions: 4.1
> Environment: Hbase 0.98.4-Hadoop2
> Phoenix 4.1
> Reporter: Sun Fulin
> Assignee: rajeshbabu
> Fix For: 5.0.0, 4.2
>
> Attachments: PHOENIX-1249.patch
>
>
> Currently local indexing are forced created as default mutable index which
> requires index maintenance and server side processing, while immutable
> indexes are appropriate for write-once/append-only use case that may fit for
> many use cases. Hope some work for capability to create local index as
> immutable index.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
