You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello!
I came across an issue, where when I drop a view using impyla, then confirming that view is not available (also using impyla) and right after that create the same view, but with use of subprocess and impala-shell (create view query contains impala-shell custom variables which as far as I know are not supported by impyla), the create query returns error "ERROR: AnalysisException: Table already exists: <view_name>".
When I tested this case using only impyla, so drop view, then immediately create the same view again, it works.
It looks like, even though drop view query is correctly executed (confirmed with "show tables" query), when create view with the same name is executed in separate instance (impala-shell in this case), the view is not dropped at all.
Hello!
I came across an issue, where when I drop a view using impyla, then confirming that view is not available (also using impyla) and right after that create the same view, but with use of subprocess and impala-shell (create view query contains impala-shell custom variables which as far as I know are not supported by impyla), the create query returns error "ERROR: AnalysisException: Table already exists: <view_name>".
When I tested this case using only impyla, so drop view, then immediately create the same view again, it works.
It looks like, even though drop view query is correctly executed (confirmed with "show tables" query), when create view with the same name is executed in separate instance (impala-shell in this case), the view is not dropped at all.
Also, it looks similar to #325 issue.
The text was updated successfully, but these errors were encountered: