[JBoss JIRA] (TEIID-5434) count(*) returns different nr of rows compared to normal select
by Bram Gadeyne (JIRA)
[ https://issues.jboss.org/browse/TEIID-5434?page=com.atlassian.jira.plugin... ]
Bram Gadeyne updated TEIID-5434:
--------------------------------
Attachment: count_plan.txt
select_plan.txt
> count(*) returns different nr of rows compared to normal select
> ---------------------------------------------------------------
>
> Key: TEIID-5434
> URL: https://issues.jboss.org/browse/TEIID-5434
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 10.3.3
> Reporter: Bram Gadeyne
> Assignee: Steven Hawkins
> Priority: Critical
> Attachments: count_plan.txt, select_plan.txt
>
>
> Normal select return 162175 rows:
> {code:sql}
> select pa.ICUSessionID,11074, obr.DateTime, obr.varvalue, true, 15001866
> from tv_retrieve_observrec obr
> join kd_matric.ExtrPatICUAdmissions epa on epa.PatientID = obr.admissionid
> join kd_matric.PatICUAdmissions pa on pa.ICUSessionID = epa.ICUSessionID and pa.BatchID < 1152
> where obr.VariableID = 15001866;
> {code}
> count query return a count of 11573
> {code:sql}
> select count(*)
> from tv_retrieve_observrec obr
> join kd_matric.ExtrPatICUAdmissions epa on epa.PatientID = obr.admissionid
> join kd_matric.PatICUAdmissions pa on pa.ICUSessionID = epa.ICUSessionID and pa.BatchID < 1152
> where obr.VariableID = 15001866;
> {code}
> This was detected on a snapshot release of 10.3.3
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (TEIID-5434) count(*) returns different nr of rows compared to normal select
by Bram Gadeyne (JIRA)
Bram Gadeyne created TEIID-5434:
-----------------------------------
Summary: count(*) returns different nr of rows compared to normal select
Key: TEIID-5434
URL: https://issues.jboss.org/browse/TEIID-5434
Project: Teiid
Issue Type: Bug
Affects Versions: 10.3.3
Reporter: Bram Gadeyne
Assignee: Steven Hawkins
Priority: Critical
Attachments: count_plan.txt, select_plan.txt
Normal select return 162175 rows:
{code:sql}
select pa.ICUSessionID,11074, obr.DateTime, obr.varvalue, true, 15001866
from tv_retrieve_observrec obr
join kd_matric.ExtrPatICUAdmissions epa on epa.PatientID = obr.admissionid
join kd_matric.PatICUAdmissions pa on pa.ICUSessionID = epa.ICUSessionID and pa.BatchID < 1152
where obr.VariableID = 15001866;
{code}
count query return a count of 11573
{code:sql}
select count(*)
from tv_retrieve_observrec obr
join kd_matric.ExtrPatICUAdmissions epa on epa.PatientID = obr.admissionid
join kd_matric.PatICUAdmissions pa on pa.ICUSessionID = epa.ICUSessionID and pa.BatchID < 1152
where obr.VariableID = 15001866;
{code}
This was detected on a snapshot release of 10.3.3
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (TEIID-5405) Change default vdb version behavior for Odata/Odata4 to use Connection type like JDBC Connections
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5405?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5405.
-----------------------------------
Resolution: Done
There isn't a good way to control this per vdb, so instead it's not an option of the odata services.
I've added explicit-vdb-version as an init param that can be overridden via the odata4 web.xml. If needed I can also add the ability to set this from a system property as well.
> Change default vdb version behavior for Odata/Odata4 to use Connection type like JDBC Connections
> -------------------------------------------------------------------------------------------------
>
> Key: TEIID-5405
> URL: https://issues.jboss.org/browse/TEIID-5405
> Project: Teiid
> Issue Type: Feature Request
> Components: OData
> Affects Versions: 8.12.13.6_4
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
> Fix For: 11.1
>
>
> With JDBC/ODBC Connections having the Connection type set to BY_VERSION for all versions of a VDB and not specifying the version in the URL it connects to the earliest version (as it should) and setting the Connection type to ANY for the latest version of the VDB it connects to that version by default if none is specified in the URL (this is also the correct behavior) but connecting via OData/OData4 it will always connect to version 1 if the version is not specified in the URL even if the latest VDB version has Connection type of ANY and all others are set to BY_VERSION. Can the OData connection behavior be the same as JDBC/ODBC?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (TEIID-5405) Change default vdb version behavior for Odata/Odata4 to use Connection type like JDBC Connections
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5405?page=com.atlassian.jira.plugin... ]
Work on TEIID-5405 started by Steven Hawkins.
---------------------------------------------
> Change default vdb version behavior for Odata/Odata4 to use Connection type like JDBC Connections
> -------------------------------------------------------------------------------------------------
>
> Key: TEIID-5405
> URL: https://issues.jboss.org/browse/TEIID-5405
> Project: Teiid
> Issue Type: Feature Request
> Components: OData
> Affects Versions: 8.12.13.6_4
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
> Fix For: 11.1
>
>
> With JDBC/ODBC Connections having the Connection type set to BY_VERSION for all versions of a VDB and not specifying the version in the URL it connects to the earliest version (as it should) and setting the Connection type to ANY for the latest version of the VDB it connects to that version by default if none is specified in the URL (this is also the correct behavior) but connecting via OData/OData4 it will always connect to version 1 if the version is not specified in the URL even if the latest VDB version has Connection type of ANY and all others are set to BY_VERSION. Can the OData connection behavior be the same as JDBC/ODBC?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (TEIID-5363) SimpleDB connector not quoting table names in internal Select queries
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5363?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-5363:
----------------------------------
Fix Version/s: 10.3.4
11.1
11.0.1
(was: 11.0)
(was: 10.3.2)
Based upon the feedback, the original fix made an invalid assumption about how the translator utilized the name in source. Thus there is a regression that is part of 10.3.2/10.3.3/11.0 when using the simpledb translator with native metadata. The workaround is the specify the ddl without the quoting in the nameinsource. I proactively put the new fix in 11.0.1 as well prior to release.
> SimpleDB connector not quoting table names in internal Select queries
> ---------------------------------------------------------------------
>
> Key: TEIID-5363
> URL: https://issues.jboss.org/browse/TEIID-5363
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Reporter: Pranav K
> Assignee: Steven Hawkins
> Fix For: 11.1, 11.0.1, 10.3.4
>
>
> Facing an issue while querying the Simple DB connector for a specific type of tables - the tables that contain a hyphen in the name.
> According to the SimpleDB documentation:
> Attribute and domain names may appear without quotes if they contain only letters, numbers, underscores (_), or dollar symbols ($) and do not start with a number. You must quote all other attribute and domain names with the backtick (`).
> (https://docs.aws.amazon.com/AmazonSimpleDB/latest/DeveloperGuide/QuotingR...)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (TEIID-5431) Function postgis_full_version() does not exist; Transaction Fails
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5431?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5431.
-----------------------------------
Fix Version/s: 11.1
11.0.1
10.3.3
Resolution: Done
Switched to looking for the function in the catalog first.
> Function postgis_full_version() does not exist; Transaction Fails
> -----------------------------------------------------------------
>
> Key: TEIID-5431
> URL: https://issues.jboss.org/browse/TEIID-5431
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 11.0
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Fix For: 11.1, 11.0.1, 10.3.3
>
>
> Within a XA transaction, when Teiid tries to do "initCapabilities" on Postgresql JDBC connector, it issues a function call "select postgis_full_version()" to detect the postgis version. However, if the postgis is not installed, then this fails.
> The undesired side effect is, the query already started a transaction then the whole transaction is rolled back.
> {code}
> Caused by: org.postgresql.util.PSQLException: ERROR: function postgis_full_version() does not exist
> Hint: No function matches the given name and argument types. You might need to add explicit type casts.
> Position: 8
> at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2455) ~[postgresql-9.4.1212.jre7.jar!/:9.4.1212.jre7]
> at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2155) ~[postgresql-9.4.1212.jre7.jar!/:9.4.1212.jre7]
> at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:288) ~[postgresql-9.4.1212.jre7.jar!/:9.4.1212.jre7]
> at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:430) ~[postgresql-9.4.1212.jre7.jar!/:9.4.1212.jre7]
> at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:356) ~[postgresql-9.4.1212.jre7.jar!/:9.4.1212.jre7]
> at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:303) ~[postgresql-9.4.1212.jre7.jar!/:9.4.1212.jre7]
> at org.postgresql.jdbc.PgStatement.executeCachedSql(PgStatement.java:289) ~[postgresql-9.4.1212.jre7.jar!/:9.4.1212.jre7]
> at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:266) ~[postgresql-9.4.1212.jre7.jar!/:9.4.1212.jre7]
> at org.postgresql.jdbc.PgStatement.executeQuery(PgStatement.java:233) ~[postgresql-9.4.1212.jre7.jar!/:9.4.1212.jre7]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_161]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_161]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_161]
> at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_161]
> at org.postgresql.ds.PGPooledConnection$StatementHandler.invoke(PGPooledConnection.java:423) ~[postgresql-9.4.1212.jre7.jar!/:9.4.1212.jre7]
> at com.sun.proxy.$Proxy90.executeQuery(Unknown Source) ~[na:na]
> at org.teiid.translator.jdbc.postgresql.PostgreSQLExecutionFactory.initCapabilities(PostgreSQLExecutionFactory.java:324) ~[translator-jdbc-11.1.0-SNAPSHOT.jar!/:11.1.0-SNAPSHOT]
> at org.teiid.translator.jdbc.postgresql.PostgreSQLExecutionFactory.initCapabilities(PostgreSQLExecutionFactory.java:72) ~[translator-jdbc-11.1.0-SNAPSHOT.jar!/:11.1.0-SNAPSHOT]
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (TEIID-5431) Function postgis_full_version() does not exist; Transaction Fails
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5431?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5431:
---------------------------------------
TEIID-4851 seems to be insufficient. It could be related to using a later pg server version.
> Function postgis_full_version() does not exist; Transaction Fails
> -----------------------------------------------------------------
>
> Key: TEIID-5431
> URL: https://issues.jboss.org/browse/TEIID-5431
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 11.0
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
>
> Within a XA transaction, when Teiid tries to do "initCapabilities" on Postgresql JDBC connector, it issues a function call "select postgis_full_version()" to detect the postgis version. However, if the postgis is not installed, then this fails.
> The undesired side effect is, the query already started a transaction then the whole transaction is rolled back.
> {code}
> Caused by: org.postgresql.util.PSQLException: ERROR: function postgis_full_version() does not exist
> Hint: No function matches the given name and argument types. You might need to add explicit type casts.
> Position: 8
> at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2455) ~[postgresql-9.4.1212.jre7.jar!/:9.4.1212.jre7]
> at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2155) ~[postgresql-9.4.1212.jre7.jar!/:9.4.1212.jre7]
> at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:288) ~[postgresql-9.4.1212.jre7.jar!/:9.4.1212.jre7]
> at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:430) ~[postgresql-9.4.1212.jre7.jar!/:9.4.1212.jre7]
> at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:356) ~[postgresql-9.4.1212.jre7.jar!/:9.4.1212.jre7]
> at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:303) ~[postgresql-9.4.1212.jre7.jar!/:9.4.1212.jre7]
> at org.postgresql.jdbc.PgStatement.executeCachedSql(PgStatement.java:289) ~[postgresql-9.4.1212.jre7.jar!/:9.4.1212.jre7]
> at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:266) ~[postgresql-9.4.1212.jre7.jar!/:9.4.1212.jre7]
> at org.postgresql.jdbc.PgStatement.executeQuery(PgStatement.java:233) ~[postgresql-9.4.1212.jre7.jar!/:9.4.1212.jre7]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_161]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_161]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_161]
> at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_161]
> at org.postgresql.ds.PGPooledConnection$StatementHandler.invoke(PGPooledConnection.java:423) ~[postgresql-9.4.1212.jre7.jar!/:9.4.1212.jre7]
> at com.sun.proxy.$Proxy90.executeQuery(Unknown Source) ~[na:na]
> at org.teiid.translator.jdbc.postgresql.PostgreSQLExecutionFactory.initCapabilities(PostgreSQLExecutionFactory.java:324) ~[translator-jdbc-11.1.0-SNAPSHOT.jar!/:11.1.0-SNAPSHOT]
> at org.teiid.translator.jdbc.postgresql.PostgreSQLExecutionFactory.initCapabilities(PostgreSQLExecutionFactory.java:72) ~[translator-jdbc-11.1.0-SNAPSHOT.jar!/:11.1.0-SNAPSHOT]
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (TEIID-5431) Function postgis_full_version() does not exist; Transaction Fails
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5431?page=com.atlassian.jira.plugin... ]
Work on TEIID-5431 started by Steven Hawkins.
---------------------------------------------
> Function postgis_full_version() does not exist; Transaction Fails
> -----------------------------------------------------------------
>
> Key: TEIID-5431
> URL: https://issues.jboss.org/browse/TEIID-5431
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 11.0
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
>
> Within a XA transaction, when Teiid tries to do "initCapabilities" on Postgresql JDBC connector, it issues a function call "select postgis_full_version()" to detect the postgis version. However, if the postgis is not installed, then this fails.
> The undesired side effect is, the query already started a transaction then the whole transaction is rolled back.
> {code}
> Caused by: org.postgresql.util.PSQLException: ERROR: function postgis_full_version() does not exist
> Hint: No function matches the given name and argument types. You might need to add explicit type casts.
> Position: 8
> at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2455) ~[postgresql-9.4.1212.jre7.jar!/:9.4.1212.jre7]
> at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2155) ~[postgresql-9.4.1212.jre7.jar!/:9.4.1212.jre7]
> at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:288) ~[postgresql-9.4.1212.jre7.jar!/:9.4.1212.jre7]
> at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:430) ~[postgresql-9.4.1212.jre7.jar!/:9.4.1212.jre7]
> at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:356) ~[postgresql-9.4.1212.jre7.jar!/:9.4.1212.jre7]
> at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:303) ~[postgresql-9.4.1212.jre7.jar!/:9.4.1212.jre7]
> at org.postgresql.jdbc.PgStatement.executeCachedSql(PgStatement.java:289) ~[postgresql-9.4.1212.jre7.jar!/:9.4.1212.jre7]
> at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:266) ~[postgresql-9.4.1212.jre7.jar!/:9.4.1212.jre7]
> at org.postgresql.jdbc.PgStatement.executeQuery(PgStatement.java:233) ~[postgresql-9.4.1212.jre7.jar!/:9.4.1212.jre7]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_161]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_161]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_161]
> at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_161]
> at org.postgresql.ds.PGPooledConnection$StatementHandler.invoke(PGPooledConnection.java:423) ~[postgresql-9.4.1212.jre7.jar!/:9.4.1212.jre7]
> at com.sun.proxy.$Proxy90.executeQuery(Unknown Source) ~[na:na]
> at org.teiid.translator.jdbc.postgresql.PostgreSQLExecutionFactory.initCapabilities(PostgreSQLExecutionFactory.java:324) ~[translator-jdbc-11.1.0-SNAPSHOT.jar!/:11.1.0-SNAPSHOT]
> at org.teiid.translator.jdbc.postgresql.PostgreSQLExecutionFactory.initCapabilities(PostgreSQLExecutionFactory.java:72) ~[translator-jdbc-11.1.0-SNAPSHOT.jar!/:11.1.0-SNAPSHOT]
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months