[
https://issues.jboss.org/browse/TEIID-3931?page=com.atlassian.jira.plugin...
]
Steven Hawkins reassigned TEIID-3931:
-------------------------------------
Fix Version/s: 9.x
(was: 9.0)
Assignee: (was: Steven Hawkins)
This will be difficult to do as Teiid currently has a single geometry type value - olingo
needs to use a specific subtype instead. We can emulate this somewhat by using extension
metadata when creating the edm metadata - however all of the other logic paths are just
based upon passing the teiid type (and not the column) which would be required to
determine the proper odata type.
Add support for odata service geospatial handling
-------------------------------------------------
Key: TEIID-3931
URL:
https://issues.jboss.org/browse/TEIID-3931
Project: Teiid
Issue Type: Bug
Components: OData
Reporter: Steven Hawkins
Fix For: 9.x
We should use the Edm.Geometry type for the Teiid geometry type (we can also use system
metadata to see if it's appropriate to use a geometry subtype) along with any
geospatial operations that odata and Teiid support.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)