[
https://issues.apache.org/jira/browse/CALCITE-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17124487#comment-17124487
]
David Hait commented on CALCITE-4035:
-------------------------------------
Julian Thank you for the rfc6570, I haven't seen it before and I think it's
exactly what we can use on the URL side. Now we need a way specify the mapping
between arbitrary JSON and a table. I've been looking at [JMESPath
|[https://jmespath.org/]] – something like that might be useful here.
> Adapter for REST interface with query or path parameters
> --------------------------------------------------------
>
> Key: CALCITE-4035
> URL: https://issues.apache.org/jira/browse/CALCITE-4035
> Project: Calcite
> Issue Type: New Feature
> Reporter: David Hait
> Priority: Major
>
> A typical microservice with a REST interface will be queryable by an HTTP GET
> with query parameters or path parameters, and return JSON. It would be
> useful to have an adapter that allows access to this sort of interface. One
> use case would be to allow a join between a database table and a table which
> represents the interface. SQL "where" items could be mapped to specific
> query parameters or path parameters on the web API.
> So, for example,
> {{ SELECT * from service.MyEndpoint where id=123;}}
> could get translated into
> {{ GET http:/service/MyEndpoint/123}}
> or alternatively
> {{ GET [http://service/MyEndpoint?id=123]}}
> The mapping between SQL terms and URL path would be specified in a model
> file.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
