[
https://issues.apache.org/jira/browse/ASTERIXDB-3496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17909567#comment-17909567
]
ASF subversion and git services commented on ASTERIXDB-3496:
------------------------------------------------------------
Commit 90716b091c0bb9b5c83603cc963054bb9de17187 in asterixdb's branch
refs/heads/master from murali4104
[ https://gitbox.apache.org/repos/asf?p=asterixdb.git;h=90716b091c ]
[ASTERIXDB-3496][COMP] Array Unnest Optimization
- user model changes: no
- storage format changes: no
- interface changes: no
Details:
Unnest Array operations are moved to more optimal locations in the plan
if possible. Think of Unnest Array ops as UDFs. A UDF can be very
expensive, so moving it to a place in the plan where the cardinality
is low is a good optimization. Similarly, when UNNEST ops are moved
above a join, the join gets less expensive as an UNNEST operation will
usually increase the cardinality and hence make the join more expensive.
Ext-ref: MB-64228
Change-Id: I103cdf840821a4c0c91cf3221f906cae75f053da
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/19209
Reviewed-by: Peeyush Gupta <[email protected]>
Tested-by: Peeyush Gupta <[email protected]>
> Move Array field access Unnest Operator as high up in the tree as possible
> --------------------------------------------------------------------------
>
> Key: ASTERIXDB-3496
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-3496
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: *DB - AsterixDB
> Reporter: murali krishna
> Priority: Major
> Labels: triaged
>
> Q3 is CH2 improves by a factor of 2x when the array unnest operation is moved
> higher up.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
