November 2011 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1749) Update the LDAP configuration documentation

by Ramesh Reddy (JIRA)

Update the LDAP configuration documentation ------------------------------------------- Key: TEIID-1749 URL: https://issues.jboss.org/browse/TEIID-1749 Project: Teiid Issue Type: Task Components: Documentation Affects Versions: 7.5 Reporter: Ramesh Reddy Assignee: Steven Hawkins Fix For: 7.4.1, 7.6 Attachments: eds-ldap.html Update the LDAP configuration in the Admin Guide with attached. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

5
5
0 / 0

[JBoss JIRA] Created: (TEIID-1705) Encountered NPE in SQLStringVisitor for TIMESTAMPADD and TIMESTAMPDIFF

by Mark Drilling (JIRA)

Encountered NPE in SQLStringVisitor for TIMESTAMPADD and TIMESTAMPDIFF ---------------------------------------------------------------------- Key: TEIID-1705 URL: https://issues.jboss.org/browse/TEIID-1705 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.4 Reporter: Mark Drilling Assignee: Steven Hawkins I was using expression builder in Designer when I encountered this NPE. java.lang.NullPointerException at org.teiid.query.sql.visitor.SQLStringVisitor.visit(SQLStringVisitor.java:1280) at org.teiid.query.sql.symbol.Function.acceptVisitor(Function.java:182) at org.teiid.query.sql.visitor.SQLStringVisitor.getSQLString(SQLStringVisitor.java:164) at com.metamatrix.query.internal.ui.builder.util.LanguageObjectLabelProvider.getText(LanguageObjectLabelProvider.java:129) I think the visit method for FUNCTION in SQLStringVisitor just needs to do a null check on the first arg. I'm attaching a code patch. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

3
7
0 / 0

[JBoss JIRA] Created: (TEIID-832) Support calling oracle stored functions returning result sets as stored procedures

by Steven Hawkins (JIRA)

Support calling oracle stored functions returning result sets as stored procedures ---------------------------------------------------------------------------------- Key: TEIID-832 URL: https://jira.jboss.org/jira/browse/TEIID-832 Project: Teiid Issue Type: Feature Request Components: JDBC Connector Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.3.0 This is only an issue with oracle native drivers, which need to have the returned result set explicitly called as a return parameter. For this to work we'll need to ensure that the import metadata on a procedure is being set to isFunction appropriately and then use that metadata in the Oracle connector. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

5
7
0 / 0

[JBoss JIRA] (TEIID-141) Develop a strategy for backtracking during planning

by Steven Hawkins (Closed) (JIRA)

[ https://issues.jboss.org/browse/TEIID-141?page=com.atlassian.jira.plugin.... ] Steven Hawkins closed TEIID-141. -------------------------------- > Develop a strategy for backtracking during planning > --------------------------------------------------- > > Key: TEIID-141 > URL: https://issues.jboss.org/browse/TEIID-141 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 9.x > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Original Estimate: 2 days > Remaining Estimate: 2 days > > Currently rule raise access is run after rule push criteria, which can cause non-pushable criteria to end up in undesirable points of the plan. It would be good to either run rule raise access before the first run of push select criteria, or allow rule raise access to detect what nodes it can "push up". -- 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

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1764) Hibernate Month Date Extraction

by Andrew Block (JIRA)

Hibernate Month Date Extraction ------------------------------- Key: TEIID-1764 URL: https://issues.jboss.org/browse/TEIID-1764 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1.1 Reporter: Andrew Block Assignee: Steven Hawkins When using teiid-hibernate-dialect-7.1.1.GA, the TeiidDialect does not include a function to get the month value of a date object. It includes functions to get other date attributes (year, dayofmonth etc). Without a defined function, attempting to get a month value falls back on the hibernate-core function which attempts to utilize an extract method which is not supported in 7.1.1. Being able to obtain a month value from a date is a critical requirement. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (TEIID-1747) hasROLE(rolename) function always returns false

by Paul Nittel (JIRA)

