[ https://issues.apache.org/jira/browse/CALCITE-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16752735#comment-16752735 ]
Jesus Camacho Rodriguez commented on CALCITE-2802: -------------------------------------------------- PR looks good to me. Thanks [~kgyrtkirk] > Druid adapter: Usage of range conditions like "2010-01-01 < timestamp" leads > to incorrect results > ------------------------------------------------------------------------------------------------- > > Key: CALCITE-2802 > URL: https://issues.apache.org/jira/browse/CALCITE-2802 > Project: Calcite > Issue Type: Bug > Reporter: Zoltan Haindrich > Assignee: Zoltan Haindrich > Priority: Major > > Timestamp range conditions when the timestamp is on left hand side work > correctly; however when the literal is on the left hand side results are > missing. > {code} > @Test > public void testRangeCalc() { > final Fixture2 f = new Fixture2(); > checkDateRange(f, > f.and( > f.le(f.timestampLiteral(2011, Calendar.JANUARY, 1), f.t), > f.le(f.t, f.timestampLiteral(2012, Calendar.FEBRUARY, 2))), > is("[2011-01-01T00:00:00.000Z/2012-02-02T00:00:00.001Z]")); > } > {code} > Fail: > {code} > java.lang.AssertionError: > Expected: is "[2011-01-01T00:00:00.000Z/2012-02-02T00:00:00.001Z]" > but: was "[1900-01-01T00:00:00.000Z/2011-01-01T00:00:00.001Z]" > {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)