You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2023/04/26 22:11:00 UTC
[jira] [Updated] (CALCITE-5676) Appropriately set `DATA_TYPE` and `TYPE_NAME` metadata values for `MEASURE` types
[ https://issues.apache.org/jira/browse/CALCITE-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated CALCITE-5676:
------------------------------------
Labels: pull-request-available (was: )
> Appropriately set `DATA_TYPE` and `TYPE_NAME` metadata values for `MEASURE` types
> ---------------------------------------------------------------------------------
>
> Key: CALCITE-5676
> URL: https://issues.apache.org/jira/browse/CALCITE-5676
> Project: Calcite
> Issue Type: Sub-task
> Components: core
> Reporter: TJ Banghart
> Assignee: TJ Banghart
> Priority: Minor
> Labels: pull-request-available
>
> Subtask of CALCITE-5549 to focus on the metadata we can control in calcite-core. Ensure that schema metadata and result set metadata agree on {{DATA_TYPE}} and {{TYPE_NAME}} for a {{MEASURE}}.
> The challenging part will be writing tests for this. [{{CalciteRemoteDriverTest.java}}|https://github.com/apache/calcite/blob/03050674594152ea785af69517f33960d7e27dd5/core/src/test/java/org/apache/calcite/jdbc/CalciteRemoteDriverTest.java#L99] has some that might be useful but use {{class Employee}} for a schema. We'll need a way to set some test {{MEASURE}} types as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)