June 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Closed: (TEIID-218) Security URL properties handling

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-218?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins closed TEIID-218. ------------------------------- > Security URL properties handling > -------------------------------- > > Key: TEIID-218 > URL: https://jira.jboss.org/browse/TEIID-218 > Project: Teiid > Issue Type: Sub-task > Components: JDBC Driver, Server > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 7.0 > > > Defect Tracker #24196: Security URL properties are currently a mess in that there are three properties, clientToken, credentials, and trustedPayload that are all eventually treated at the trustedPayload. This is not desirable. Instead we should pass all of the connection properties to the membership service (as a map) for access by membership domains. This would remove the need to specifically pass the trustedPayload and application name as parameters. This could also be done for connectors provided that the message or the transport containing the connection properties is encrypted. -- 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

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-754) LOCATE() function isn't being translated correctly by Oracle Connector

by Larry O'Leary (JIRA)

LOCATE() function isn't being translated correctly by Oracle Connector ---------------------------------------------------------------------- Key: TEIID-754 URL: https://jira.jboss.org/jira/browse/TEIID-754 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 6.1.0, 6.0.0, 6.2.0 Reporter: Larry O'Leary Assignee: Larry O'Leary Fix For: 6.2.0 The rewritten/translated query for the MMx LOCATE() function to Oracle's instr() function does not appear to be correct. SELECT locate(INTNUM, '234567890', 1) FROM SMALLA WHERE INTKEY = 26 Is being rewritten for Oracle as: SELECT instr('234567890', to_char(SmallA.IntNum), 2) FROM SmallA WHERE SmallA.IntKey = 26 In this case Oracle will return 0 for instr() because Oracle starts at position 1. The query should be: SELECT instr('234567890', to_char(SmallA.IntNum), 1) FROM SmallA WHERE SmallA.IntKey = 26 Furthermore, if I pass a negative value to LOCATE() it appears we assume position 1. If the negative value is sent to Oracle, Oracle goes from the end of the string. We should prevent this (if not already). In 5.5.1 the rewritten query is even different and may ore may not be correct. I have not checked 5.5.3/5.5.4 and/or Westport/Teiid. Here are the test cases that should cover this issue: public void testRewriteLocate() throws Exception { String input = "SELECT locate(INTNUM, 'chimp', 1) FROM SMALLA"; //$NON-NLS-1$ String output = "SELECT instr('chimp', to_char(SmallA.IntNum), 1) FROM SmallA"; //$NON-NLS-1$ helpTestVisitor(getTestVDBPath(), input, new Integer(TranslatedCommand.EXEC_TYPE_QUERY), output); } public void testRewriteLocate2() throws Exception { String input = "SELECT locate(STRINGNUM, 'chimp') FROM SMALLA"; //$NON-NLS-1$ String output = "SELECT instr('chimp', SmallA.StringNum) FROM SmallA"; //$NON-NLS-1$ helpTestVisitor(getTestVDBPath(), input, new Integer(TranslatedCommand.EXEC_TYPE_QUERY), output); } public void testRewriteLocate3() throws Exception { String input = "SELECT locate(INTNUM, '234567890', 1) FROM SMALLA WHERE INTKEY = 26"; //$NON-NLS-1$ String output = "SELECT instr('234567890', to_char(SmallA.IntNum), 1) FROM SmallA WHERE SmallA.IntKey = 26"; //$NON-NLS-1$ helpTestVisitor(getTestVDBPath(), input, new Integer(TranslatedCommand.EXEC_TYPE_QUERY), output); } public void testRewriteLocate4() throws Exception { String input = "SELECT locate('c', 'chimp', 1) FROM SMALLA"; //$NON-NLS-1$ String output = "SELECT 1 FROM SmallA"; //$NON-NLS-1$ helpTestVisitor(getTestVDBPath(), input, new Integer(TranslatedCommand.EXEC_TYPE_QUERY), output); } public void testRewriteLocate5() throws Exception { String input = "SELECT locate(STRINGNUM, 'chimp', -5) FROM SMALLA"; //$NON-NLS-1$ String output = "SELECT instr('chimp', SmallA.StringNum, 1) FROM SmallA"; //$NON-NLS-1$ helpTestVisitor(getTestVDBPath(), input, new Integer(TranslatedCommand.EXEC_TYPE_QUERY), output); } -- 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, 6 months

3
6
0 / 0

[JBoss JIRA] Created: (TEIID-882) Look into using javax.xml.xpath in the XML-Relational connectors.

by John Doyle (JIRA)

Look into using javax.xml.xpath in the XML-Relational connectors. ----------------------------------------------------------------- Key: TEIID-882 URL: https://jira.jboss.org/jira/browse/TEIID-882 Project: Teiid Issue Type: Task Components: XML Connector Reporter: John Doyle Assignee: John Doyle Fix For: 7.0 Using the javax.xml.xpath implementation might give us a more complete XPath capability (functions, etc). -- 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, 6 months

2
4
0 / 0

[JBoss JIRA] Closed: (TEIID-981) Ability to cache XML documents

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-981?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins closed TEIID-981. ------------------------------- > Ability to cache XML documents > ------------------------------ > > Key: TEIID-981 > URL: https://jira.jboss.org/browse/TEIID-981 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Lance Phillips > Assignee: Steven Hawkins > Fix For: 7.0 > > > We can currently cache relational result sets but have to re-create the XML document. XML being verbose this re-creation could take some time. This requirement would probably need a materialized flag on the document model, and the ability to store the XML document in an RDBMS (As a blob?) -- 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

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1007) Remove unnecessary inline views over group bys

