Mailing-List: contact dev-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Tue, 7 Mar 2017 17:55:38 +0000 (UTC)
From: "Paul Rogers (JIRA)" <jira@apache.org>
To: dev@drill.apache.org
Message-ID: <JIRA.13048960.1488909317000.3714.1488909338203@Atlassian.JIRA>
In-Reply-To: <JIRA.13048960.1488909317000@Atlassian.JIRA>
References: <JIRA.13048960.1488909317000@Atlassian.JIRA> <JIRA.13048960.1488909317631@jira-lw-us.apache.org>
Subject: [jira] [Created] (DRILL-5323) Provide test tools to create,
 populate and compare row sets
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 07 Mar 2017 17:55:43 -0000

Paul Rogers created DRILL-5323:
----------------------------------

             Summary: Provide test tools to create, populate and compare row sets
                 Key: DRILL-5323
                 URL: https://issues.apache.org/jira/browse/DRILL-5323
             Project: Apache Drill
          Issue Type: Sub-task
    Affects Versions: 1.11.0
            Reporter: Paul Rogers
            Assignee: Paul Rogers
             Fix For: 1.11.0


Operators work with individual row sets. A row set is a collection of records stored as column vectors. (Drill uses various terms for this concept. A record batch is a row set with an operator implementation wrapped around it. A vector container is a row set, but with much functionality left as an exercise for the developer. And so on.)

To simplify tests, we need a {{TestRowSet}} concept that wraps a {{VectorContainer}} and provides easy ways to:

* Define a schema for the row set.
* Create a set of vectors that implement the schema.
* Populate the row set with test data via code.
* Add an SV2 to the row set.
* Pass the row set to operator components (such as generated code blocks.)
* Compare the results of the operation with an expected result set.
* Dispose of the underling direct memory when work is done.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)