[
https://issues.apache.org/jira/browse/KNOX-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Larry McCay resolved KNOX-2224.
-------------------------------
Resolution: Fixed
> KnoxLine and KnoxShell DataSource and Select Command Alignment
> --------------------------------------------------------------
>
> Key: KNOX-2224
> URL: https://issues.apache.org/jira/browse/KNOX-2224
> Project: Apache Knox
> Issue Type: Improvement
> Components: KnoxShell
> Reporter: Larry McCay
> Assignee: Larry McCay
> Priority: Major
> Fix For: 1.4.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The KnoxLine shell environment datasource selection creates the connection
> for the session. The connection is kept for the session or until datasource
> select is used to create a connection to a new datasource. Each SQL query
> continues to use the same connection. The connections are cleaned up and
> closed through a shutdown hook for the KnoxLine environment.
> In the interactive KnoxShell there are Custom Groovy Commands for datasource
> management and SQL queries submission. The life of the connection is limited
> to each command rather than being able to be used again in subsequent
> queries. Connections are closed for each query. This requires a new
> connection and login per query - since login isn't done at datasource
> selection time like it is in KnoxLine.
> This change aligns the two environments. Connections are managed at the shell
> environment level rather than at the command level. Connections are created
> when selecting datasources rather than and SQL query invocation. Connections
> are cleaned up in the interactive shell through a shutdown hook.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
