How to send the URI parameters to the REST web service via Teiid Spring Boot?

[dieman.one]

My REST web service requires a couple of URI-embedded parameters.

I was assuming (probably wrongly) that the query parameter will be embedded by Teiid into the Web service call as a URL parameter, but my DEBUG logging shows that Teiid makes a cal exactly as described in @sonTable annotation with no parameters.

The I thought  that URI parameters can be embedded using @RestConfiguration annotation - but the purpose of this is sending HTTP header parameters, it seems.

In short: how to make sure that parameters I need to pass to the web service get embedded in the URI Teiid used to invoke my REST web service I am trying to integrate with Teiid?

Thanks!

[rareddy]

I have not thought about it, but you can enter JIRA at Teiid Spring Boot - JBoss Issue Tracker . I guess, you want these parameters to be dynamic, otherwise, you can enter on the endpoint itself.

[dieman.one]

Tried to create an issue, but got the following error, related to default assignee (and it's not possible to change the assignee). My issue summary and description below

SUMMARY: Make it possible to pass URI-embedded parameters to REST web service

DESCRIPTION:

When a REST web service is integrated with Teiid as a data source, it is often necessary to include parameters into the HTTP call that Teiid will use under the hood to invoke the web service.

Example:

http://localhost:8082/artor?type=SUB&query=<query string>

It is often required to pass the query parameters from the "where" clause of  SQL query generated in Teiid, and occasionally some additional parameters as well, so there should be some degree of flexibility as to which parameters are passed.

[rareddy]

Try again, try setting the "assigned" field to "unassigned".

[dieman.one]

Sorry, that field is not visible to me at all.

[rareddy]

Logged [TEIIDSB-106] Provide ability to dynamically provide the URL query parameters for Rest Calls - JBoss Issue Tracker to track this.

[rareddy]

It should be fixed on the master branch right now, will be available from 1.2.0 release.