[JBoss JIRA] (TEIID-5054) autoFailover with a multi-batch result timing issue
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIID-5054?page=com.atlassian.jira.plugin... ]
Andrej Šmigala commented on TEIID-5054:
---------------------------------------
Hello [~shawkins], could you please provide more details on how to reproduce this issue? Thank you.
> autoFailover with a multi-batch result timing issue
> ---------------------------------------------------
>
> Key: TEIID-5054
> URL: https://issues.jboss.org/browse/TEIID-5054
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Driver
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Blocker
> Fix For: 10.0, 8.12.x-6.4, 9.2.6, 9.3.3
>
>
> With autoFailover=true there is a periodic ping before usage of the connection. This ping may be called during processing of multi-batch results such that the ping call effectively hangs. 4 minutes later (or whatever the synch timeout is) the client will attempt to failover.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 10 months
[JBoss JIRA] (TEIID-5225) Building embedded applications without JBoss Third Party repository is not possible
by Jan Stastny (JIRA)
[ https://issues.jboss.org/browse/TEIID-5225?page=com.atlassian.jira.plugin... ]
Jan Stastny reassigned TEIID-5225:
----------------------------------
Assignee: Jan Stastny (was: Ramesh Reddy)
> Building embedded applications without JBoss Third Party repository is not possible
> -----------------------------------------------------------------------------------
>
> Key: TEIID-5225
> URL: https://issues.jboss.org/browse/TEIID-5225
> Project: Teiid
> Issue Type: Bug
> Components: Build/Kits
> Affects Versions: 10.0
> Reporter: Ramesh Reddy
> Assignee: Jan Stastny
> Priority: Blocker
> Fix For: 10.1
>
>
> Building any Teiid applications like
> - Embedded Teiid based applications
> - WildFly Swarm based applications
> - Spring Boot based applications
> is not possible just using the Maven Central repository, one must include the JBoss Third Party repository to fetch "nux:nux:1.6" jar. This project seems to nowhere to found in maven central and not actively being managed. The alternative solution is to fork the code of this project and build deploy a maven artifact with "org.teiid:nux:1.6" coordinates into Maven Central and use this in Teiid build.
> Also, xerces:xercesImpl seems to be in similar situation, but a stable version of this library is now available in the Maven Central repository. Teiid build should be moved to this version.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 10 months
[JBoss JIRA] (TEIID-5225) Building embedded applications without JBoss Third Party repository is not possible
by Jan Stastny (JIRA)
[ https://issues.jboss.org/browse/TEIID-5225?page=com.atlassian.jira.plugin... ]
Jan Stastny reassigned TEIID-5225:
----------------------------------
Assignee: Ramesh Reddy (was: Jan Stastny)
> Building embedded applications without JBoss Third Party repository is not possible
> -----------------------------------------------------------------------------------
>
> Key: TEIID-5225
> URL: https://issues.jboss.org/browse/TEIID-5225
> Project: Teiid
> Issue Type: Bug
> Components: Build/Kits
> Affects Versions: 10.0
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Priority: Blocker
> Fix For: 10.1
>
>
> Building any Teiid applications like
> - Embedded Teiid based applications
> - WildFly Swarm based applications
> - Spring Boot based applications
> is not possible just using the Maven Central repository, one must include the JBoss Third Party repository to fetch "nux:nux:1.6" jar. This project seems to nowhere to found in maven central and not actively being managed. The alternative solution is to fork the code of this project and build deploy a maven artifact with "org.teiid:nux:1.6" coordinates into Maven Central and use this in Teiid build.
> Also, xerces:xercesImpl seems to be in similar situation, but a stable version of this library is now available in the Maven Central repository. Teiid build should be moved to this version.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 10 months
[JBoss JIRA] (TEIID-5236) Document and update GeoServer/PG JDBC compatibility
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5236?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5236:
---------------------------------------
2.12 geoserver also uses DatabaseMetaData.getPrimaryKeys - this uses _pg_expandarray and record/struct field accessors (i.keys).n. It doesn't seem to be required, but I'll access how much work there is in supporting it.
> Document and update GeoServer/PG JDBC compatibility
> ---------------------------------------------------
>
> Key: TEIID-5236
> URL: https://issues.jboss.org/browse/TEIID-5236
> Project: Teiid
> Issue Type: Quality Risk
> Components: Documentation, ODBC, Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.2
>
>
> It is not documented on the geoserver integration page, but most of the initial work was done against versions between 2.6 and 2.8. It appears that even 2.8 can have issues as it can use the 9.4 postgresql driver, which expects additional syntax support for type metadata.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 10 months
[JBoss JIRA] (TEIID-5236) Document and update GeoServer/PG JDBC compatibility
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5236?page=com.atlassian.jira.plugin... ]
Steven Hawkins edited comment on TEIID-5236 at 1/29/18 2:22 PM:
----------------------------------------------------------------
It appears that most of the issues were due to the driver itself -
in addition to the support mentioned in the previous comments, we were also affected by https://github.com/pgjdbc/pgjdbc/pull/745 which showed that we were putting the wrong string form of boolean values into results but the previous driver version was tolerant.
I've now successfully tested 2.8 and converted the Teiid source to test with the latest 42.1 driver. Still need to validate the latest geoserver release.
was (Author: shawkins):
It appears that most of the issues were due to the driver itself. I've now successfully tested 2.8 and converted the Teiid source to test with the latest 42.1 driver. Still need to validate the latest geoserver release.
> Document and update GeoServer/PG JDBC compatibility
> ---------------------------------------------------
>
> Key: TEIID-5236
> URL: https://issues.jboss.org/browse/TEIID-5236
> Project: Teiid
> Issue Type: Quality Risk
> Components: Documentation, ODBC, Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.2
>
>
> It is not documented on the geoserver integration page, but most of the initial work was done against versions between 2.6 and 2.8. It appears that even 2.8 can have issues as it can use the 9.4 postgresql driver, which expects additional syntax support for type metadata.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 10 months
[JBoss JIRA] (TEIID-5236) Document and update GeoServer/PG JDBC compatibility
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5236?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-5236:
----------------------------------
Summary: Document and update GeoServer/PG JDBC compatibility (was: Document and update GeoServer compatibility)
It appears that most of the issues were due to the driver itself. I've now successfully tested 2.8 and converted the Teiid source to test with the latest 42.1 driver. Still need to validate the latest geoserver release.
> Document and update GeoServer/PG JDBC compatibility
> ---------------------------------------------------
>
> Key: TEIID-5236
> URL: https://issues.jboss.org/browse/TEIID-5236
> Project: Teiid
> Issue Type: Quality Risk
> Components: Documentation, ODBC, Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.2
>
>
> It is not documented on the geoserver integration page, but most of the initial work was done against versions between 2.6 and 2.8. It appears that even 2.8 can have issues as it can use the 9.4 postgresql driver, which expects additional syntax support for type metadata.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 10 months
[JBoss JIRA] (TEIID-5236) Document and update GeoServer compatibility
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5236?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5236:
---------------------------------------
There are two statements issued from the PG JDBC TypeInfoCache that are problematic. One can be satisfied by implementing current_schemas. The other requires implementing:
generate_series table valued function
array_upper (similar to array_length for the first dimension)
natural join (with an explicit column list)
We'll also need to populate the typinput column from pg_type. It may be easier to just add a full override of the expected sql.
> Document and update GeoServer compatibility
> -------------------------------------------
>
> Key: TEIID-5236
> URL: https://issues.jboss.org/browse/TEIID-5236
> Project: Teiid
> Issue Type: Quality Risk
> Components: Documentation, ODBC, Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.2
>
>
> It is not documented on the geoserver integration page, but most of the initial work was done against versions between 2.6 and 2.8. It appears that even 2.8 can have issues as it can use the 9.4 postgresql driver, which expects additional syntax support for type metadata.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 11 months