phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abhishek Sreenivasa (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (PHOENIX-1733) sqlline.py doesn't allow connecting with a tenant-specific connection
Date Thu, 16 Apr 2015 00:40:58 GMT

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

Abhishek Sreenivasa reassigned PHOENIX-1733:
--------------------------------------------

    Assignee: Abhishek Sreenivasa

> sqlline.py doesn't allow connecting with a tenant-specific connection
> ---------------------------------------------------------------------
>
>                 Key: PHOENIX-1733
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1733
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Gabriel Reid
>            Assignee: Abhishek Sreenivasa
>              Labels: Newbie
>
> Connecting with a client-specific connection via sqlline.py should work with a command
like the following:
> {code}
> ./bin/sqlline.py 'localhost:2181;TenantId=t1'
> {code}
> However, the command that is built up within sqlline.py doesn't correctly quote the JDBC
url, so the JDBC url parameter ends up as:
> {code}
> jdbc:phoenix:localhost:2181;TenantId=t1
> {code}
> without quoting. This causes the semicolon to be interpreted as a command separator by
the shell, effectively ignoring it (and any other parameters).
> Proper parameter quoting (as done with the pipes module in psql.py) should be used for
sqlline.py to get around this and similar issues.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message