[jira] [Updated] (PHOENIX-1038) Dynamically add INDEX_TYPE column to SYSTEM.CATALOG if not already there

["James Taylor (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/PHOENIX-1038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Taylor updated PHOENIX-1038:
----------------------------------

    Attachment: PHOENIX-933.patch

This change, along with adding the INDEX_TYPE column to the schema of the SYSTEM.CATALOG table should be done in 3.0 as well. Keeping the schema the same between 3.1 and 4.1 will make it easier for folks to migrate from 3.1 to 4.1.

> 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: rajeshbabu
>         Attachments: PHOENIX-933.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)