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

[jira] [Resolved] (CALCITE-2175) Revisit the assumption made by druid calcite adapter that there is only one timestamp column

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

Danny Chen resolved CALCITE-2175.
---------------------------------
    Fix Version/s: 1.23.0
         Assignee: Danny Chen
       Resolution: Fixed

Fixed in [39e5856|https://github.com/apache/calcite/commit/39e58566c1ac02824d99ae9260d3315539efd57e], thanks for your PR [~chris-baynes] !

> Revisit the assumption made by druid calcite adapter that there is only one timestamp column 
> ---------------------------------------------------------------------------------------------
>
>                 Key: CALCITE-2175
>                 URL: https://issues.apache.org/jira/browse/CALCITE-2175
>             Project: Calcite
>          Issue Type: Task
>          Components: druid-adapter
>            Reporter: Slim Bouguerra
>            Assignee: Danny Chen
>            Priority: Major
>             Fix For: 1.23.0
>
>
> Currently, the Druid Calcite adapter assumes that the row returned by druid has only one timestamp typed column, this is not true, in fact, we can have multiple projections of the time column with extraction functions. Thus code like this need to be revisited. 
> {code}
> int posTimestampField = -1;
> for (int i = 0; i < fieldTypes.size(); i++) {
> if (fieldTypes.get(i) == ColumnMetaData.Rep.JAVA_SQL_TIMESTAMP) {
>  posTimestampField = i;
>  break;
>  }
> }
> {code} 



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