[
https://issues.apache.org/jira/browse/OLINGO-904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15195465#comment-15195465
]
Christian Amend commented on OLINGO-904:
----------------------------------------
[~rareddy] I looked into this an found the following:
The 4.1.0 parser was very lenient with crossjoin. As far as I can tell it
didn`t even check that the content of the crossjoin are all EntitySets. The new
parser checks this and allows these EntitySets to be adressed in filter
expressions. This is also tested with this sample URL:
"$crossjoin(ESTwoPrim,ESMixPrimCollComp)?$filter=ESTwoPrim/PropertyString eq
ESMixPrimCollComp/PropertyComp/PropertyString"
For expand this is currently missing since there the logic is different. There
you can have the plain entity set name to indicate that the entity should be
part of the payload instead of a simple URL.
So since this is currently missing I will try to get it done before we make the
release at the end of the month.
> $crossjoin with $expand not being parsed correctly
> --------------------------------------------------
>
> Key: OLINGO-904
> URL: https://issues.apache.org/jira/browse/OLINGO-904
> Project: Olingo
> Issue Type: Bug
> Components: odata4-server
> Reporter: Ramesh Reddy
> Assignee: Christian Amend
> Fix For: (Java) V4 4.2.0
>
>
> With the new version of the parser the $crossjoin queries with $expand are
> not correctly being parsed. for ex
> http://host:port/svc/$crossjoin(x,y)?$expand=x
> This was working correctly in 4.1.0 version, the new parser introduced the
> regression.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
