[
https://issues.apache.org/jira/browse/PHOENIX-5994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17156726#comment-17156726
]
Istvan Toth commented on PHOENIX-5994:
--------------------------------------
Getting the metadata directly from the System schema would lead to a lot of
code duplication, and possibly having to handle version differences.
However, using the MetaData API exposed via MateData is not without its
problems either.
Both the Phoenix MetaData implementation and the Avatica proxy implementation
has bugs, see the linked JIRAs.
The new patch fixes and expands the avatica metadata client, rebases the
sqlAlchemy driver to use it, and also rewrites the connection parameter
handling.
Please review!
> SqlAlchemy schema filtering incorrect semantics
> ------------------------------------------------
>
> Key: PHOENIX-5994
> URL: https://issues.apache.org/jira/browse/PHOENIX-5994
> Project: Phoenix
> Issue Type: Bug
> Components: queryserver
> Affects Versions: queryserver-1.0.0
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
>
> The SqlAlchemy driver interprets the _schema=None_ parameter as any/all
> schema.
> According to the SqlAlchemy docs this should mean default schema.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
