drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Rogers (JIRA)" <j...@apache.org>
Subject [jira] [Created] (DRILL-5258) Allow "extended" mock tables access from SQL queries
Date Sun, 12 Feb 2017 03:33:41 GMT
Paul Rogers created DRILL-5258:
----------------------------------

             Summary: Allow "extended" mock tables access from SQL queries
                 Key: DRILL-5258
                 URL: https://issues.apache.org/jira/browse/DRILL-5258
             Project: Apache Drill
          Issue Type: Improvement
    Affects Versions: 1.10
            Reporter: Paul Rogers
            Assignee: Paul Rogers
            Priority: Minor
             Fix For: 1.10


DRILL-5152 provided a simple way to generate sample data in SQL using a new, simplified version
of the mock data generator. This approach is very convenient, but is inherently limited. For
example, the limited syntax available in SQL does not encoding much information about columns
such as repeat count, data generator or so on. The simple SQL approach does not allow generating
multiple groups of data.

However, all these features are present in the original mock data source via a special JSON
configuration file. Previously, only physical plans could access that extended syntax.

This ticket requests a SQL interface to the extended mock data source:

{code}
SELECT * FROM `mock`.`example/mock-options.json`
{code}

Mock data source options are always stored as a JSON file. Since the existing mock data generator
for SQL never uses JSON files, a simple rule is that if the table name ends in ".json" then
it is a specification, else the information is encoded in table and column names.

The format of the data generation syntax is documented in the mock data source classes.



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

Mime
View raw message