[ https://issues.apache.org/jira/browse/PHOENIX-1038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14025474#comment-14025474 ]
James Taylor commented on PHOENIX-1038: --------------------------------------- [~rajesh23] - to test this patch, start Phoenix against 4.0. Then upgrade the cluster to 4.1 and bring it up again. It should dynamically add the INDEX_TYPE column on the first connection to the cluster. > 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)