[
https://issues.apache.org/jira/browse/PHOENIX-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15297338#comment-15297338
]
Alicia Ying Shu commented on PHOENIX-2931:
------------------------------------------
[~jamestaylor] Discussed this offline with [~sergey.soldatov] regarding to how
to find the connection string. For psql.py, if there is any parameter without
directive ('-' or '--'), will check whether it exists on file system. If not,
assume it is a connection string, we are done. In this case, if it was a file
and because it did not exit, the connection would fail anyway.
If it exists on file system, found a file and continue looking for connection
string. If not finding any, construct the connection string from
hbase-site.xml. If find another string, we are done.
Similar logic apply to sqlline.py as well. We can lift the requirement that
connection string must be present as the 1st parameter when establishing a
connection.
> 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)
