[
https://issues.jboss.org/browse/TEIID-3290?page=com.atlassian.jira.plugin...
]
Ramesh Reddy resolved TEIID-3290.
---------------------------------
Labels: Beta2 (was: )
Resolution: Done
During the execution of the procedure, the new routine consults the underlying metadata of
the procedure for parameter types and converts them from string to target type before
executing. Thus in case of XML the string will not be truncated at 4000 chars.
Another lingering issue with larger payloads is, at the first stage of parameter
consumption at the REST layer is still is String, that means the payload value is being
materialized, which is bad in terms of memory management. Not sure how one can read stream
version of parameter.
Auto generated REST WAR truncates the larger payloads
-----------------------------------------------------
Key: TEIID-3290
URL:
https://issues.jboss.org/browse/TEIID-3290
Project: Teiid
Issue Type: Bug
Affects Versions: 8.4
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Priority: Blocker
Labels: Beta2
Fix For: 8.7.1, 8.10
Currently only query parameters are supported as the input parameters to the Teiid
procedure in POST based call.
The POST BODY also needs to be supported to handle larger payloads in this situation as
query parameters has size limitations. Currently string based query parameters are
supported, but since they passed as is as strings on larger payloads the they will be
subject 4000 string length restriction.
It should be possible to read metadata of the procedure and convert the string objects to
respective objects before the query gets executed.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)