[
https://issues.jboss.org/browse/TEIID-5694?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-5694:
---------------------------------------
[~rareddy] See the pull request
https://github.com/teiid/teiid/pull/1139
With the optional-geo removed the following will occur - and handled gracefully:
- no ST_ASGEOJSON, ST_GEOMFROMGEOJSON, nor ST_TRANSFORM functions
- geography values may not be valid/normalized
- to gml without srid may fail
- mongodb usage of geojson will fail
As described above the isolation of jts-core would be even more work. To be done properly
it would even take another module to isolate the interdependence with olingo.
Create a sub-module for geo functions
-------------------------------------
Key: TEIID-5694
URL:
https://issues.jboss.org/browse/TEIID-5694
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Major
Fix For: 12.2
When not including the geo functionality we should see an warning, but not fail to start.
The current logic will fail to start by looking directly at geometryutils to load the
st_extent aggregate. It will also not fail to load the other function methods as
Geo*FunctionMethods is isolated from the missing dependencies.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)