phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-1733) doesn't allow connecting with a tenant-specific connection
Date Fri, 17 Apr 2015 20:29:58 GMT


ASF GitHub Bot commented on PHOENIX-1733:

Github user abisek commented on the pull request:
    @gabrielreid - good catch! I updated the code to handle the shell quoting in a platform-specific
    I verified the changes on Unix. I'm going to try it on Windows by end of the day today.

> doesn't allow connecting with a tenant-specific connection
> ---------------------------------------------------------------------
>                 Key: PHOENIX-1733
>                 URL:
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Gabriel Reid
>            Assignee: Abhishek Sreenivasa
>              Labels: Newbie
> Connecting with a client-specific connection via should work with a command
like the following:
> {code}
> ./bin/ 'localhost:2181;TenantId=t1'
> {code}
> However, the command that is built up within 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 should be used for to get around this and similar issues.

This message was sent by Atlassian JIRA

View raw message