[ 
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:

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.

  was:
The order of resolving an undefined alias should be:

1. datasets (global aliases -- the second outer most scope)
2. dataverse (global aliases -- the outer most scope)
3. field access

In the current master, 1, 2, and 3 and resolved together without an ordering.


> The order of resolving undefined aliases
> ----------------------------------------
>
>                 Key: ASTERIXDB-1650
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-1650
>             Project: Apache AsterixDB
>          Issue Type: Bug
>            Reporter: Yingyi Bu
>            Assignee: Yingyi Bu
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to