[
https://issues.apache.org/jira/browse/PHOENIX-3376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15699897#comment-15699897
]
James Taylor commented on PHOENIX-3376:
---------------------------------------
Yes, this is still an issue, I believe, [[email protected]]. Let's get rid of
any usages of the util func mentioned in the description and add a couple of
unit tests.
> 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
> Assignee: Ankit Singhal
> Fix For: 4.10.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)
