[ 
https://issues.apache.org/jira/browse/PHOENIX-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13979322#comment-13979322
 ] 

rajeshbabu edited comment on PHOENIX-935 at 4/24/14 5:49 AM:
-------------------------------------------------------------

[~jamestaylor]
Thanks for review.
bq. You won't need the following change, as this is a facility to pre-split a 
table. We won't allow a local index to be pre-split or salted -this is an error 
case we catch earlier:
If user table has multiple regions then index table also should have that many 
regions right? otherwise we cannot colocate. We cannot allow user to explicitly 
set splits for index table. Can you give more details about the error cases you 
have mentioned?

I will handle other comments in the next patch. Thanks


was (Author: rajesh23):
[~jamestaylor]
Thanks for review.
bq. You won't need the following change, as this is a facility to pre-split a 
table. We won't allow a local index to be pre-split or salted -this is an error 
case we catch earlier:
If user table has multiple regions then index table also should have that many 
regions right? otherwise we cannot colocate. We cannot allow user to explicitly 
set splits for index table.

> create local index table with the same split keys of user table
> ---------------------------------------------------------------
>
>                 Key: PHOENIX-935
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-935
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: rajeshbabu
>            Assignee: rajeshbabu
>         Attachments: PHOENIX-935.patch
>
>
> For co-locating user table regions and index table regions, the regions key 
> ranges should be same. So when user specify to create local index, internally 
> we can create the index table with the same split keys of user table.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to