[
https://issues.apache.org/jira/browse/PHOENIX-5404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17110690#comment-17110690
]
Chinmay Kulkarni commented on PHOENIX-5404:
-------------------------------------------
Another option is, if RPCs 3 or 4 fail, we issue a drop table/view to clean up
the header rows etc. left in SYSTEM.CATALOG and continue returning the error
code as per current behavior. Is there any better way to rollback? [~larsh]
[~kadir] [~gjacoby] [~tdsilva]?
> Move check to client side to see if there are any child views that need to be
> dropped while receating a table/view
> ------------------------------------------------------------------------------------------------------------------
>
> Key: PHOENIX-5404
> URL: https://issues.apache.org/jira/browse/PHOENIX-5404
> Project: Phoenix
> Issue Type: Sub-task
> Affects Versions: 5.0.0, 4.15.0
> Reporter: Thomas D'Silva
> Assignee: Chinmay Kulkarni
> Priority: Major
> Fix For: 5.1.0, 4.16.0
>
>
> Remove {{ViewUtil.dropChildViews(env, tenantIdBytes, schemaName,
> tableName);}} call in MetdataEndpointImpl.createTable
> While creating a table or view we need to ensure that are not any child views
> that haven't been clean up by the DropChildView task yet. Move this check to
> the client (issue a scan against SYSTEM.CHILD_LINK to see if a single linking
> row exists).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
