[jira] [Updated] (DRILL-4741) sqlline scripts should differentiate embedded vs remote config

["James Turton (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DRILL-4741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Turton updated DRILL-4741:
--------------------------------
    Fix Version/s:     (was: 1.21.0)

> sqlline scripts should differentiate embedded vs remote config
> --------------------------------------------------------------
>
>                 Key: DRILL-4741
>                 URL: https://issues.apache.org/jira/browse/DRILL-4741
>             Project: Apache Drill
>          Issue Type: Improvement
>    Affects Versions: 1.8.0
>            Reporter: Paul Rogers
>            Priority: Minor
>
> $DRILL_HOME/bin contains four sqlline-related scripts:
> sqlline -- main script for running sqlline
> drill-conf — Wrapper for sqlline, uses drill config to find Drill. Seems this one needs fixing to use a config other than the hard-coded $DRILL_HOME/conf location.
> drill-embedded — Starts a drill “embedded” in SqlLine, using a local ZK.
> drill-localhost — Wrapper for sqlline, uses a local ZK.
> The last three turn around and call sqlline.
> Behind the scenes, the script call drill-config.sh and drill-env.sh to do setup.
> Note, however that we run Sqlline and Drill in three distinct configurations:
> sqlline as client: should run with light memory
> drillbit as daemon: should run with full memory use
> sqline with embedded drillbit: sqlline needs to run with Drillbit memory options.
> Today, sqlline always uses the Drillbit memory options (and VM options) which results in too much memory and port conflicts when running client-only.
> Provide sqlline specific VM and memory options. Then, the tricky bit, use them only when Drill is not embedded.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)