hasROLE(rolename) function always returns false ----------------------------------------------- Key: TEIID-1747 URL: https://issues.jboss.org/browse/TEIID-1747 Project: Teiid Issue Type: Bug Components: Query Engine Environment: Fedora 14, SOA-P 5.2 ER3 Reporter: Paul Nittel Assignee: Steven Hawkins Given teiid-security-roles.properties contains user=NoRolesRole and the VDB in use has data roles defined, when logged into Teiid as user, the following SQL should return true. SELECT hasROLE('NoRolesRole') However, it always--AFAICT--returns false. (Roles are working for this VDB as this user is not able to query certain tables.) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

4
10
0 / 0

[JBoss JIRA] Created: (TEIID-1732) Native PG Connector does not pass back errors to client

by Graeme Gillies (JIRA)

Native PG Connector does not pass back errors to client ------------------------------------------------------- Key: TEIID-1732 URL: https://issues.jboss.org/browse/TEIID-1732 Project: Teiid Issue Type: Bug Affects Versions: 7.5 Environment: Red Hat Enterprise Linux Server release 5.7 (Tikanga) JBoss EAP 5.1.1 java version "1.6.0_20" OpenJDK Runtime Environment (IcedTea6 1.9.8) (rhel-1.22.1.9.8.el5_6-x86_64) OpenJDK 64-Bit Server VM (build 19.0-b09, mixed mode) Reporter: Graeme Gillies Assignee: Steven Hawkins Hi, When we have people connecting to the native postgres emulation component of teiid (port 35432) using say, perl, or python, they can connect and query stuff fine, but if they give it a bad query (for exammple, the statement "selectx * from table.name") we see an error in the server side long saying the syntax is incorrect, but this error is never passed back to the client. The client just sits there waiting for a response that never comes. Can we please have any and all errors returned back to the client correctly? Thanks, Graeme -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

4
5
0 / 0

[JBoss JIRA] Created: (TEIID-1665) Optimize SELECT of all constants

by Mark Addleman (JIRA)

Optimize SELECT of all constants -------------------------------- Key: TEIID-1665 URL: https://issues.jboss.org/browse/TEIID-1665 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.4 Reporter: Mark Addleman Assignee: Steven Hawkins Priority: Minor If a translator supports LIMIT but does not support select expressions, SELECT 'A' as A, 'B' as B FROM xyz GROUP BY A, B should be written as SELECT * FROM xyz LIMIT 1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

3
5
0 / 0

[JBoss JIRA] (TEIID-1763) EDS inner join returns no data, left join does

by Steven Hawkins (Closed) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1763?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-1763. --------------------------------- > EDS inner join returns no data, left join does > ----------------------------------------------- > > Key: TEIID-1763 > URL: https://issues.jboss.org/browse/TEIID-1763 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.1.1 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 7.1.1 > > > We've encountered a rather concerning case of the wrong data (no data) being returned on a federated query. We're pretty sure it should return data, and when we change an inner join to a left join it does return the data we expect (complete data, with a value for the column being left joined rather than a null). > This issue has been tested on 5.2 ER3 and is fixed, but the customer needs a CP for the 5.1 release. -- 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

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1773) Ingres as source - Query with LOCATE causing stackoverflow error

by Steven Hawkins (Closed) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1773?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-1773. --------------------------------- > Ingres as source - Query with LOCATE causing stackoverflow error > ---------------------------------------------------------------- > > Key: TEIID-1773 > URL: https://issues.jboss.org/browse/TEIID-1773 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 7.4.1 > Reporter: Warren Gibson > Assignee: Steven Hawkins > Fix For: 7.4.1, 7.6 > > > EDS Query Testing is getting unexpected results on 16 queries involving LOCATE. A couple examples queries are given below: > SELECT INTKEY, LOCATE(1, STRINGNUM) FROM BQT1.SmallA ORDER BY intkey (Expected 50 records but received only 0) > Remote org.teiid.core.TeiidProcessingException: Source: null > see stackoverflow.log attached > SELECT INTKEY FROM BQT1.SmallA WHERE LOCATE(1, INTKEY) = 1 ORDER BY INTKEY > Remote org.teiid.core.TeiidProcessingException: Source: null > Is also a stackoverflow error. -- 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

14 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2011