[
https://issues.apache.org/jira/browse/ASTERIXDB-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16537842#comment-16537842
]
ASF subversion and git services commented on ASTERIXDB-2405:
------------------------------------------------------------
Commit e93617f8a73abf46a25b94e7f9d7af441f167698 in asterixdb's branch
refs/heads/master from Steven Glenn Jacobs
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=e93617f ]
[ASTERIXDB-2405][COMP] Allow IntroduceJoin to start at delegates
- user model changes: no
- storage format changes: no
- interface changes: no
details:
Previously, IntroduceJoinAccessMethodRule would only start at
the top of a plan (commit or distribute result)
Commit is the only delegate operator in master.
We have one more delegate operator in BAD, which is also the
top of the plan.
This change allows all delegates to be considered by
IntroduceJoinAccessMethodRule as a starting point.
Change-Id: I00172958df8c9ce6dc4cc6b405bc1d6665e2d514
Reviewed-on: https://asterix-gerrit.ics.uci.edu/2740
Sonar-Qube: Jenkins <[email protected]>
Tested-by: Jenkins <[email protected]>
Integration-Tests: Jenkins <[email protected]>
Contrib: Jenkins <[email protected]>
Reviewed-by: Xikui Wang <[email protected]>
> IntroduceJoinAccessMethodUtil doesn't start at delegates other than commit.
> ---------------------------------------------------------------------------
>
> Key: ASTERIXDB-2405
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2405
> Project: Apache AsterixDB
> Issue Type: Improvement
> Reporter: Steven Jacobs
> Priority: Major
>
> Currently, we only have two delegates:
> commit()
> and the BAD delegate, notify-brokers()
> They should both be considered by IntroduceJoinAccessMethodUtil
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
