Bug 1316476 - OData ignores entities with empty list of related entities if $filter is applied to expanded entities
Summary: OData ignores entities with empty list of related entities if $filter is appl...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Teiid
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ER4
: 6.3.0
Assignee: Van Halbert
QA Contact: Juraj Duráni
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-10 10:59 UTC by Juraj Duráni
Modified: 2016-08-24 11:45 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-24 11:45:30 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker TEIID-4044 0 Major Closed OData ignores entities with empty list of related entities if $filter is applied to expanded entities 2016-06-15 12:36:21 UTC

Description Juraj Duráni 2016-03-10 10:59:03 UTC 
Description of problem:
If user want to apply filter for related entities, OData service should return all entities, not only those with non-empty collection of related entities.

*Example:*
*URL:* http://localhost:8080/odata4/olingo_basic/Source/Customers/?$expand=Orders_FK0($filter=place%20eq%20%27town%27)
*Result:* OData returns only 2 customers (both have at least one order with place "town")
*Expectation:* OData should return all 4 customers (two of them should have empty list of orders)
Comment 1 JBoss JIRA Server 2016-03-18 16:01:12 UTC 
Ramesh Reddy <rareddy> updated the status of jira TEIID-4044 to Resolved
Comment 2 Van Halbert 2016-03-18 18:19:58 UTC 
Duplicate of TEIID-4064

*** This bug has been marked as a duplicate of bug 1316511 ***
Comment 3 JBoss JIRA Server 2016-05-20 13:26:41 UTC 
Juraj Duráni <jdurani> updated the status of jira TEIID-4044 to Reopened
Comment 4 Juraj Duráni 2016-05-20 13:27:53 UTC 
I have reopened TEIID-4044. This is not resolved in ER3. Note that TEIID-4064 is resolved, but this one not. So I expected this to be no more duplicate of TEIID-4064.
Comment 5 JBoss JIRA Server 2016-05-20 13:41:23 UTC 
Juraj Duráni <jdurani> updated the status of jira TEIID-4044 to Closed
Comment 6 JBoss JIRA Server 2016-05-20 13:46:46 UTC 
Juraj Duráni <jdurani> updated the status of jira TEIID-4044 to Reopened
Comment 7 JBoss JIRA Server 2016-05-24 11:35:29 UTC 
Ramesh Reddy <rareddy> updated the status of jira TEIID-4044 to Resolved
Comment 8 JBoss JIRA Server 2016-06-15 12:36:21 UTC 
Steven Hawkins <shawkins> updated the status of jira TEIID-4044 to Closed
Note You need to log in before you can comment on or make changes to this bug.