tree 60ed0faeed0fb5722f470b8f68a8a1f6ca535225
parent fba0449ab02c7df056e00efb1bfdf04bf319ef76
author Ali Alsuliman <ali.al.solaiman@gmail.com> 1656098770 +0300
committer Michael Blow <mblow@apache.org> 1675023911 +0000

[ASTERIXDB-3043][COMP] Fix handling of multiple datasources in join branch

- user model changes: no
- storage format changes: no
- interface changes: no

Details:
When analyzing and collecting information from a join branch,
make sure the correct datasource is used instead of using
the first datasource encountered in the branch path.

- Collect and map the datasources variables to their types/source indicators.
- Remove unused isUnnestOverVarAllowed since it's always passed false.
- In case the field name is nested (i.e. there are nested assigns that eventually lead to the datasource), use the optimization context to compute the intermediate nested assign variable.

Change-Id: I1ce48e0bb1198855b6d6d5efad49a19861a3ef98
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/16686
Integration-Tests: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Tested-by: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Reviewed-by: Ali Alsuliman <ali.al.solaiman@gmail.com>
Reviewed-by: Glenn Galvizo <ggalvizo@uci.edu>
Reviewed-by: Wail Alkowaileet <wael.y.k@gmail.com>
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/17349
Reviewed-by: Michael Blow <mblow@apache.org>
Tested-by: Michael Blow <mblow@apache.org>