[
https://issues.apache.org/jira/browse/ASTERIXDB-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921637#comment-17921637
]
Wail Y. Alkowaileet commented on ASTERIXDB-3543:
------------------------------------------------
[~vsarathy1],
Not that I'm aware about the issue itself (an example would help here), but I
assume the issue is that the inline rule is not fired in certain cases. If
that's the case, you can easily detect it using
[DefUseChainComputerVisitor|https://github.com/apache/asterixdb/blob/master/asterixdb/asterix-algebra/src/main/java/org/apache/asterix/optimizer/rules/pushdown/visitor/DefUseChainComputerVisitor.java].
This will compute the def-use (or
[use-def|https://en.wikipedia.org/wiki/Use-define_chain]) chain. In
[PushdownContext|https://github.com/apache/asterixdb/blob/517743261a2c731ffdf841279211c9f4e215185d/asterixdb/asterix-algebra/src/main/java/org/apache/asterix/optimizer/rules/pushdown/PushdownContext.java#L163],
you can get which operators used a defined variable.
CCing [~alsuliman] and [~ritik.raj]
> Investigate single reference inlining rule
> ------------------------------------------
>
> Key: ASTERIXDB-3543
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-3543
> Project: Apache AsterixDB
> Issue Type: Task
> Components: COMP - Compiler
> Reporter: Vijay Sarathy
> Assignee: Vijay Sarathy
> Priority: Major
> Labels: triaged
>
> Query takes too long when field accesses get inlined, resulting in the
> document not being projected early at the beginning of the plan. Investigate
> this issue and suggest improvements as part of this task.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
