]
Barry LaFond updated TEIIDDES-319:
----------------------------------
Fix Version/s: 7.7.1
Request for single table import option in Web Service As Relational
web service
-------------------------------------------------------------------------------
Key: TEIIDDES-319
URL:
https://issues.jboss.org/browse/TEIIDDES-319
Project: Teiid Designer
Issue Type: Feature Request
Affects Versions: Future
Environment: 5.5.3 GA on Linux
Reporter: Greg Haber
Assignee: Barry LaFond
Fix For: 7.7.1
This is a longer term feature request - not expecting any near term resolution.
It would be great if the web service as relational importer could have an option to model
a web service with a single table representing both the request and response, instead of
as separate tables as today. Not sure if it makes sense to allow this for heirarchical
response web services, or only simple ones returning a flat schema.
Whenever possible I always manually model web service connections this way because of the
pros - but would be much better if the importer would do it for me.
Pros:
-Would avoid multiple queries to web service connector for a single web service call
(since XML-Relational connectors don't support join pushdown) - simpler query plans
-With that single call it lessens use/paves way for disabling the XML-Relational
connector internal doc cache (which, at least in 5.0SP2, was a _big_ bottleneck in the
field with concurrent calls to the same web service, if the web service takes more than a
few seconds to respond - I believe because the whole doc cache is locked on both read and
write, effectively resulting in single threaded and blocking behavior. Anyway, just
speculating on the cause, but it is established that in 5.0SP2 that single-table web
services were much faster than multi-table ones).
-Would work in preview
Cons:
-Does not logically represent the way web services actually work
-Confusing as it jumbles together elements from two XML docs in a single relational base
table
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: