[
https://issues.apache.org/jira/browse/PHOENIX-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15297428#comment-15297428
]
Sergey Soldatov commented on PHOENIX-2931:
------------------------------------------
[~jamestaylor] Actually it's only sounds complicated. We have 2 (in case of
psql 3) params. If only 1 provided, we can check whether it's a file on the
file system and if it's not, we consider it as a connection uri. I can't see
any difference between those two approaches. In both cases they may fail with
the message 'Unable to connect to testfile'. But in my case we do not
introduce any file name conventions. Not sure, but for example not all my test
files have an .sql ext. Nor our certification suite (just checked - all files
are .txt :) )
There are a couple others possible solutions like introduce a switch for the
file (something like {{sqlline -f/--file sqlfile}}) or force user to use stdin
( {{sqlline <sqlfile}} )
> Phoenix client asks users to provide configs in cli that are present on the
> machine in hbase conf
> -------------------------------------------------------------------------------------------------
>
> Key: PHOENIX-2931
> URL: https://issues.apache.org/jira/browse/PHOENIX-2931
> Project: Phoenix
> Issue Type: Bug
> Reporter: Alicia Ying Shu
> Assignee: Alicia Ying Shu
> Priority: Minor
> Attachments: PHOENIX-2931.patch
>
>
> Users had complaints on running commands like
> {code}
> phoenix-sqlline
> pre-prod-poc-2.novalocal,pre-prod-poc-10.novalocal,pre-prod-poc-1.novalocal:/hbase-unsecure
> service-logs.sql
> {code}
> However the zookeeper quorum and the port are available in hbase configs.
> Phoenix should read these configs from the system instead of having the user
> supply them every time.
> What we can do is to introduce a keyword "default". If it is specified,
> default zookeeper quorum and port will be taken from hbase configs.
> Otherwise, users can specify their own.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
