You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2017/06/02 19:21:04 UTC
[jira] [Commented] (PHOENIX-3908) Ensure MetaDataEntityNotFound
handled for CREATE VIEW
[ https://issues.apache.org/jira/browse/PHOENIX-3908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035276#comment-16035276 ]
James Taylor commented on PHOENIX-3908:
---------------------------------------
[~sukunaidu@gmail.com] - please let me know about this one. Thanks!
> Ensure MetaDataEntityNotFound handled for CREATE VIEW
> -----------------------------------------------------
>
> Key: PHOENIX-3908
> URL: https://issues.apache.org/jira/browse/PHOENIX-3908
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: Maddineni Sukumar
>
> 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)