drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-4163) Support schema changes for MergeJoin operator.
Date Sat, 05 Dec 2015 00:41:10 GMT

    [ https://issues.apache.org/jira/browse/DRILL-4163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15042488#comment-15042488

ASF GitHub Bot commented on DRILL-4163:

GitHub user amithadke opened a pull request:


    DRILL-4163 Schema changes support in MergeJoin Operator.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/amithadke/drill mergejoin-schemachanges

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #292
commit 7daf7071748231073dc41b8871712af677ad4ab3
Author: Amit Hadke <amit.hadke@gmail.com>
Date:   2015-12-05T00:38:36Z

    DRILL-4163 Schema changes support in MergeJoin Operator.


> Support schema changes for MergeJoin operator.
> ----------------------------------------------
>                 Key: DRILL-4163
>                 URL: https://issues.apache.org/jira/browse/DRILL-4163
>             Project: Apache Drill
>          Issue Type: Improvement
>            Reporter: amit hadke
>            Assignee: amit hadke
> Since external sort operator supports schema changes, allow use of union types in merge
join to support for schema changes.
> For now, we assume that merge join always works on record batches from sort operator.
Thus merging schemas and promoting to union vectors is already taken care by sort operator.
> Test Cases:
> 1) Only one side changes schema (join on union type and primitive type)
> 2) Both sids change schema on all columns.
> 3) Join between numeric types and string types.
> 4) Missing columns - each batch has different columns. 

This message was sent by Atlassian JIRA

View raw message