April 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Commented: (TEIID-105) MySQL capabilities should be made specific to version 4/5

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-105?page=com.atlassian.jira.plug... ] Ramesh Reddy commented on TEIID-105: ------------------------------------ is this valid any more? > MySQL capabilities should be made specific to version 4/5 > --------------------------------------------------------- > > Key: TEIID-105 > URL: https://jira.jboss.org/jira/browse/TEIID-105 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 6.x > Reporter: Steven Hawkins > Fix For: 6.1.0 > > > Defect Tracker #24746: The current mysql capabilities seem to have been written for version 5 (it initially included support for timestampdiff). The support for 4.x should be specifically refined or specifically removed from the docs. 4.x goes completely eol by the end of 2009, so it's unlikely many customers would care if this were done for 5.5.1. > see also http://www.mysql.com/company/legal/lifecycle/#calendar -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIID-233) Server should support JGroups communication over P2P

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-233?page=com.atlassian.jira.plug... ] Ramesh Reddy reassigned TEIID-233: ---------------------------------- Assignee: Ramesh Reddy > Server should support JGroups communication over P2P > ---------------------------------------------------- > > Key: TEIID-233 > URL: https://jira.jboss.org/jira/browse/TEIID-233 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 6.0.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 6.1.0 > > > Currently Server only supports the JGroups over Multicast we need to support unicast protocol tool, with configuration. -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIID-128) Consider replacing homegrown XML-Relational doc cache implementation with JBoss Cache or other standard implementation

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-128?page=com.atlassian.jira.plug... ] Ramesh Reddy reassigned TEIID-128: ---------------------------------- Assignee: John Doyle > Consider replacing homegrown XML-Relational doc cache implementation with JBoss Cache or other standard implementation > ---------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-128 > URL: https://jira.jboss.org/jira/browse/TEIID-128 > Project: Teiid > Issue Type: Quality Risk > Components: XML Connector > Affects Versions: 6.x > Reporter: Greg Haber > Assignee: John Doyle > Priority: Minor > Fix For: 6.1.0 > > > My understanding is that the document cache implementation in the XML-Relational connector is a homegrown implementation. Homegrown = more code to maintain and better chance of us hitting major issues like JBEDSP-834. Plus AFAIK this homegrown cache implementation locks the whole cache even on read operations which I suspect is going to introduce scaling problems (in fact I think we actually experienced this at a customer with 5.0SP2 but we were unable to conclusively determine that that was the cause of problems we saw then). -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-379) MySQL connector assumes that database is running in ANSI mode rather than the default mode

by Greg Haber (JIRA)

MySQL connector assumes that database is running in ANSI mode rather than the default mode ------------------------------------------------------------------------------------------ Key: TEIID-379 URL: https://jira.jboss.org/jira/browse/TEIID-379 Project: Teiid Issue Type: Bug Components: JDBC Connector Environment: Teiid trunk as of 2/23/09 at 3:22 PM eastern Reporter: Greg Haber Assignee: Steven Hawkins I noticed with the legacy MetaMatrix product that our MySQL connector seems to assume that it is connecting to a MySQL database running in "ANSI" SQL mode For instance, we list in the capabilities class that MySQL supports || as a string concatenation parameter, but it actually only supports it if the SQL mode "PIPES_AS_CONCAT" is set - and this is one of the individual modes that gets set when you set the "ANSI" meta-mode (see http://dev.mysql.com/doc/refman/5.0/en/server-sql-mode.html#sqlmode_ansi for details). This is a bad assumption as it is not the default setting for MySQL (the default sql-mode setting is "", or no special modes). I took a look at some of the databases used at Red Hat for testing MetaMatrix for MySQL (specifically, slntds03) and noticed that they have sql-mode set to ANSI on the server side. I took a look at the current Teiid trunk code and it is the same as the legacy MetaMatrix code in this regard, so Teiid has the same issue. Two possible resolutions are: -Rework the connector to remove any assumptions that sql-mode=ANSI -set sql-mode to ANSI when establishing new connections to MySQL (this can be done by sending the SQL statement 'set SESSION sql-mode="ANSI" after establishing a connection). Unfortunately there does not appear to be a way to set this mode via a JDBC connection property - you need to send the "set" command after establishing the connection. -- 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

15 years, 9 months

2
6
0 / 0

[JBoss JIRA] Created: (TEIID-488) XML Plugin reporting/bundling the incorrect entries

by Ramesh Reddy (JIRA)

