[JBoss JIRA] Created: (TEIID-1681) Limit not working as expected
by Gaurav Chaudhary (JIRA)
Limit not working as expected
-----------------------------
Key: TEIID-1681
URL: https://issues.jboss.org/browse/TEIID-1681
Project: Teiid
Issue Type: Bug
Components: JDBC Driver
Affects Versions: 7.3
Reporter: Gaurav Chaudhary
Assignee: Steven Hawkins
select CHORUS_B."ID", CHORUS_B."ACCESS_MODE", CHORUS_B."USER_ID", CHORUS_B."CREATED_ON", CHORUS_B."NOTE",'chorusdata.note' as "__objecttype__" from
(select * from chorus_notes.RETRIEVE_NOTES where
OBJECT_PKEY =
xmlserialize(xmlelement("demodata.rule", XMLATTRIBUTES(cast('name 1' as String) as "name",cast('sysid 0' as String) as "system",cast('user 1000' as String) as "user")) as String)) as CHORUS_B LIMIT 50
This query is not returning correct results unless we remove Limit from this.
If we include Limit over here, it interchanges the columns and returning incorrect data.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] Created: (TEIID-1465) Join between char and varchar
by Claudio Venturini (JIRA)
Join between char and varchar
-----------------------------
Key: TEIID-1465
URL: https://issues.jboss.org/browse/TEIID-1465
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.3
Environment: Teiid 7.3 deployed on Jboss AS 5.1.0 GA running on Ubuntu Server 10.04 LTS, MySQL 5.1.51 running on the same machine as JBoss, SQL Server 2000 Standard SP4 running on Windows Server 2003
Reporter: Claudio Venturini
Assignee: Steven Hawkins
Joins between char and varchar fields fail.
Suppose to have a table T1 with a field A, declared as char(10), and a table T2 with a field B, declared as varchar(10). Suppose that the two tables have the following data.
*T1*:
||A||
|ML0001|
*T2*:
||B||
|ML0001|
When performing a INNER JOIN with the condition {{T1.A = T2.B}} the result set is empty, even if the two record match correctly.
This happens when the two base tables refer to two different sources, because if they are in the same source Teiid pushes the join to the source, which computes it correctly.
I think the problem is in the comparison of the two strings. I have the table T1 in SQL Server 2000, and the table T2 in MySQL 5.1.
If one asks SQL Server to convert the string to bytes, the result is {{0x4D4C3030303120202020}}, because the string is filled with (invisible) blanks in order to reach the limit of 10 characters. Note that if one asks for the length of that string, SQL Server states (correctly) that it is 6 characters.
The string in MySQL is a VARCHAR(10), so its conversion to binary is {{0x4D4C30303031}}.
I think that Teiid compares the two binary strings in their entire length. That comparison fails, and no match is found.
The problem remains even if the table T1 is placed in MySQL, and T2 in SQL Server (the opposite situation). I also verified that the problem exists either when querying the source models or view models built over them.
*Workaround:*
A workaround exists but it is too complex (IMHO). I haven't tested it with many records, but I think it will slow down performances considerably.
It consists in casting the string from char to varchar, and then trimming it (with RTRIM() and LTRIM() because SQL Server doesn't support TRIM()). So the join condition is:
{noformat}
RTRIM(LTRIM(CAST(T1.A AS VARCHAR))) = T2.B
{noformat}
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] Created: (TEIID-1612) Tried a custom log appended, but the LoggingEvent.getMessage() returns org.teiid.logging.LogMessage and not org.teiid.logging.CommandLogMessage
by Van Halbert (JIRA)
Tried a custom log appended, but the LoggingEvent.getMessage() returns org.teiid.logging.LogMessage and not org.teiid.logging.CommandLogMessage
-----------------------------------------------------------------------------------------------------------------------------------------------
Key: TEIID-1612
URL: https://issues.jboss.org/browse/TEIID-1612
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 7.1.1
Reporter: Van Halbert
Assignee: Steven Hawkins
Tried to create a custom logger, following what the doc says:
------
If you want to build a custom appender for command logging that will have access to log4j "LoggingEvents" to the "COMMAND_LOG" context, it will have a message that is an instance of org.teiid.logging.CommandLogMessage defined in the teiid-api-7.4.jar use these class in your development.
-------
but the actual object type from event.getMessage() is: LOGGING EVENT MSG TYPE: org.teiid.logging.LogMessage
(this is a sysout from the custom appender)
And there, don't have access to the similar methods provided n CommandLogMessage.
I'll attach the code.
Did I implement something incorrectly?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] Created: (TEIID-1585) Make payload available in ExecutionFactory.getConnection
by Mark Addleman (JIRA)
Make payload available in ExecutionFactory.getConnection
--------------------------------------------------------
Key: TEIID-1585
URL: https://issues.jboss.org/browse/TEIID-1585
Project: Teiid
Issue Type: Feature Request
Components: Connector API
Affects Versions: 7.3
Reporter: Mark Addleman
Assignee: Steven Hawkins
We require user-specific connections to our backend datasources. We pass user credentials to the translators using the payload but the payload is not available in the getConnection(Factory f) method. I propose adding public getConnection(Factory f, Serializable payload) method in ExecutionFactory whose default implementation is to call getConnection(Factory f).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] Created: (TEIID-1640) QueryTimeout connection parameter does not cancel long-running queries
by Paul Nittel (JIRA)
QueryTimeout connection parameter does not cancel long-running queries
----------------------------------------------------------------------
Key: TEIID-1640
URL: https://issues.jboss.org/browse/TEIID-1640
Project: Teiid
Issue Type: Bug
Components: JDBC Driver
Affects Versions: 7.4
Environment: Fedora 14 (server & client), Teiid 7.4 Final
Reporter: Paul Nittel
Assignee: Steven Hawkins
Testing XML files as data sources involves running queries which can take a long time (minutes). I defined my connection URL (in SQuirreL) as jdbc:teiid:VDB@mm://localhost:31000;QueryTimeout=1
The next query I executed processed for over 4 seconds, but there was no evidence of an attempt to cancel the query.
I've got a series of XML files you can use to test this, if you want. They're too big to attach (even when zipped).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months