by Steven Hawkins (JIRA)

Remove unnecessary inline views over group bys ---------------------------------------------- Key: TEIID-1007 URL: https://jira.jboss.org/jira/browse/TEIID-1007 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.0 Our check for removing a view layer only checks for a grouping node, it should check to see if any of the projected columns are used in the group by. e.g. instead of select max(c1) from (select c1 from table) v1 -> select max(c1) from table -- 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, 6 months

2
2
0 / 0

[JBoss JIRA] Closed: (TEIID-502) Allow Multiple UDF Definition Models

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIID-502?page=com.atlassian.jira.plugin.sy... ] Steve Hawkins closed TEIID-502. ------------------------------- > Allow Multiple UDF Definition Models > ------------------------------------ > > Key: TEIID-502 > URL: https://jira.jboss.org/browse/TEIID-502 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Reporter: Debbie Steigner > Assignee: Ramesh Reddy > Fix For: 7.0 > > > Customer feature request from Issue Tracker ticket# 228151: > The current mechanism for UDF (user-defined functions) is limited to having one model (FunctionDefinitions.xmi) in which UDF are defined and related to their Java implementations. This results in a configuration management problem even on just one project. For multiple projects it becomes a nightmare, unless we abandon all hope of building a body of reusable UDFs. I would therefore suggest that designer and server need to support multiple UDF definition models, identified by the extensions already defined and used for FunctionDefinitions.xmi. > Similar to JBEDSP-632 -- 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

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1097) Add support for nested table references

by Steve Hawkins (JIRA)

Add support for nested table references --------------------------------------- Key: TEIID-1097 URL: https://jira.jboss.org/browse/TEIID-1097 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.0 Reporter: Steve Hawkins Assignee: Steve Hawkins Fix For: 7.1 Our current approach to procedural relational queries that relies upon criteria is difficult to use and causes numerous problems, such as TEIID-32 and unclear applicability of default values. It would be easier to just add support nested table references. e.g. select * from t, table(... t.x) t1 Where the join between the procedure or query contained in the table expression is implied. See http://publib.boulder.ibm.com/infocenter/dzichelp/v2r2/index.jsp?topic=/c... for more on the usage constraints. This functionality is also needed by the XMLTABLE function. -- 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

14 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-807) Develop the new Teiid Console using JOPR for its core framework

by Van Halbert (JIRA)

Develop the new Teiid Console using JOPR for its core framework --------------------------------------------------------------- Key: TEIID-807 URL: https://jira.jboss.org/jira/browse/TEIID-807 Project: Teiid Issue Type: Feature Request Components: Console, Jopr Plugin Affects Versions: 6.3.0 Reporter: Van Halbert Assignee: Van Halbert Use the the JOPR framework to develop the new Teiid console for administrating and monitoring a Teiid resource. -- 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, 6 months

4
6
0 / 0

[JBoss JIRA] Created: (TEIID-988) 3 argument locate function on postgres reports the wrong value

by Steven Hawkins (JIRA)

3 argument locate function on postgres reports the wrong value -------------------------------------------------------------- Key: TEIID-988 URL: https://jira.jboss.org/jira/browse/TEIID-988 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.0 Any time the locate third argument is greater than 1 the postgres translation is returning the wrong position value. -- 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, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-890) AdminShell runs as if bsh.interactive=false was specified, even though interactive

by Paul Nittel (JIRA)

AdminShell runs as if bsh.interactive=false was specified, even though interactive ---------------------------------------------------------------------------------- Key: TEIID-890 URL: https://jira.jboss.org/jira/browse/TEIID-890 Project: Teiid Issue Type: Bug Components: Tools Affects Versions: 7.0 Environment: Fedora 10, JDK Java HotSpot(TM) Server VM (build 11.0-b16, mixed mode), 7.0 M1 build Reporter: Paul Nittel Assignee: Steven Hawkins I installed and started Teiid with a query testing VDB deployed. When I entered "SELECT * FROM Smalla;", it went back to the interactive prompt without displaying any data. Executing "bsh.interactive=true;" before the SELECT corrected the problem (otherwise I had to "printResults();") In previous versions this has worked as intended. -- 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, 6 months

3
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2010