You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "slim bouguerra (JIRA)" <ji...@apache.org> on 2018/02/12 15:47:00 UTC

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

slim bouguerra created CALCITE-2175:
---------------------------------------

             Summary: 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
            Reporter: slim bouguerra
            Assignee: Julian Hyde


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
(v7.6.3#76005)