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

James Taylor commented on PHOENIX-3376:
---------------------------------------

[~an...@apache.org] - do you think you could take a look? We have to be a bit 
careful about backward compatibility. Perhaps we can keep the existing behavior 
when namespaces is off, but use the correct one when it's on?

> Physical table for indexes on views isn't use same schema as table
> ------------------------------------------------------------------
>
>                 Key: PHOENIX-3376
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3376
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>             Fix For: 4.9.0
>
>
> See this code in ConnectionQueryServicesImpl:
> {code}
>     private void ensureViewIndexTableCreated(byte[] physicalTableName, 
> Map<String, Object> tableProps,
>             List<Pair<byte[], Map<String, Object>>> families, byte[][] 
> splits, long timestamp,
>             boolean isNamespaceMapped) throws SQLException {
>         byte[] physicalIndexName = 
> MetaDataUtil.getViewIndexPhysicalName(physicalTableName);
> {code}
> We should get rid of the {{MetaDataUtil.getViewIndexPhysicalName()}} function 
> and use the appropriate one.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to