February 2012 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-499) pushdown of parsedate, parsetime, parsetimestamp

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-499?page=com.atlassian.jira.plugin.... ] Steven Hawkins commented on TEIID-499: -------------------------------------- We'll look at least adding the ability for translators to indicate support for literal format strings. > pushdown of parsedate, parsetime, parsetimestamp > ------------------------------------------------ > > Key: TEIID-499 > URL: https://issues.jboss.org/browse/TEIID-499 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Connector > Affects Versions: 6.0.0 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 7.7.1 > > > Client requesting pushdown of parsedate, parsetime, parsetimestamp functions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-499) pushdown of parsedate, parsetime, parsetimestamp

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-499?page=com.atlassian.jira.plugin.... ] Steven Hawkins reassigned TEIID-499: ------------------------------------ Assignee: Steven Hawkins > pushdown of parsedate, parsetime, parsetimestamp > ------------------------------------------------ > > Key: TEIID-499 > URL: https://issues.jboss.org/browse/TEIID-499 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Connector > Affects Versions: 6.0.0 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 7.7.1 > > > Client requesting pushdown of parsedate, parsetime, parsetimestamp functions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-499) pushdown of parsedate, parsetime, parsetimestamp

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-499?page=com.atlassian.jira.plugin.... ] Steven Hawkins updated TEIID-499: --------------------------------- Fix Version/s: 7.7.1 Affects Version/s: 6.0.0 (was: 9.x) Affects: Release Notes > pushdown of parsedate, parsetime, parsetimestamp > ------------------------------------------------ > > Key: TEIID-499 > URL: https://issues.jboss.org/browse/TEIID-499 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Connector > Affects Versions: 6.0.0 > Reporter: Marc Shirley > Fix For: 7.7.1 > > > Client requesting pushdown of parsedate, parsetime, parsetimestamp functions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[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, 4 months

2
8
0 / 0

[JBoss JIRA] Created: (TEIID-1613) Cannot define an implicit temp table with columns and a query value expression

by Steven Hawkins (JIRA)

Cannot define an implicit temp table with columns and a query value expression ------------------------------------------------------------------------------ Key: TEIID-1613 URL: https://issues.jboss.org/browse/TEIID-1613 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.4 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.4.1 I believe this may have been a regression from TEIID-1177. "insert into #x select 1 as y" works, but "insert into #x (y) select 1 as y" does not. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1593) Creating a temp table gets error that Cannot create temporary table "dddd". A table with the same name already exists.

by Paul Nittel (JIRA)

Creating a temp table gets error that Cannot create temporary table "dddd". A table with the same name already exists. ---------------------------------------------------------------------------------------------------------------------- Key: TEIID-1593 URL: https://issues.jboss.org/browse/TEIID-1593 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.4 Reporter: Paul Nittel Assignee: Steven Hawkins Logging into a VDB using SQuirreL, I entered: create local temporary table dddd (id string, name string) What I received was: Cannot create temporary table "dddd". A table with the same name already exists. There appears to be no way to create a temporary table, using this method. SELECT * INTO #temp from ... does work, however. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
2
0 / 0

[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, 4 months

3
7
0 / 0

[JBoss JIRA] (TEIID-1620) Fetch keyword not handled

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1620?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-1620. --------------------------------- > Fetch keyword not handled > ------------------------- > > Key: TEIID-1620 > URL: https://issues.jboss.org/browse/TEIID-1620 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Environment: JBDS 4.0 > Reporter: Joel Tosi > Assignee: Steven Hawkins > Priority: Minor > Fix For: 7.5 > > > Try to limit your query using native SQL construct fetch. While there are other ways to do this inside designer, support the native SQL construct for ease of use by data architects: > select * from SAMPLE_DATABASE fetch first 100 rows only > jBoss Designer error: > select * from SAMPLE_DATABASE fetch first 100 rows only > Remote org.teiid.api.exception.query.QueryParserException: Parsing error: > Encountered "fetch" at line 1, column 36. > Was expecting one of: > <EOF> > "group" ... > "having" ... > "intersect" ... > "limit" ... > "makedep" ... > "makenotdep" ... > "order" ... > "where" ... > "," ... > ";" ... > "union" ... > "except" ... > "option" ... > "cross" ... > "right" ... > "left" ... > "full" ... > "inner" ... > "join" ... > Elapsed Time: 0 hr, 0 min, 0 sec, 0 ms. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1550) Row level security enhancements

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1550?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-1550. --------------------------------- > Row level security enhancements > ------------------------------- > > Key: TEIID-1550 > URL: https://issues.jboss.org/browse/TEIID-1550 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Labels: 7.4Beta3 > Fix For: 7.4 > > > To assist with implementing row level security through UDFs the following enhancements are requested: > 1. Add the ability for data roles to cover functions. > 2. Add the ability to get the JAAS subject from the CommandContext so that UDFs can perform attribute or other checks on the subject easily. > Actual row level security will then be up to the implementer of the UDF. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1587) Minimize final project columns

by Steven Hawkins (JIRA)

Minimize final project columns ------------------------------ Key: TEIID-1587 URL: https://issues.jboss.org/browse/TEIID-1587 Project: Teiid Issue Type: Enhancement Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.0 The final project columns should be minimized so that duplicate deterministic project cols and literals are omitted from the pushdown query. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2012