]
Ramesh Reddy commented on TEIID-3968:
-------------------------------------
The above upstream JIRAs are fixed in 4.2.0 version. I am going to make this a sub-ask of
TEIID-3932
OData 4 array type handling
---------------------------
Key: TEIID-3968
URL:
https://issues.jboss.org/browse/TEIID-3968
Project: Teiid
Issue Type: Bug
Components: OData
Reporter: Steven Hawkins
Assignee: Steven Hawkins
To ensure we are appropriate returning the correct error messages, creating the right
upstream changes, etc. we have several paths to validate wrt array handling. There are:
In the translator - ODataProcedureExecution.getQueryParameters,
ODataFilterVisitor.visit(Function) and ODataFilterVisitor.visit(ColumnReference),
ODataExpressionToSQLVisitor.visitAlias, ODataUpdateVisitor.visit(Update)
In the OData service - ODataExpressionToSQLVisitor.visit(Alias)
From the spec it appears that a uri should be able to specify arrays, but olingo and
other frameworks may have limitations. For example it should be possible to have an array
argument to a function, but the olingo framework will complain that arrays are not allowed
in the resource part of the uri.
At the very least we'll capture what won't work with this issue.