How to access VDB using OData V4 (instead of V2)

[simon.evenepoel]

Dear

I am running teiid 8.12.3 and have a virtual database (VDB) configured which I try to access using OData V4 in the JSON format. Surfing to http://host/odata/vdb/view?$format=json yields a response, but an OData V2 response if I am not mistaken.

However, on these release notes: teiid: 8.11 Final Released, Support for OData V4 and SAP HANA I read the following:

"TEIID-2973 OData V4 Access your VDB using OData V4 protocol".

So I assumed that it would be possible. However I can't find any information on accomplishing what I need. Can you explain to me how I can address my data using the V4 version of the OData protocol instead of the V2 version ? Or can you point me to some reference documentation which I might have overlooked?

To clarify the distinction between what I have and what I need: The json being rendered by my local teiid instance looks like this: (V2 specification were each {...} represents an entity):

{
     "d" : {
         "results" : [ {...}, {...} , ... ]
     }
}

But our OData client expects the following json format (V4 specification) for a list of entities:

{
     "@odata.context": "...",
     "@odata.count": 37,
     "value": [{...}, {...}, ... ]
}

Kind regards and thanks in advance for your help

Simon

[rareddy]

try

http://host/odata4/vdb/schema/view?$format=json

I will write some notes here. https://docs.jboss.org/author/display/TEIID/OData+Support

Ramesh..

[simon.evenepoel]

Hi

Thx for your answer.

I am indeed getting further towards resolving my problem, however now I get a malformed URL exception when there is a TIMESTAMP as part of my primary key and it complains that:

<error>
     <code>500</code>
     <message>java.net.URISyntaxException: Illegal character in scheme name at index 10: probesview(metric='BITRATE',timing=2016-01-13 11:25:03.884,topologylocationid=8453)
     </message>
</error>

I assume that this follows from the fact that there is a space in the timestamp. This problem remains if I manually change the timestamp to 2016-01-13T10:25:03.884Z and specify the primary key in my URI: http://localhost:8080/odata4/myvdb/myvirtualmodel/probesview(metric='BITRATE',timing=2016-01-13T10:25:03.884Z,topologylocationid=8453)

Is this something I can avoid? Note that I am using Teiid 8.12.4 in the meantime.

Thx again

Simon

[shawkins]

> Is this something I can avoid? Note that I am using Teiid 8.12.4 in the meantime.

It looks like a composite key will only accept a string literal for the timestamp value.  So try putting your value in single quotes.  I need to dig a little more to see why Olingo won't directly accept the datatimeoffset literal value.

[shawkins]

Actually there is an issue with our handling of building the entity id to go into the response.  We are not properly encoding datatime values.  This will require an issue to fix.  Can you log one at Teiid - JBoss Issue Tracker

[simon.evenepoel]

Hi

Thanks for the information!

I created [TEIID-3914] Datetime values not properly encoded in OData4 entity identifiers - JBoss Issue Tracker per your request.

Kind regards

Simon

[shawkins]

Thanks Simon.  We'll try to get the fix in for 8.13 Final.  If not it will be in a later 8.13.x release.