phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ankit Singhal (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (PHOENIX-3376) Physical table for indexes on views isn't use same schema as table
Date Thu, 13 Oct 2016 13:17:20 GMT

     [ https://issues.apache.org/jira/browse/PHOENIX-3376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ankit Singhal reassigned PHOENIX-3376:
--------------------------------------

    Assignee: Ankit Singhal

> 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.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)

Mime
View raw message