[
https://issues.apache.org/jira/browse/ASTERIXDB-2174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625900#comment-16625900
]
ASF subversion and git services commented on ASTERIXDB-2174:
------------------------------------------------------------
Commit 36e20b78bb1584538c9844e2e7398eacf8dd3fb8 in asterixdb's branch
refs/heads/master from luochen01
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=36e20b7 ]
[ASTERIXDB-2174] Use ListSet when clone partition property
- user model changes: no
- storage format changes: no
- interface changes: no
Details:
- Use ListSet instead of HashSet when cloning partitioning properties
to ensure it has the consistent behavior as before.
Change-Id: Ib2b8c1715d75b387a73504f4709524d9ab9ce123
Reviewed-on: https://asterix-gerrit.ics.uci.edu/2968
Sonar-Qube: Jenkins <[email protected]>
Tested-by: Jenkins <[email protected]>
Integration-Tests: Jenkins <[email protected]>
Reviewed-by: Dmitry Lychagin <[email protected]>
> Improve partitioning property propagation in
> AbstractPreclusteredGroupByPOperator
> ---------------------------------------------------------------------------------
>
> Key: ASTERIXDB-2174
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2174
> Project: Apache AsterixDB
> Issue Type: Improvement
> Components: COMP - Compiler
> Reporter: Dmitry Lychagin
> Assignee: Dmitry Lychagin
> Priority: Minor
>
> Currently AbstractPreclusteredGroupByPOperator propagates its input
> partitioning property as is. For example if "gby var1 as var2" and input is
> partitioned on "var1" the output partitioning would also be reported on
> "var1". The problem is that "var1" is not visible after the group by. The
> variable in the output partitioning property should be changed from "var1" to
> "var2" because both these variables are bound to the same value and "var2" is
> visible after the group by.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
