[
https://issues.redhat.com/browse/TEIID-5852?page=com.atlassian.jira.plugi...
]
Steven Hawkins edited comment on TEIID-5852 at 2/28/20 12:56 PM:
-----------------------------------------------------------------
The purpose of the dual resolving is to first resolve just the query command, then to
resolve view after adjustments have been made to the metadata. The re-resolving makes it
easier to avoid corner cases with the metadata adjustments. Unless we move the knowledge
of that up into the metadata validation, then we should just leave this as is for now.
was (Author: shawkins):
The purpose of the dual resolving is to first resolve just the query command, then to
resolve view after adjustments have been made to the metadata. I wasn't successful
even with skipping just the reparsing of the sql, let alone the re-resolving as there are
corner cases about each situation. Unless we move the knowledge of that up into the
metadata validation, then we should just leave this as is for now.
views are resolved twice in the metadata validator
--------------------------------------------------
Key: TEIID-5852
URL:
https://issues.redhat.com/browse/TEIID-5852
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Major
Fix For: 13.1
There is an initial resolve to run the Validation visitor, then another resolve in
resolveView. This should be combined as much as possible.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)