Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id BEB1C200C85 for ; Tue, 16 May 2017 00:13:07 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id BD5A3160BD0; Mon, 15 May 2017 22:13:07 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 17E3B160BC2 for ; Tue, 16 May 2017 00:13:06 +0200 (CEST) Received: (qmail 83527 invoked by uid 500); 15 May 2017 22:13:06 -0000 Mailing-List: contact dev-help@drill.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@drill.apache.org Delivered-To: mailing list dev@drill.apache.org Received: (qmail 83515 invoked by uid 99); 15 May 2017 22:13:06 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 May 2017 22:13:06 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id ACD1EC0386 for ; Mon, 15 May 2017 22:13:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id oFWofWnGkcOX for ; Mon, 15 May 2017 22:13:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id ECA5F5FAF9 for ; Mon, 15 May 2017 22:13:04 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 70ABCE0280 for ; Mon, 15 May 2017 22:13:04 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 2CE3E2431D for ; Mon, 15 May 2017 22:13:04 +0000 (UTC) Date: Mon, 15 May 2017 22:13:04 +0000 (UTC) From: "Paul Rogers (JIRA)" To: dev@drill.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (DRILL-5514) Enhance VectorContainer to merge two row sets MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 15 May 2017 22:13:07 -0000 Paul Rogers created DRILL-5514: ---------------------------------- Summary: Enhance VectorContainer to merge two row sets Key: DRILL-5514 URL: https://issues.apache.org/jira/browse/DRILL-5514 Project: Apache Drill Issue Type: Improvement Affects Versions: 1.10.0 Reporter: Paul Rogers Assignee: Paul Rogers Priority: Minor Fix For: 1.11.0 Consider the concept of a "record batch" in Drill. On the one hand, one can envision a record batch as a stack of records: {code} | a1 | b1 | c1 | ---------------- | a2 | b2 | c2 | {code} But, Drill is columnar. So a record batch is really a "bundle" of vectors: {code} | a1 | | b1 | | c1 | | a2 | | b2 | | c2 | {code} There are times when it is handy to build up a record batch as a merge of two different vector bundles: {code} -- bundle 1 -- -- bundle 2 -- | a1 | | b1 | | c1 | | a2 | | b2 | | c2 | {code} For example, consider a reader. The reader implementation might read columns (a, b) from a file, say. Then, the "{{ScanBatch}}" might add (c) as an implicit vector (the file name, say.) The merged set of vectors comprises the final schema: (a, b, c). This ticket asks for the code to do the merge: * Merge two schemas A = (a, b), B = (c) to create schema C = (a, b, c). * Merge two vector containers C1 and C2 to create a new container, C3, that holds the merger of the vectors from the first two. -- This message was sent by Atlassian JIRA (v6.3.15#6346)