[
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
was:
The order of resolving an undefined alias should be:
1. datasets (global aliases -- the second outer most scope)
2. dataverses (global aliases -- the outer most scope)
3. field access (syntactic sugar)
In the current master, 1, 2, and 3 and resolved together without an ordering.
The order of alias resolution shouldn't depend on where the alias is referred.
Component/s: Translator - SQL++
> 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
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