XML Plugin reporting/bundling the incorrect entries --------------------------------------------------- Key: TEIID-488 URL: https://jira.jboss.org/jira/browse/TEIID-488 Project: Teiid Issue Type: Bug Components: XML Connector Affects Versions: 6.0.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.1.0 1. Changed all "ConnectorTypeClassPath" properties to be hidden 2. Changed all "connector-*.6.0.0" references to be "connector-*-6.0.0 (notice the first dot now is a dash) 3. Removed "Default Value=..." for all "ConnectorClassPath" properties I believe we had talked about 1 & 3. Barry had told me about the JAR name changes. I noticed following JARs are not in your "extensions" directory yet are referenced by multiple "ConnectorTypeClassPath" property values: 1. axis-jaxrpc-1.3.jar (this used to be in extensions dir) 2. wsdl4j-1.5.1.jar (this used to be in extensions dir) 3. xml-apis-1.0.b2.jar Can references to these be removed from the configuration.xml file? -- 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

15 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (TEIID-510) Server was failing to start because non-existing properties needed to be removed from the QueryService initialization

by Van Halbert (JIRA)

Server was failing to start because non-existing properties needed to be removed from the QueryService initialization --------------------------------------------------------------------------------------------------------------------- Key: TEIID-510 URL: https://jira.jboss.org/jira/browse/TEIID-510 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 6.2.0 Reporter: Van Halbert Assignee: Van Halbert The QueryService would fail at startup because of references to 2 properties that are no longer used. Also, in this change, the property references in QueryServicePropertyNames will be changed to reference the statics in DQPConfigSource. -- 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

15 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-505) Do not parse the URL, when creating a Data Source or XA DataSource

by Ramesh Reddy (JIRA)

Do not parse the URL, when creating a Data Source or XA DataSource ------------------------------------------------------------------ Key: TEIID-505 URL: https://jira.jboss.org/jira/browse/TEIID-505 Project: Teiid Issue Type: Task Affects Versions: 6.0.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.1.0 Previously Teiid always dependent upon the Data Direct drivers, which were provided in a unified URL across all the RDBMS, so that Teiid could parse the given URL and extract serverName, databaseName, portNumber etc. However, now in order to support with native vendor drivers this assumption is no longer valid. Teiid can not assume the format of these URL, so there should be no attempt made to parse these URLs to extract above properties, rather if the URL specified it should be supplied to the Data Source as like any other property. This requires code change. - All the Data Direct XA Connector Types needs to be modified, so that do not depend on the URL property alone - All vendor XA data sources need to be checked to make sure they all work. -- 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

15 years, 9 months

1
2
0 / 0

