Description of problem: Teiid does not process header *OData-Isolation: snapshot* defined in request correctly. * if service (Teiid) does not support this option it must return error 412 * if Teiid does supports this option then it is not processed correctly, because modifications made during request are visbile See http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part1-protocol/odata-v4.0-errata02-os-part1-protocol-complete.html#_Toc406398231 Steps to Reproduce: 1. Request [1] 2. Request [2] 3. Data modification via JDBC 4. Request [2] Data returned from steps 2. and 4. are different. [1] Jsoup.connect("http://localhost:8080/odata4/Redshift/Source/SmallA/?$select=IntKey") .header("Authorization", "Basic "+ Base64.encodeBytes(("user:user").getBytes())) .header("OData-MaxVersion", "4.0") .header("Accept", "application/xml") .header("OData-Isolation", "snapshot") .header("Prefer", "odata.maxpagesize=10") [2] Jsoup.connect("http://localhost:8080/odata4/Redshift/Source/SmallA/?$select=IntKey&$skiptoken=+koj1e+zqsMU--10") .header("Authorization", "Basic "+ Base64.encodeBytes(("user:user").getBytes())) .header("OData-MaxVersion", "4.0") .header("Accept", "application/xml") .header("Prefer", "odata.maxpagesize=10")
Per engineers, deferring till Teiid supports 4.2 Olingo.
Ramesh Reddy <rareddy> updated the status of jira TEIID-3906 to Coding In Progress
Ramesh Reddy <rareddy> updated the status of jira TEIID-3906 to Resolved
Due to the issues found with OData, this issue will now be fixed because Teiid will be upgrading Olingo.
Steven Hawkins <shawkins> updated the status of jira TEIID-3906 to Closed