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.
> 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.
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
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.