[
https://issues.apache.org/jira/browse/DRILL-7980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitalii Diravka updated DRILL-7980:
-----------------------------------
Component/s: (was: Query Planning & Optimization)
Web Server
> Pushdowns subquery results as parameters
> ----------------------------------------
>
> Key: DRILL-7980
> URL: https://issues.apache.org/jira/browse/DRILL-7980
> Project: Apache Drill
> Issue Type: Bug
> Components: Web Server
> Affects Versions: 1.19.0
> Reporter: Vitalii Diravka
> Assignee: Vitalii Diravka
> Priority: Major
>
> If a sub query is used to generate parameters for an API call you get 400
> errors and the paramters don't show up on URL in the error.
>
> For Example:
> If you have an API config that requires a "q=" paramter and want to populate
> that with a sub query like this...
>
> {code:java}
> SELECT *
> FROM api.example
> WHERE q IN (SELECT col FROM source){code}
> It doesn't work. The expected behavior would be multiple API calls (one for
> each value in "col") with the results aggregated back together for the
> projection.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
