[
https://issues.apache.org/jira/browse/PHOENIX-1038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeffrey Zhong updated PHOENIX-1038:
-----------------------------------
Attachment: addColumnsToSystemTable.patch
Your patch can work on adding columns to system.catalog(Phoenix-1095). But for
this JIRA, the timestamp passed into addColumnsIfNotExists need to be changed
otherwise it will throw NewerTableAlreadyExistsException.
I attached a unit test for adding columns into system.catalog for you to try
later if there is a need.
> Dynamically add INDEX_TYPE column to SYSTEM.CATALOG if not already there
> ------------------------------------------------------------------------
>
> Key: PHOENIX-1038
> URL: https://issues.apache.org/jira/browse/PHOENIX-1038
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: rajeshbabu
> Assignee: James Taylor
> Fix For: 5.0.0, 4.1
>
> Attachments: PHOENIX-1038.patch, PHOENIX-933.patch,
> addColumnsToSystemTable.patch
>
>
> When a query involves more columns to project than columns in index and query
> condition involves leading columns in local index then first we can get
> matching rowkeys from local index table and then get the required columns
> from data table. In local index both data region and index region co-reside
> in the same RS, we can call get on data region to get the missing columns in
> the index, without any n/w overhead. So it's efficient.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