[JBoss JIRA] Resolved: (TEIID-398) mmadmin: exportDataRoles gives NPE if no roles present for VDB - Should throw better exception.

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-398?page=com.atlassian.jira.plug... ] Ramesh Reddy resolved TEIID-398. -------------------------------- Resolution: Done All the methods that use the ObjectConverterUtil have been checked to make sure they only send valid contents as parameters, if not they will throw an exception showing that an error has occurred. > mmadmin: exportDataRoles gives NPE if no roles present for VDB - Should throw better exception. > ----------------------------------------------------------------------------------------------- > > Key: TEIID-398 > URL: https://jira.jboss.org/jira/browse/TEIID-398 > Project: Teiid > Issue Type: Bug > Components: Tools > Affects Versions: 6.0.0 > Environment: fedora 10 running 5.5.2GA > Reporter: Paul Nittel > Assignee: Ramesh Reddy > Priority: Minor > Fix For: 6.1.0 > > > While creating mmadmin tests for NIAP, I found that attempting to export roles from a VDB with no data roles, got an NPE. It should be getting a more meaningful exception. > exportDataRoles("NiapWebVdb","2","/home/pnittel/mmx/552niap/TestMmadmin/testroles.xml"); > // Error: // Uncaught Exception: Method Invocation ObjectConverterUtil.write : at Line: 600 : in file: URL: jar:file:/home/pnittel/mmx/552niap/tools/lib/mmadmin.jar!/scripts/serveradmin.bsh : ObjectConverterUtil .write ( currentContext ( ) .internalAdmin .exportDataRoles ( vdbName , vdbVersion ) , filename ) > Called from method: exportDataRoles : at Line: 1 : in file: <unknown file> : exportDataRoles ( "NiapWebVdb" , "2" , "/home/pnittel/mmx/552niap/TestMmadmin/testroles.xml" ) > Target exception: java.lang.NullPointerException > java.lang.NullPointerException > at com.metamatrix.core.util.ObjectConverterUtil.write(ObjectConverterUtil.java:121) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at bsh.Reflect.invokeMethod(Unknown Source) > at bsh.Reflect.invokeStaticMethod(Unknown Source) > at bsh.Name.invokeMethod(Unknown Source) > at bsh.BSHMethodInvocation.eval(Unknown Source) > at bsh.BSHPrimaryExpression.eval(Unknown Source) > at bsh.BSHPrimaryExpression.eval(Unknown Source) > at bsh.BSHBlock.evalBlock(Unknown Source) > at bsh.BSHBlock.eval(Unknown Source) > at bsh.BshMethod.invokeImpl(Unknown Source) > at bsh.BshMethod.invoke(Unknown Source) > at bsh.BshMethod.invoke(Unknown Source) > at bsh.Name.invokeLocalMethod(Unknown Source) > at bsh.Name.invokeMethod(Unknown Source) > at bsh.BSHMethodInvocation.eval(Unknown Source) > at bsh.BSHPrimaryExpression.eval(Unknown Source) > at bsh.BSHPrimaryExpression.eval(Unknown Source) > at bsh.Interpreter.run(Unknown Source) > at com.metamatrix.script.shell.MMAdmin.main(MMAdmin.java:50) -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-224) mmadmin tool has many usability issues

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-224?page=com.atlassian.jira.plug... ] Ramesh Reddy resolved TEIID-224. -------------------------------- Resolution: Partially Completed > mmadmin tool has many usability issues > -------------------------------------- > > Key: TEIID-224 > URL: https://jira.jboss.org/jira/browse/TEIID-224 > Project: Teiid > Issue Type: Feature Request > Components: Tools > Affects Versions: 6.0.0 > Environment: Linux > Reporter: Johnny Verhaeg > Assignee: Ramesh Reddy > Fix For: 6.1.0 > > > 1) The script doesn't even run without first editing the script source itself, reading its initial comment, and performing an export for a variable that points to a folder containing the JDBC libraries. The script should have just prompted me for this, or possibly just run mmtoolsenv from the Console's installation folder. > 2) I couldn't figure out how to either get help or even quit the program. Turns out you have to enter everything like it's a function, with trailing parentheses and a semicolon. If we're going to require trailing anything, we should at least indicate that after the next prompt when the user hits enter. How hard can it possibly be to have BeanShell recognize simple commands like help and exit without requiring the function-like syntax? > 3) Many of the commands you enter are very long, but there is no way to retrieve (such as hitting the up arrow) and edit/use previous commands. > 4) You can't edit commands using the left arrow. If I'm typing a long command, then realize that I made a type near the beginning of the command, all I can do is backspace over everything I typed and reenter it from the typo. > 5) When I enter a query that fails, I don't get back any of the information that might clue me in as to why it failed. My only option is to access the logs that reside on the server. -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Commented: (TEIID-224) mmadmin tool has many usability issues

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-224?page=com.atlassian.jira.plug... ] Ramesh Reddy commented on TEIID-224: ------------------------------------ Except for Item#4 all other issues are now fixed. As Steve indicated BeanShell does come with Graphical Environment editor, which does provide somewhat better editing capabilities. This can be enabled by supplying "-Dgui=true" property in the AdminShell script. However, we did not make this as the default option to cut down on support issues with this environment. I would encourage admin shell users to use this and provide feed back, then we can decide to support this as the default mode for "interactive" shell. > mmadmin tool has many usability issues > -------------------------------------- > > Key: TEIID-224 > URL: https://jira.jboss.org/jira/browse/TEIID-224 > Project: Teiid > Issue Type: Feature Request > Components: Tools > Affects Versions: 6.0.0 > Environment: Linux > Reporter: Johnny Verhaeg > Assignee: Ramesh Reddy > Fix For: 6.1.0 > > > 1) The script doesn't even run without first editing the script source itself, reading its initial comment, and performing an export for a variable that points to a folder containing the JDBC libraries. The script should have just prompted me for this, or possibly just run mmtoolsenv from the Console's installation folder. > 2) I couldn't figure out how to either get help or even quit the program. Turns out you have to enter everything like it's a function, with trailing parentheses and a semicolon. If we're going to require trailing anything, we should at least indicate that after the next prompt when the user hits enter. How hard can it possibly be to have BeanShell recognize simple commands like help and exit without requiring the function-like syntax? > 3) Many of the commands you enter are very long, but there is no way to retrieve (such as hitting the up arrow) and edit/use previous commands. > 4) You can't edit commands using the left arrow. If I'm typing a long command, then realize that I made a type near the beginning of the command, all I can do is backspace over everything I typed and reenter it from the typo. > 5) When I enter a query that fails, I don't get back any of the information that might clue me in as to why it failed. My only option is to access the logs that reside on the server. -- 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

15 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2009