[jira] [Commented] (DRILL-6981) command line option to choose/force drill-override.conf

["Paul Rogers (JIRA)" <ji...@apache.org>]

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

Paul Rogers commented on DRILL-6981:
------------------------------------

As it turns out, Drill already has this feature via the {{--site}} flag:

{noformat}
sqlline --site /path/to/site-dir
{noformat}

Config consists of more than just {{drill-override.conf}} file. The "site" directory provides alternatives to all these files. Suppose the site directory is ${{DRILL_SITE}}:

{noformat}
$DRILL_SITE
|-- jars
    |-- myUdf.jar
|--  lib
    |-- libpam.so
|-- logs
|-- drill-env.sh
|-- drill-override.sh
|-- core-site.xml
...
{noformat}

With a site directory, you can easily have any number of Drill setups on a single machine or network. Also, upgrade is trivial: delete the old Drill directory, install the new one and run. No need to copy files from the old to the new directory.

> command line option to choose/force drill-override.conf 
> --------------------------------------------------------
>
>                 Key: DRILL-6981
>                 URL: https://issues.apache.org/jira/browse/DRILL-6981
>             Project: Apache Drill
>          Issue Type: Wish
>    Affects Versions: 1.15.0
>            Reporter: benj
>            Priority: Minor
>
> It will be nice to have a command line option from sqlline to specify which file to use to override instead of the natural drill-overide.conf.
> Example :
>  
> {code:java}
> ./sqlline --conf=../conf/another-drill-overide.conf
> {code}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)