[
https://issues.apache.org/jira/browse/PHOENIX-3908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035300#comment-16035300
]
James Taylor commented on PHOENIX-3908:
---------------------------------------
Good to hear - I think it's due to the force cache update we do for create
view. If it's not too much trouble, it's probably a good idea to add a test for
this in UpdateCacheAcrossDifferentClientsIT.
> 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
> Fix For: 4.11.0
>
>
> 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)
