You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Julian Hyde (Jira)" <ji...@apache.org> on 2020/10/01 23:56:00 UTC

[jira] [Resolved] (CALCITE-4279) SEARCH operator cannot be pushed into Druid

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

Julian Hyde resolved CALCITE-4279.
----------------------------------
    Resolution: Fixed

Fixed in [64a0ca71|https://github.com/apache/calcite/commit/64a0ca71038da14f0f883f169aa95df00d909e06].

> 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
>              Labels: pull-request-available
>             Fix For: 1.26.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> 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)