[
https://issues.jboss.org/browse/TEIID-5694?page=com.atlassian.jira.plugin...
]
Steven Hawkins edited comment on TEIID-5694 at 3/21/19 9:04 AM:
----------------------------------------------------------------
Geo logic that is dependent upon other libraries is present in:
- engine
- runtime (pg geo support)
- olingo (geo support)
- mongodb
In particular the olingo support requires the mapping of the jts geometry object to the
corresponding olingo object, so I believe it would be best/simplest to just consider
jts-core as required, but make proj4j and wololo optional.
was (Author: shawkins):
Geo logic that is dependent upon other libraries is present in:
- engine
- runtime (pg geo support)
- olingo (geo support)
I believe it would be best/simplest to just consider jts-core as required, but make proj4j
and wololo optional.
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)