[JBoss JIRA] Created: (TEIID-1281) DB2 substring index bounds are different than teiid
by Steven Hawkins (JIRA)
DB2 substring index bounds are different than teiid
---------------------------------------------------
Key: TEIID-1281
URL: https://jira.jboss.org/browse/TEIID-1281
Project: Teiid
Issue Type: Quality Risk
Components: Misc. Connectors
Affects Versions: 7.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Minor
Fix For: 7.3
DB2/Derby do not allow the start argument to be negative or be greater than or equal to the length. The length parameter cannot be negative (Teiid returns null), and it plus the start cannot exceed the string length.
In general we are inconsistent with our handling of negative string indexing. For example the locate function. We should look at making this more consistent in Teiid 8.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] Created: (TEIID-1329) API to force metadata read
by Mark Addleman (JIRA)
API to force metadata read
--------------------------
Key: TEIID-1329
URL: https://jira.jboss.org/browse/TEIID-1329
Project: Teiid
Issue Type: Feature Request
Components: AdminApi
Affects Versions: 7.1
Reporter: Mark Addleman
Assignee: Steven Hawkins
Priority: Minor
We have a dynamic set of datasources that are accessed through Teiid. Each data source is represented as a different model within the VDB. Some data sources may not be available at the time Teiid executes the translator's getMetadata() method. When our code detects the data source is available, I'd like to poke Teiid to re-read the appropriate translator's metadata.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] Created: (TEIID-1383) Partial Results processing fails too easily when a source is unavailable
by Paul Nittel (JIRA)
Partial Results processing fails too easily when a source is unavailable
------------------------------------------------------------------------
Key: TEIID-1383
URL: https://jira.jboss.org/browse/TEIID-1383
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.1.1
Environment: Fedora 12, SOA-P ER4
Reporter: Paul Nittel
Assignee: Steven Hawkins
I'm updating the MMx partial results test to work with Teiid and ran into this problem while testing that.
To mimic an unavailable data source, I munged the server name in the data source definition (-ds) file. Using SQuirreL, I first "set partialResultsMode true" and then query a unioned table: SELECT * FROM PartialVM.MyUnionTable order by INTKEY.
I'm getting back an exception about the bad connection, but no apparent attempt to continue the query without that source is made. Steve Hawkins suspects, "it's testing partial results at too low of a level".
Artifacts will be attached.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months