You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Francis Chuang (Jira)" <ji...@apache.org> on 2020/08/14 00:51:00 UTC

[jira] [Updated] (CALCITE-4174) avatica-go should handle complex/long URLs

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

Francis Chuang updated CALCITE-4174:
------------------------------------
    Fix Version/s: avatica-1.18.0

> avatica-go should handle complex/long URLs
> ------------------------------------------
>
>                 Key: CALCITE-4174
>                 URL: https://issues.apache.org/jira/browse/CALCITE-4174
>             Project: Calcite
>          Issue Type: Improvement
>          Components: avatica-go
>            Reporter: Josiah Goodson
>            Assignee: Josiah Goodson
>            Priority: Major
>             Fix For: avatica-1.18.0
>
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> The current avatica-go driver assumes the full URL path is the schema name. This is incorrect for some deployments - for example, using a proxy.
> Current behavior:
> dsn = "http://host.com/service/proxy/schema"
> conf.schema = "service/proxy/schema"
> Expected behavior:
> dsn = "http://host.com/service/proxy/schema"
> conf.schema = "schema"



--
This message was sent by Atlassian Jira
(v8.3.4#803005)