phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-3908) Ensure MetaDataEntityNotFound handled for CREATE VIEW
Date Fri, 02 Jun 2017 22:49:04 GMT

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

James Taylor updated PHOENIX-3908:
----------------------------------
    Issue Type: Sub-task  (was: Bug)
        Parent: PHOENIX-3819

> Ensure MetaDataEntityNotFound handled for CREATE VIEW
> -----------------------------------------------------
>
>                 Key: PHOENIX-3908
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3908
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: James Taylor
>            Assignee: Maddineni Sukumar
>             Fix For: 4.11.0
>
>         Attachments: PHOENIX-3908.patch
>
>
> We may already handle this (if so please close), but it's possible that a CREATE VIEW
statement could reference a table that was created in a different connection. We should add
a test for this in UpdateCacheAcrossDifferentClientsIT and a similar retry loop as was done
in PhoenixStatement within CreateTableCompiler here:
> {code}
>         return new BaseMutationPlan(context, operation) {
>             @Override
>             public MutationState execute() throws SQLException {
>                 try {
>                     return client.createTable(finalCreate, splits, parent, viewStatement,
viewType, viewColumnConstants, isViewColumnReferenced);
>                 } finally {
>                     if (client.getConnection() != connection) {
>                         client.getConnection().close();
>                     }
>                 }
>             }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message