[JBoss JIRA] (TEIID-4484) Random test failure with cancelled query
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4484?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4484:
---------------------------------------
I cleared the only direct interrupt call on the main thread I could find. Hopefully that is the only one.
> Random test failure with cancelled query
> ----------------------------------------
>
> Key: TEIID-4484
> URL: https://issues.jboss.org/browse/TEIID-4484
> Project: Teiid
> Issue Type: Bug
> Components: Integration Tests
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.1, 9.0.5
>
>
> Due to interrupt handling we can have spurious test failures such as:
> {code}
> Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.39 sec <<< FAILURE! - in org.teiid.jdbc.TestResultsCache
> testScope(org.teiid.jdbc.TestResultsCache) Time elapsed: 0.116 sec <<< ERROR!
> org.teiid.jdbc.TeiidSQLException: 57014 TEIID30160 The request 1kMLfcEKVhMX.0 has been cancelled.
> at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:146)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 9 months
[JBoss JIRA] (TEIID-4484) Random test failure with cancelled query
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-4484:
-------------------------------------
Summary: Random test failure with cancelled query
Key: TEIID-4484
URL: https://issues.jboss.org/browse/TEIID-4484
Project: Teiid
Issue Type: Bug
Components: Integration Tests
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 9.1, 9.0.5
Due to interrupt handling we can have spurious test failures such as:
{code}
Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.39 sec <<< FAILURE! - in org.teiid.jdbc.TestResultsCache
testScope(org.teiid.jdbc.TestResultsCache) Time elapsed: 0.116 sec <<< ERROR!
org.teiid.jdbc.TeiidSQLException: 57014 TEIID30160 The request 1kMLfcEKVhMX.0 has been cancelled.
at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:146)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 9 months
[JBoss JIRA] (TEIID-3952) Update to updatable internal materialized view should update the materialized view as well as the database
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3952?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3952:
----------------------------------
Fix Version/s: 9.2
(was: 9.1)
> Update to updatable internal materialized view should update the materialized view as well as the database
> ----------------------------------------------------------------------------------------------------------
>
> Key: TEIID-3952
> URL: https://issues.jboss.org/browse/TEIID-3952
> Project: Teiid
> Issue Type: Enhancement
> Components: VDB
> Affects Versions: 8.7
> Environment: Red Hat JBoss Data Virtualization 6.2 based on Teiid 8.7.x
> Reporter: Andy Yuen
> Assignee: Steven Hawkins
> Labels: jboss
> Fix For: 9.2
>
>
> Updating an updatable internal materized view updates the database but not the materialized view at present. The requested enhancement is that they, both, should be updated.
> Setup
> Client - SquirrelSQL to access JDV
> JDV 6.2 - with an updatable nternal materialized view of one table from the data source
> Data Source - just one data source: MySQL
> I can see from the console that the target table/view has been materialized
> Then I did the following:
> 1) select a row from the materialized table
> 2) update a field in a row in the materialized view
> 3) select that row (value unchanged ie, same as int 1) - tried multiple times
> 4) issue EXEC SYSADMIN.refreshMatViewRow(...) using primary key for the row that has been changed
> 5) select that row (value unchanged) - now I can see the changed data
> This behaviour is counter-intuitive because I was expecting that since it is an updatable materialized view, my change will write through the materialized view ie, change both the materialized view as well as the database. But in this case, it changed the database and not the materialized view?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 9 months
[JBoss JIRA] (TEIID-4012) Implement XA transaction support for Teiid ODBC
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4012?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4012:
----------------------------------
Fix Version/s: 9.2
(was: 9.1)
> Implement XA transaction support for Teiid ODBC
> -----------------------------------------------
>
> Key: TEIID-4012
> URL: https://issues.jboss.org/browse/TEIID-4012
> Project: Teiid
> Issue Type: Feature Request
> Components: ODBC
> Affects Versions: 8.7.1.6_2
> Environment: Red Hat JBoss Data Virtualization 6.2.2 on EAP6.4.0 patched to version 6.4.5,
> JBoss Developer Studio 8.1.0GA with Teiid Designer plugin 9.0.3.Final.v20150810-1438-B1157
> 64-bit Windows 7 environment
> Reporter: Steve Tran
> Assignee: Steven Hawkins
> Fix For: 9.2
>
>
> Without XA support the pg client will hit the following error:
> TEIID30020 Processing exception for request ... 'Group does not exist: pg_prepared_xacts'
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 9 months