[jira] [Commented] (CALCITE-4279) SEARCH operator cannot be pushed into Druid
[ https://issues.apache.org/jira/browse/CALCITE-4279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17202934#comment-17202934 ] Stamatis Zampetakis commented on CALCITE-4279: -- Many thanks for picking this up [~julianhyde]. I will follow your suggestion regarding CALCITE-4278. > SEARCH operator cannot be pushed into Druid > --- > > Key: CALCITE-4279 > URL: https://issues.apache.org/jira/browse/CALCITE-4279 > Project: Calcite > Issue Type: Bug > Components: druid-adapter >Reporter: Stamatis Zampetakis >Assignee: Julian Hyde >Priority: Major > Fix For: 1.26.0 > > > CALCITE-4173 and a few other follow ups, introduced a new internal operator, > SEARCH, replacing IN-list and BETWEEN in relational expressions. However, the > code for handling the transformations to Druid was not updated thus the > processing cannot be pushed into Druid. > This is reflected in the IT tests of the Druid adapter where there are about > [22 queries with failures|https://github.com/apache/calcite/runs/1165028611] > at the moment. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CALCITE-4279) SEARCH operator cannot be pushed into Druid
[ https://issues.apache.org/jira/browse/CALCITE-4279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17202370#comment-17202370 ] Julian Hyde commented on CALCITE-4279: -- I'll take this. It may take a few days. In the mean time, feel free to merge CALCITE-4278 with the tests disabled. > SEARCH operator cannot be pushed into Druid > --- > > Key: CALCITE-4279 > URL: https://issues.apache.org/jira/browse/CALCITE-4279 > Project: Calcite > Issue Type: Bug > Components: druid-adapter >Reporter: Stamatis Zampetakis >Priority: Major > > CALCITE-4173 and a few other follow ups, introduced a new internal operator, > SEARCH, replacing IN-list and BETWEEN in relational expressions. However, the > code for handling the transformations to Druid was not updated thus the > processing cannot be pushed into Druid. > This is reflected in the IT tests of the Druid adapter where there are about > [22 queries with failures|https://github.com/apache/calcite/runs/1165028611] > at the moment. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CALCITE-4279) SEARCH operator cannot be pushed into Druid
[ https://issues.apache.org/jira/browse/CALCITE-4279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17202116#comment-17202116 ] Stamatis Zampetakis commented on CALCITE-4279: -- Tests can be done easily by using the code in the PR of CALCITE-4278. > SEARCH operator cannot be pushed into Druid > --- > > Key: CALCITE-4279 > URL: https://issues.apache.org/jira/browse/CALCITE-4279 > Project: Calcite > Issue Type: Bug > Components: druid-adapter >Reporter: Stamatis Zampetakis >Priority: Major > > CALCITE-4173 and a few other follow ups, introduced a new internal operator, > SEARCH, replacing IN-list and BETWEEN in relational expressions. However, the > code for handling the transformations to Druid was not updated thus the > processing cannot be pushed into Druid. > This is reflected in the IT tests of the Druid adapter where there are about > [22 queries with failures|https://github.com/apache/calcite/runs/1165028611] > at the moment. -- This message was sent by Atlassian Jira (v8.3.4#803005)
