[JBoss JIRA] (TEIID-3896) When error occurs in the materialization process, an ERROR should be logged instead of DEBUG
by Van Halbert (JIRA)
Van Halbert created TEIID-3896:
----------------------------------
Summary: When error occurs in the materialization process, an ERROR should be logged instead of DEBUG
Key: TEIID-3896
URL: https://issues.jboss.org/browse/TEIID-3896
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Affects Versions: 8.12.2
Reporter: Van Halbert
Assignee: Steven Hawkins
Priority: Minor
When trying to do materialization, there's an issue (DEBUG) appearing in the server.log:
09:58:51,272 DEBUG [org.teiid.PROCESSOR] (Worker5_QueryProcessorQueue302) org.teiid.jdbc.TeiidSQLException: TEIID30168 Couldn't execute the dynamic SQL command "EXECUTE IMMEDIATE ('SELECT count(*) as rowCount FROM ' || matViewTable) AS rowCount integer INTO #load_count" with the SQL statement "('SELECT count(*) as rowCount FROM ' || matViewTable)" due to: Group specified is ambiguous, resubmit the query by fully qualifying the group name: Stock
I believe this be logged as an ERROR as it appears to be detrimental to what's being materialized.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (TEIID-3895) OData - metadata returns primary key with attribute "Nullable=true"
by Juraj Duráni (JIRA)
Juraj Duráni created TEIID-3895:
-----------------------------------
Summary: OData - metadata returns primary key with attribute "Nullable=true"
Key: TEIID-3895
URL: https://issues.jboss.org/browse/TEIID-3895
Project: Teiid
Issue Type: Bug
Components: OData
Affects Versions: 8.12.3
Reporter: Juraj Duráni
Assignee: Juraj Duráni
If column's name in source (PHYSICAL) model has different name than one in the source (case sensitive) then attribute "Nullable" is set to true.
{code:xml}
<vdb name="test" version="1">
<model name="Source" type="PHYSICAL">
<source name="rs" connection-jndi-name="java:/Redshift" translator-name="postgresql"/>
<metadata type="DDL">
<![CDATA[create foreign table SmallB (
IntKey integer PRIMARY KEY OPTIONS(NAMEINSOURCE 'intkey', NATIVE_TYPE 'int4')) OPTIONS(NAMEINSOURCE 'smalla');
]]>
</metadata>
</model>
</vdb>
{code}
result:
{code:xml}
<edmx:Edmx xmlns:edmx="http://schemas.microsoft.com/ado/2007/06/edmx" Version="1.0">
<edmx:DataServices xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata" m:DataServiceVersion="2.0">
<Schema xmlns="http://schemas.microsoft.com/ado/2008/09/edm" Namespace="Source">
<EntityType Name="SmallB">
<Key>
<PropertyRef Name="IntKey"/>
</Key>
<Property Name="IntKey" Type="Edm.Int32" Nullable="true"/>
</EntityType>
<EntityContainer Name="Source" m:IsDefaultEntityContainer="false">
<EntitySet Name="SmallB" EntityType="Source.SmallB"/>
</EntityContainer>
</Schema>
...
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (TEIID-3893) Handling of binary odbc parameters needs improved
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3893?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3893:
----------------------------------
Summary: Handling of binary odbc parameters needs improved (was: Handling of binary odbc parameters needs improvded)
> Handling of binary odbc parameters needs improved
> -------------------------------------------------
>
> Key: TEIID-3893
> URL: https://issues.jboss.org/browse/TEIID-3893
> Project: Teiid
> Issue Type: Quality Risk
> Components: ODBC
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.13, 8.12.4
>
>
> parameters sent in binary format are just treated as byte arrays. We should us the oids sent with prepare to convert into the expected values. Clients such as postgresql JDBC 9.2+ expect this handling unless configured to not use binary values.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (TEIID-3893) Handling of binary odbc parameters needs improvded
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3893?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3893.
-----------------------------------
Resolution: Partially Completed
We now have handling for binary numeric types, but not for date/time, arrays, etc. Those have more involved handling that will require additional code to be taken from the pg client or elsewhere. The best solution is to have the client disable binary parameters when possible, for example with the jdbc client use binaryTransfer=false as a connection parameter - https://wiki.postgresql.org/wiki/JDBC-BinaryTransfer
> Handling of binary odbc parameters needs improvded
> --------------------------------------------------
>
> Key: TEIID-3893
> URL: https://issues.jboss.org/browse/TEIID-3893
> Project: Teiid
> Issue Type: Quality Risk
> Components: ODBC
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.13, 8.12.4
>
>
> parameters sent in binary format are just treated as byte arrays. We should us the oids sent with prepare to convert into the expected values. Clients such as postgresql JDBC 9.2+ expect this handling unless configured to not use binary values.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (TEIID-3894) Teiid transport ssl attributes should add some default values
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-3894?page=com.atlassian.jira.plugin... ]
Kylin Soong updated TEIID-3894:
-------------------------------
Description:
Execute the following cli
{code}
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-mode,value=enabled)
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-authentication-mode,value=1-way)
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-ssl-protocol,value=TLSv1)
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-keymanagement-algorithm,value=SunX509)
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-enabled-cipher-suites,value="SSL_RSA_WITH_RC4_128_MD5,SSL_RSA_WITH_RC4_128_SHA")
/subsystem=teiid/transport=jdbc:write-attribute(name=keystore-type,value=JKS)
{code}
no suggested value pop up, some values only allow existed value, so I think add some default value is necessary.
h3. ssl-mode allowed value
* enabled
* login
* enabled
h3. ssl-authentication-mode allowed value
* 1-way
* 2-way
* anonymous
h3. ssl-ssl-protocol default value
* TLSv1
h3. ssl-keymanagement-algorithm default value
* SunX509
h3. ssl-enabled-cipher-suites default value
* SSL_RSA_WITH_RC4_128_MD5,SSL_RSA_WITH_RC4_128_SHA
h3. keystore-type default value
* JKS
was:
Execute the following cli
{code}
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-mode,value=enabled)
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-authentication-mode,value=1-way)
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-ssl-protocol,value=TLSv1)
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-keymanagement-algorithm,value=SunX509)
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-enabled-cipher-suites,value="SSL_RSA_WITH_RC4_128_MD5,SSL_RSA_WITH_RC4_128_SHA")
/subsystem=teiid/transport=jdbc:write-attribute(name=keystore-type,value=JKS)
{code}
no suggested value pop up, some values only allow existed value, so I think add some default value is necessary.
h3. ssl-mode allowed value
* enabled
* login
* enabled
h3. ssl-authentication-mode allowed value
* 1-way
* 2-way
* anonymous
h3. ssl-ssl-protocol default value
* TLSv1
h3. ssl-keymanagement-algorithm default value
* SunX509
h3. ssl-enabled-cipher-suites default value
* SSL_RSA_WITH_RC4_128_MD5,SSL_RSA_WITH_RC4_128_SHA
h3. keystore-type default value
* JKS
> Teiid transport ssl attributes should add some default values
> -------------------------------------------------------------
>
> Key: TEIID-3894
> URL: https://issues.jboss.org/browse/TEIID-3894
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 9.x
> Reporter: Kylin Soong
> Assignee: Steven Hawkins
> Fix For: 9.x
>
>
> Execute the following cli
> {code}
> /subsystem=teiid/transport=jdbc:write-attribute(name=ssl-mode,value=enabled)
> /subsystem=teiid/transport=jdbc:write-attribute(name=ssl-authentication-mode,value=1-way)
> /subsystem=teiid/transport=jdbc:write-attribute(name=ssl-ssl-protocol,value=TLSv1)
> /subsystem=teiid/transport=jdbc:write-attribute(name=ssl-keymanagement-algorithm,value=SunX509)
> /subsystem=teiid/transport=jdbc:write-attribute(name=ssl-enabled-cipher-suites,value="SSL_RSA_WITH_RC4_128_MD5,SSL_RSA_WITH_RC4_128_SHA")
> /subsystem=teiid/transport=jdbc:write-attribute(name=keystore-type,value=JKS)
> {code}
> no suggested value pop up, some values only allow existed value, so I think add some default value is necessary.
> h3. ssl-mode allowed value
> * enabled
> * login
> * enabled
> h3. ssl-authentication-mode allowed value
> * 1-way
> * 2-way
> * anonymous
> h3. ssl-ssl-protocol default value
> * TLSv1
> h3. ssl-keymanagement-algorithm default value
> * SunX509
> h3. ssl-enabled-cipher-suites default value
> * SSL_RSA_WITH_RC4_128_MD5,SSL_RSA_WITH_RC4_128_SHA
> h3. keystore-type default value
> * JKS
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (TEIID-3894) Teiid transport ssl attributes should add some default values
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-3894?page=com.atlassian.jira.plugin... ]
Kylin Soong updated TEIID-3894:
-------------------------------
Description:
Execute the following cli
{code}
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-mode,value=enabled)
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-authentication-mode,value=1-way)
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-ssl-protocol,value=TLSv1)
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-keymanagement-algorithm,value=SunX509)
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-enabled-cipher-suites,value="SSL_RSA_WITH_RC4_128_MD5,SSL_RSA_WITH_RC4_128_SHA")
/subsystem=teiid/transport=jdbc:write-attribute(name=keystore-type,value=JKS)
{code}
no suggested value pop up, some values only allow existed value, so I think add some default value is necessary.
h3. ssl-mode allowed value
* enabled
* login
* enabled
h3. ssl-authentication-mode allowed value
* 1-way
* 2-way
* anonymous
h3. ssl-ssl-protocol default value
* TLSv1
h3. ssl-keymanagement-algorithm default value
* SunX509
h3. ssl-enabled-cipher-suites default value
* SSL_RSA_WITH_RC4_128_MD5,SSL_RSA_WITH_RC4_128_SHA
h3. keystore-type default value
* JKS
was:
Execute the following cli
{code}
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-mode,value=enabled)
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-authentication-mode,value=1-way)
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-ssl-protocol,value=TLSv1)
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-keymanagement-algorithm,value=SunX509)
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-enabled-cipher-suites,value="SSL_RSA_WITH_RC4_128_MD5,SSL_RSA_WITH_RC4_128_SHA")
/subsystem=teiid/transport=jdbc:write-attribute(name=keystore-type,value=JKS)
{code}
no suggested value pop up, some values only allow existed value, so I think add some default value is necessary.
### ssl-mode allowed value
* enabled
* login
* enabled
### ssl-authentication-mode allowed value
* 1-way
* 2-way
* anonymous
> Teiid transport ssl attributes should add some default values
> -------------------------------------------------------------
>
> Key: TEIID-3894
> URL: https://issues.jboss.org/browse/TEIID-3894
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 9.x
> Reporter: Kylin Soong
> Assignee: Steven Hawkins
> Fix For: 9.x
>
>
> Execute the following cli
> {code}
> /subsystem=teiid/transport=jdbc:write-attribute(name=ssl-mode,value=enabled)
> /subsystem=teiid/transport=jdbc:write-attribute(name=ssl-authentication-mode,value=1-way)
> /subsystem=teiid/transport=jdbc:write-attribute(name=ssl-ssl-protocol,value=TLSv1)
> /subsystem=teiid/transport=jdbc:write-attribute(name=ssl-keymanagement-algorithm,value=SunX509)
> /subsystem=teiid/transport=jdbc:write-attribute(name=ssl-enabled-cipher-suites,value="SSL_RSA_WITH_RC4_128_MD5,SSL_RSA_WITH_RC4_128_SHA")
> /subsystem=teiid/transport=jdbc:write-attribute(name=keystore-type,value=JKS)
> {code}
> no suggested value pop up, some values only allow existed value, so I think add some default value is necessary.
> h3. ssl-mode allowed value
> * enabled
> * login
> * enabled
> h3. ssl-authentication-mode allowed value
> * 1-way
> * 2-way
> * anonymous
> h3. ssl-ssl-protocol default value
> * TLSv1
> h3. ssl-keymanagement-algorithm default value
> * SunX509
> h3. ssl-enabled-cipher-suites default value
> * SSL_RSA_WITH_RC4_128_MD5,SSL_RSA_WITH_RC4_128_SHA
> h3. keystore-type default value
> * JKS
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (TEIID-3894) Teiid transport ssl attributes should add some default values
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-3894?page=com.atlassian.jira.plugin... ]
Kylin Soong updated TEIID-3894:
-------------------------------
Description:
Execute the following cli
{code}
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-mode,value=enabled)
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-authentication-mode,value=1-way)
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-ssl-protocol,value=TLSv1)
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-keymanagement-algorithm,value=SunX509)
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-enabled-cipher-suites,value="SSL_RSA_WITH_RC4_128_MD5,SSL_RSA_WITH_RC4_128_SHA")
/subsystem=teiid/transport=jdbc:write-attribute(name=keystore-type,value=JKS)
{code}
no suggested value pop up, some values only allow existed value, so I think add some default value is necessary.
### ssl-mode allowed value
* enabled
* login
* enabled
### ssl-authentication-mode allowed value
* 1-way
* 2-way
* anonymous
was:
Execute the following cli
{code}
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-mode,value=enabled)
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-authentication-mode,value=1-way)
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-ssl-protocol,value=TLSv1)
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-keymanagement-algorithm,value=SunX509)
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-enabled-cipher-suites,value="SSL_RSA_WITH_RC4_128_MD5,SSL_RSA_WITH_RC4_128_SHA")
/subsystem=teiid/transport=jdbc:write-attribute(name=keystore-type,value=JKS)
{code}
no suggested value pop up, some values only allow existed value, so I think add some default value is necessary.
h4 ssl-mode allowed value
* enabled
* login
* enabled
h4 ssl-authentication-mode allowed value
* 1-way
* 2-way
* anonymous
> Teiid transport ssl attributes should add some default values
> -------------------------------------------------------------
>
> Key: TEIID-3894
> URL: https://issues.jboss.org/browse/TEIID-3894
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 9.x
> Reporter: Kylin Soong
> Assignee: Steven Hawkins
> Fix For: 9.x
>
>
> Execute the following cli
> {code}
> /subsystem=teiid/transport=jdbc:write-attribute(name=ssl-mode,value=enabled)
> /subsystem=teiid/transport=jdbc:write-attribute(name=ssl-authentication-mode,value=1-way)
> /subsystem=teiid/transport=jdbc:write-attribute(name=ssl-ssl-protocol,value=TLSv1)
> /subsystem=teiid/transport=jdbc:write-attribute(name=ssl-keymanagement-algorithm,value=SunX509)
> /subsystem=teiid/transport=jdbc:write-attribute(name=ssl-enabled-cipher-suites,value="SSL_RSA_WITH_RC4_128_MD5,SSL_RSA_WITH_RC4_128_SHA")
> /subsystem=teiid/transport=jdbc:write-attribute(name=keystore-type,value=JKS)
> {code}
> no suggested value pop up, some values only allow existed value, so I think add some default value is necessary.
> ### ssl-mode allowed value
> * enabled
> * login
> * enabled
> ### ssl-authentication-mode allowed value
> * 1-way
> * 2-way
> * anonymous
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (TEIID-3894) Teiid transport ssl attributes should add some default values
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-3894?page=com.atlassian.jira.plugin... ]
Kylin Soong updated TEIID-3894:
-------------------------------
Description:
Execute the following cli
{code}
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-mode,value=enabled)
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-authentication-mode,value=1-way)
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-ssl-protocol,value=TLSv1)
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-keymanagement-algorithm,value=SunX509)
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-enabled-cipher-suites,value="SSL_RSA_WITH_RC4_128_MD5,SSL_RSA_WITH_RC4_128_SHA")
/subsystem=teiid/transport=jdbc:write-attribute(name=keystore-type,value=JKS)
{code}
no suggested value pop up, some values only allow existed value, so I think add some default value is necessary.
h4 ssl-mode allowed value
* enabled
* login
* enabled
h4 ssl-authentication-mode allowed value
* 1-way
* 2-way
* anonymous
was:
Execute the following cli
{code}
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-mode,value=enabled)
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-authentication-mode,value=1-way)
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-ssl-protocol,value=TLSv1)
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-keymanagement-algorithm,value=SunX509)
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-enabled-cipher-suites,value="SSL_RSA_WITH_RC4_128_MD5,SSL_RSA_WITH_RC4_128_SHA")
/subsystem=teiid/transport=jdbc:write-attribute(name=keystore-type,value=JKS)
{code}
no suggested value pop up, some values only allow existed value, so I think add some default value is necessary.
> Teiid transport ssl attributes should add some default values
> -------------------------------------------------------------
>
> Key: TEIID-3894
> URL: https://issues.jboss.org/browse/TEIID-3894
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 9.x
> Reporter: Kylin Soong
> Assignee: Steven Hawkins
> Fix For: 9.x
>
>
> Execute the following cli
> {code}
> /subsystem=teiid/transport=jdbc:write-attribute(name=ssl-mode,value=enabled)
> /subsystem=teiid/transport=jdbc:write-attribute(name=ssl-authentication-mode,value=1-way)
> /subsystem=teiid/transport=jdbc:write-attribute(name=ssl-ssl-protocol,value=TLSv1)
> /subsystem=teiid/transport=jdbc:write-attribute(name=ssl-keymanagement-algorithm,value=SunX509)
> /subsystem=teiid/transport=jdbc:write-attribute(name=ssl-enabled-cipher-suites,value="SSL_RSA_WITH_RC4_128_MD5,SSL_RSA_WITH_RC4_128_SHA")
> /subsystem=teiid/transport=jdbc:write-attribute(name=keystore-type,value=JKS)
> {code}
> no suggested value pop up, some values only allow existed value, so I think add some default value is necessary.
> h4 ssl-mode allowed value
> * enabled
> * login
> * enabled
> h4 ssl-authentication-mode allowed value
> * 1-way
> * 2-way
> * anonymous
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (TEIID-3894) Teiid transport ssl attributes should add some default values
by Kylin Soong (JIRA)
Kylin Soong created TEIID-3894:
----------------------------------
Summary: Teiid transport ssl attributes should add some default values
Key: TEIID-3894
URL: https://issues.jboss.org/browse/TEIID-3894
Project: Teiid
Issue Type: Feature Request
Components: Server
Affects Versions: 9.x
Reporter: Kylin Soong
Assignee: Steven Hawkins
Fix For: 9.x
Execute the following cli
{code}
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-mode,value=enabled)
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-authentication-mode,value=1-way)
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-ssl-protocol,value=TLSv1)
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-keymanagement-algorithm,value=SunX509)
/subsystem=teiid/transport=jdbc:write-attribute(name=ssl-enabled-cipher-suites,value="SSL_RSA_WITH_RC4_128_MD5,SSL_RSA_WITH_RC4_128_SHA")
/subsystem=teiid/transport=jdbc:write-attribute(name=keystore-type,value=JKS)
{code}
no suggested value pop up, some values only allow existed value, so I think add some default value is necessary.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (TEIID-3869) Enable Teiid to be exposed as a GIS compliant data source
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3869?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3869:
---------------------------------------
Based upon a discussion of Friday this issue will become specifically enabling support for geoserver targeting teiid odbc via their postgis configuration. It will likely be added first to 9.0 and then back ported. This entails several minor odbc issues, as well as support for ~10 scalar functions (one of requires a parsing change), an aggregate function, push down support, and a function alias.
The restrictions of this include:
- no support for curved geometry types (CIRCULARSTRING, CIRCULARSTRING, MULTICURVE, COMPOUNDCURVE)
- no Teiid support for ST_Estimated_Extent (but that seems to be ok as geoserver will workaround that, and we can also provide postgis pushdown support)
- no 3d support
- no geography support
- no Teiid spatial index support
A broader amount of support, to provide full opengis / sql/mm with spatial indexes etc., is likely too much to commit to.
> Enable Teiid to be exposed as a GIS compliant data source
> ---------------------------------------------------------
>
> Key: TEIID-3869
> URL: https://issues.jboss.org/browse/TEIID-3869
> Project: Teiid
> Issue Type: Feature Request
> Components: JDBC Driver, OData, ODBC
> Reporter: Van Halbert
> Assignee: Steven Hawkins
>
> See
> http://www.esri.com/~/media/Files/Pdfs/library/whitepapers/pdfs/supported...
> WMS - http://www.opengeospatial.org/standards/wms
> WFS - http://www.opengeospatial.org/standards/wfs
> Using MapViewer to show maps based on WMS services. The WMS services are provided by a GeoServer like ArcGIS or GeoServer.
> OData has also some capabilities in the Geo space especially on the .Net libraries side.
> See http://www.odata.org/libraries/ for Microsoft.Spatial (OData v4) and System.Spatial (OData v1-3)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months