[jira] [Assigned] (CALCITE-521) Implement metadata requests in remote JDBC driver

["TJ Banghart (Jira)" <ji...@apache.org>]

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

TJ Banghart reassigned CALCITE-521:
-----------------------------------

    Assignee: TJ Banghart

> Implement metadata requests in remote JDBC driver
> -------------------------------------------------
>
>                 Key: CALCITE-521
>                 URL: https://issues.apache.org/jira/browse/CALCITE-521
>             Project: Calcite
>          Issue Type: Bug
>          Components: avatica
>            Reporter: Julian Hyde
>            Assignee: TJ Banghart
>            Priority: Major
>
> The remote JDBC driver supports getCatalogs() and getSchemas(), via requests CatalogsRequest and SchemasRequest. We need to implement more methods:
> * getTables
> * getColumns
> * getTableTypes
> * getProcedures
> * getProcedureColumns
> * getColumnPrivileges
> * getTablePrivileges
> * getBestRowIdentifier
> * getVersionColumns
> * getPrimaryKeys
> * getImportedKeys
> * getExportedKeys
> * getCrossReference
> * getTypeInfo
> * getIndexInfo
> * getUDTs
> * getSuperTypes
> * getSuperTables
> * getAttributes
> * getClientInfoProperties
> * getFunctions
> * getFunctionColumns
> * getPseudoColumns
> Many of these will return empty sets when run against Calcite, because Calcite doesn't override the MetaImpl, and the default implementation returns empty. That's OK. This task is just to create the plumbing from client to server.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)