You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@asterixdb.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2019/10/15 14:45:00 UTC

[jira] [Commented] (ASTERIXDB-2648) Inconsistency in dataset distribution for Broadcast Hint

    [ https://issues.apache.org/jira/browse/ASTERIXDB-2648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16951981#comment-16951981 ] 

ASF subversion and git services commented on ASTERIXDB-2648:
------------------------------------------------------------

Commit 2ea7323a2a41be6cd9803450527faa9dfb9a4a6a in asterixdb's branch refs/heads/master from Shiva
[ https://gitbox.apache.org/repos/asf?p=asterixdb.git;h=2ea7323 ]

[ASTERIXDB-2648][COMP] Fix dataset order in broadcast hint

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

details:

- Provides hash-bcast hint to replace bcast hint which makes
broadcast join consistent with other types of joins for choosing
the broadcasting dataset based on dataset order in FROM clause.
- Chooses the build dataset to get broadcast based on the order
in the FROM clause not the WHERE clause (which was the case for
bcast hint).

Change-Id: I505fc8e0bc32c760ae0471c6b302bbfd8499be4a
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/3566
Tested-by: Jenkins <je...@fulliautomatix.ics.uci.edu>
Integration-Tests: Jenkins <je...@fulliautomatix.ics.uci.edu>
Reviewed-by: Dmitry Lychagin <dm...@couchbase.com>


> Inconsistency in dataset distribution for Broadcast Hint
> --------------------------------------------------------
>
>                 Key: ASTERIXDB-2648
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2648
>             Project: Apache AsterixDB
>          Issue Type: Bug
>          Components: COMP - Compiler
>            Reporter: Shiva Jahangiri
>            Priority: Major
>
>  The Broadcast hint (/*+ bcast */) is using the order of the datasets in WHERE clause for a join to choose the broadcasting dataset. This is not consistent with other types of joins such as Hybrid Hash Join and Indexed Nested Loop Join. It can also cause confusion for both user and AsterixDB if the query has more than one condition in the WHERE clause for a join, and order of datasets in these conditions are consistent.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)