[
https://issues.apache.org/jira/browse/PHOENIX-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15309004#comment-15309004
]
Enis Soztutar commented on PHOENIX-2931:
----------------------------------------
Thinking about this, there is no surefire way to check the first argument to
see whether it is the connection string. If it contains ":", we can assume it
is a connection string, otherwise, we can just check whether it is a file by
checking file exists. Or we can create a smaller compatibility issue, and only
assume a connection string if it contains ":", otherwise we just assume it is a
file. This will break in cases, where only the hostname is provided without the
port or zk-root node, but it maybe fine for Phoenix-5.0.
This is a very critical improvement in user-friendliness, I think we should
have this one way or the other.
> 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)
