Mailing-List: contact dev-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Mon, 14 Mar 2016 06:52:33 +0000 (UTC)
From: "Ian Hellstrom (JIRA)" <jira@apache.org>
To: dev@drill.apache.org
Message-ID: <JIRA.12949775.1457938325000.4958.1457938353438@Atlassian.JIRA>
In-Reply-To: <JIRA.12949775.1457938325000@Atlassian.JIRA>
References: <JIRA.12949775.1457938325000@Atlassian.JIRA>
 <JIRA.12949775.1457938325294@arcas>
Subject: [jira] [Created] (DRILL-4506) Allow substitution variables in SQL
 scripts
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Ian Hellstrom created DRILL-4506:
------------------------------------

             Summary: Allow substitution variables in SQL scripts
                 Key: DRILL-4506
                 URL: https://issues.apache.org/jira/browse/DRILL-4506
             Project: Apache Drill
          Issue Type: Bug
          Components: SQL Parser
            Reporter: Ian Hellstrom


It would be great if substitution variables could be created =C3=A0 la SQL*=
Plus in scripts. This would be especially helpful when objects need to be (=
re-)created from scratch (i.e. in testing), and they share e.g. workspaces,=
 which have to be hard-coded otherwise.

The following is a rough idea (based on SQL*Plus syntax):

{code}
IN_LOCATION=3Dhdfs.project
OUT_LOCATION=3Dhdfs.storage

CREATE VIEW &OUT_LOCATION.view_name AS
SELECT * FROM &IN_LOCATION.table_name;
{code}

For a first implementation, it would be best to have simply substitution va=
riables and not allow computations to be done, although it is conceivable t=
hat that would be a second step.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)