[
https://issues.apache.org/jira/browse/ASTERIXDB-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yingyi Bu updated ASTERIXDB-1650:
---------------------------------
Description:
The order of resolving an undefined alias should be:
Have different resolving mechanism for FROM/UNNEST/Quantifier and others:
-- FROM/UNNEST/Quantifier: 1. user-defined variables, 2. Datasets
-- Others: 1. user-defined variables, 2. field-accesses, 3. Datasets
Always resolving to a dataset as the last option can preserve query stability
such that the query semantics will not be perturbed by adding/removing a
dataset.
was:
The order of resolving an undefined alias should be:
Have different resolving mechanism for FROM/UNNEST/Quantifier and others:
-- FROM/UNNEST/Quantifier: 1. user-defined variables, 2. Datasets
-- Others: 1. user-defined variables, 2. field-accesses, 3. Datasets
> The order of resolving undefined aliases
> ----------------------------------------
>
> Key: ASTERIXDB-1650
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-1650
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: Translator - SQL++
> Reporter: Yingyi Bu
> Assignee: Yingyi Bu
>
> The order of resolving an undefined alias should be:
> Have different resolving mechanism for FROM/UNNEST/Quantifier and others:
>
> -- FROM/UNNEST/Quantifier: 1. user-defined variables, 2. Datasets
> -- Others: 1. user-defined variables, 2. field-accesses, 3. Datasets
> Always resolving to a dataset as the last option can preserve query stability
> such that the query semantics will not be perturbed by adding/removing a
> dataset.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
