[
https://issues.jboss.org/browse/TEIID-3329?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3329:
---------------------------------------
For the most part we would just want to promote the use of the ST_ functions over the
oracle function forms, and don't see any consolidation what we want to do at this
time.
For the mongodb logic we have something like:
mongo.geoWithin(CategoryName, 'Polygon', ((cast(1.0 as double), cast(2.0 as
double)),(cast(3.0 as double), cast(4.0 as double))))
This could have just a geometry argument, which the translator would then convert to
geojson (although I'm not sure how that would mesh with the BasicDBObjectBuilder
logic) for example:
mongo.geoWithin(CategoryName,
ST_GeomFromGeoJSON('{"coordinates":[[1,2],[3,4]],"type":"Polygon"}'))
Rationalize older spatial support with the new
----------------------------------------------
Key: TEIID-3329
URL:
https://issues.jboss.org/browse/TEIID-3329
Project: Teiid
Issue Type: Quality Risk
Components: Misc. Connectors
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.12
MongoDB and Oracle had existing spatial support that should be updated to account for the
new support if possible.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)