Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 8.12.11.6_4, 8.12.11.6_3
Affects Version/s: 8.12.8.6_3
Component/s: OData
Labels:
None

Steps to Reproduce:
Hide

With Salesforce

Build a VDB that has a table with a multi-column key

In Salesforce, import the table via the OData importer

Create a page in Salesforce that displays a few columns from that table

Clicking on the a row in the salesforce UI will give you a drill-down, which will create a new URI to $filter down specifically on your one record. It'll create a filter with all the columns of the primary key

Without Salesforce

Create a VDB

Create a URI that has a space right after $filter=
e.g. http://localhost:8080/odata4/VDB/Schema/Table?$filter=%20ColumnA%20eq%2077777
Show
With Salesforce Build a VDB that has a table with a multi-column key In Salesforce, import the table via the OData importer Create a page in Salesforce that displays a few columns from that table Clicking on the a row in the salesforce UI will give you a drill-down, which will create a new URI to $filter down specifically on your one record. It'll create a filter with all the columns of the primary key Without Salesforce Create a VDB Create a URI that has a space right after $filter= e.g. http://localhost:8080/odata4/VDB/Schema/Table?$filter=%20ColumnA%20eq%2077777
Git Pull Request:
https://github.com/teiid/teiid/pull/948
Bugzilla References:
https://bugzilla.redhat.com/show_bug.cgi?id=1451785, https://bugzilla.redhat.com/show_bug.cgi?id=1446180, https://bugzilla.redhat.com/show_bug.cgi?id=1446201

Description

I'm accessing my JDV table via OData4 through Salesforce's UI builder. The salesforce engine itself is creating the OData calls, and whenever a $filter is needed with multiple columns, it looks like salesforce pads the column name with a space in front and behind. That'll make the URL look like ...$filter=%20ColumnA%20eq%20123%20and%20ColumnB%20eq...

The first space right after the $filter= throws off the JDV engine as it thinks it's a malformed URL - which I guess it is. The thing is when I tested it via the OData2 interface, it accepted it just fine. I'm not sure if the OData4 specifications explicitly state in terms of the URL, so it could be anybody's bug. Perhaps we could make JDV a little more forgiving and trim the spaces after un-URL-encoding the URI.

Attachments

Activity

People

Assignee:: Johnathon Lee

Reporter:: Steve Tran

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Dates

Created:: 2017/04/19 8:30 AM

Updated:: 2021/10/25 4:14 PM

Resolved:: 2017/07/06 1:08 PM