[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 resolved TEIID-4484.
-----------------------------------
Resolution: Done
Removed the interrupt entirely - as my last commit was a mistake in that isInterrrupted doesn't clear.
> Random test failure with cancelled query
> ----------------------------------------
>
> Key: TEIID-4484
> URL: https://issues.jboss.org/browse/TEIID-4484
> …
[View More] 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)
[View Less]
8 years, 4 months
[JBoss JIRA] (TEIID-4485) import-vdb VDB name case-sensitive
by Chandra Akkinepalli (JIRA)
[ https://issues.jboss.org/browse/TEIID-4485?page=com.atlassian.jira.plugin... ]
Chandra Akkinepalli reassigned TEIID-4485:
------------------------------------------
Assignee: Steven Hawkins (was: Chandra Akkinepalli)
> import-vdb VDB name case-sensitive
> ----------------------------------
>
> Key: TEIID-4485
> URL: https://issues.jboss.org/browse/TEIID-4485
> Project: Teiid
> Issue Type: Bug
> …
[View More]Components: VDB
> Affects Versions: 8.7
> Reporter: Chandra Akkinepalli
> Assignee: Steven Hawkins
> Fix For: 9.1, 9.0.5
>
>
> I have built couple of VDBs using designer, their names are all CAPS and wanted to import these 2 VDBs as views in my 3rd VDB. As the VDB name is cases insensitive in connect string i used lower case to connect to the VDB to do JDBC import. After i completed my 3rd VDB when i tried to deploy the VDB onto the server it is going into INACTIVE state, after changing my connection string to upper case and reimporting the VDB i was able to deploy the 3rd VDB and it state turned to ACTIVE.
> The VDB import definition seem's to be case sensitive and this may be the cause of the errors.
> I haven't tested this in Dynamic VDB.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
8 years, 4 months
[JBoss JIRA] (TEIID-4485) import-vdb VDB name case-sensitive
by Chandra Akkinepalli (JIRA)
[ https://issues.jboss.org/browse/TEIID-4485?page=com.atlassian.jira.plugin... ]
Work on TEIID-4485 stopped by Chandra Akkinepalli.
--------------------------------------------------
> import-vdb VDB name case-sensitive
> ----------------------------------
>
> Key: TEIID-4485
> URL: https://issues.jboss.org/browse/TEIID-4485
> Project: Teiid
> Issue Type: Bug
> Components: VDB
> Affects Versions: 8.7
&…
[View More]gt; Reporter: Chandra Akkinepalli
> Assignee: Chandra Akkinepalli
> Fix For: 9.1, 9.0.5
>
>
> I have built couple of VDBs using designer, their names are all CAPS and wanted to import these 2 VDBs as views in my 3rd VDB. As the VDB name is cases insensitive in connect string i used lower case to connect to the VDB to do JDBC import. After i completed my 3rd VDB when i tried to deploy the VDB onto the server it is going into INACTIVE state, after changing my connection string to upper case and reimporting the VDB i was able to deploy the 3rd VDB and it state turned to ACTIVE.
> The VDB import definition seem's to be case sensitive and this may be the cause of the errors.
> I haven't tested this in Dynamic VDB.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
8 years, 4 months
[JBoss JIRA] (TEIID-4485) import-vdb VDB name case-sensitive
by Chandra Akkinepalli (JIRA)
[ https://issues.jboss.org/browse/TEIID-4485?page=com.atlassian.jira.plugin... ]
Work on TEIID-4485 started by Chandra Akkinepalli.
--------------------------------------------------
> import-vdb VDB name case-sensitive
> ----------------------------------
>
> Key: TEIID-4485
> URL: https://issues.jboss.org/browse/TEIID-4485
> Project: Teiid
> Issue Type: Bug
> Components: VDB
> Affects Versions: 8.7
&…
[View More]gt; Reporter: Chandra Akkinepalli
> Assignee: Chandra Akkinepalli
> Fix For: 9.1, 9.0.5
>
>
> I have built couple of VDBs using designer, their names are all CAPS and wanted to import these 2 VDBs as views in my 3rd VDB. As the VDB name is cases insensitive in connect string i used lower case to connect to the VDB to do JDBC import. After i completed my 3rd VDB when i tried to deploy the VDB onto the server it is going into INACTIVE state, after changing my connection string to upper case and reimporting the VDB i was able to deploy the 3rd VDB and it state turned to ACTIVE.
> The VDB import definition seem's to be case sensitive and this may be the cause of the errors.
> I haven't tested this in Dynamic VDB.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
8 years, 4 months
[JBoss JIRA] (TEIID-4486) Improve performance of st_extent
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-4486:
-------------------------------------
Summary: Improve performance of st_extent
Key: TEIID-4486
URL: https://issues.jboss.org/browse/TEIID-4486
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Affects Versions: 9.0, 8.12.5
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 9.1, 9.0.5
The implementation of st_extent …
[View More]is very costly. It should instead be based upon the Envelope class. Also it is not being pushed to pg.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
8 years, 4 months
[JBoss JIRA] (TEIID-4485) import-vdb VDB name case-sensitive
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4485?page=com.atlassian.jira.plugin... ]
Steven Hawkins reassigned TEIID-4485:
-------------------------------------
Fix Version/s: 9.1
9.0.5
Affects Version/s: 8.7
(was: 9.0.4)
Assignee: Steven Hawkins (was: Barry LaFond)
This issue here is that on deploy the vdb is creating service dependencies to the imported vdb, which are case sensitive.
> import-vdb VDB name case-…
[View More]sensitive
> ----------------------------------
>
> Key: TEIID-4485
> URL: https://issues.jboss.org/browse/TEIID-4485
> Project: Teiid
> Issue Type: Bug
> Components: VDB
> Affects Versions: 8.7
> Reporter: Chandra Akkinepalli
> Assignee: Steven Hawkins
> Fix For: 9.1, 9.0.5
>
>
> I have built couple of VDBs using designer, their names are all CAPS and wanted to import these 2 VDBs as views in my 3rd VDB. As the VDB name is cases insensitive in connect string i used lower case to connect to the VDB to do JDBC import. After i completed my 3rd VDB when i tried to deploy the VDB onto the server it is going into INACTIVE state, after changing my connection string to upper case and reimporting the VDB i was able to deploy the 3rd VDB and it state turned to ACTIVE.
> The VDB import definition seem's to be case sensitive and this may be the cause of the errors.
> I haven't tested this in Dynamic VDB.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
8 years, 4 months
[JBoss JIRA] (TEIID-4485) import-vdb VDB name case-sensitive
by Chandra Akkinepalli (JIRA)
Chandra Akkinepalli created TEIID-4485:
------------------------------------------
Summary: import-vdb VDB name case-sensitive
Key: TEIID-4485
URL: https://issues.jboss.org/browse/TEIID-4485
Project: Teiid
Issue Type: Bug
Components: VDB
Affects Versions: 9.0.4
Reporter: Chandra Akkinepalli
Assignee: Barry LaFond
I have built couple of VDBs using designer, their names are all CAPS and …
[View More]wanted to import these 2 VDBs as views in my 3rd VDB. As the VDB name is cases insensitive in connect string i used lower case to connect to the VDB to do JDBC import. After i completed my 3rd VDB when i tried to deploy the VDB onto the server it is going into INACTIVE state, after changing my connection string to upper case and reimporting the VDB i was able to deploy the 3rd VDB and it state turned to ACTIVE.
The VDB import definition seem's to be case sensitive and this may be the cause of the errors.
I haven't tested this in Dynamic VDB.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
8 years, 4 months
[JBoss JIRA] (TEIID-3630) Support merge statement pushdown
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3630?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3630.
-----------------------------------
Resolution: Done
Marking as resolved with pushdown support to hbase and h2. Also change the primary terminology to be upsert rather than merge, since the merge statement does have a standard meaning that we do not implement.
For hbase we may also want to consider a translator setting to disallow the conversion of a regular insert to an …
[View More]upsert - to force the semantics of insert to be respected.
Other sources will be added as needed.
> Support merge statement pushdown
> --------------------------------
>
> Key: TEIID-3630
> URL: https://issues.jboss.org/browse/TEIID-3630
> Project: Teiid
> Issue Type: Enhancement
> Components: Connector API, Grammar, Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.1
>
>
> We should add support for the merge statement to be pushded down.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
8 years, 4 months