You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Thomas D'Silva (JIRA)" <ji...@apache.org> on 2019/01/08 23:02:00 UTC
[jira] [Updated] (PHOENIX-3376) Physical table for indexes on views
isn't use same schema as table
[ https://issues.apache.org/jira/browse/PHOENIX-3376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas D'Silva updated PHOENIX-3376:
------------------------------------
Fix Version/s: (was: 4.15.0)
> 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
> Priority: Major
>
> 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
(v7.6.3#76005)