April 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Resolved: (TEIID-157) mmadmin - Add a short start-up help text for users

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-157?page=com.atlassian.jira.plug... ] Ramesh Reddy resolved TEIID-157. -------------------------------- Resolution: Done In the Westport this is not packaged as the separate kit, so the editing for the SERVER_CLIENT jar is no longer necessary. Also, if we do support a separate kit, it will include the client jar with the kit as the client jar is no longer huge. > mmadmin - Add a short start-up help text for users > -------------------------------------------------- > > Key: TEIID-157 > URL: https://jira.jboss.org/jira/browse/TEIID-157 > Project: Teiid > Issue Type: Feature Request > Components: Tools > Affects Versions: 6.1.0 > Environment: All > Reporter: Paul Nittel > Assignee: Ramesh Reddy > Fix For: 6.1.0 > > > After watching John Verhaeg struggle with his initial use of mmadmin, it seems a short paragraph shouuld be displayed when mmadmin is executed. This could explain how to get help, basic usage, etc. > Also, if JAVA_HOME and/or SERVER_CLIENT aren't defined, is it possible for the startup to request this info, rather than asking the user to edit mmadmin? > We'd like this tool to live on, but it needs to be more user friendly. > PS: At no time did we actually enjoy laughing at John while he struggled, but it was kinda humorous. Seriously. Honest. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Assigned: (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 reassigned TEIID-398: ---------------------------------- Assignee: Ramesh Reddy > 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, 2 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-230) Add Reading the Command line parameter support for mmadmin

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-230?page=com.atlassian.jira.plug... ] Ramesh Reddy resolved TEIID-230. -------------------------------- Resolution: Done In the admin shell, when executing in the "script mode" you can pass in parameters from the command line, and they can be accessed in your script by "bsh.args" value. For example if this below line executed mmadmin myscript.bsh param1 param2 param3 then inside the myscript.bsh file, the script developer can access the parameters as for(String arg:bsh.args) { print(arg); } > Add Reading the Command line parameter support for mmadmin > ---------------------------------------------------------- > > Key: TEIID-230 > URL: https://jira.jboss.org/jira/browse/TEIID-230 > Project: Teiid > Issue Type: Feature Request > Components: Tools > Affects Versions: 6.0.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Minor > Fix For: 6.1.0 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Currently there is no way to pass in command line parameters to the MMAdmin while executing a script other than script name it self. You could add "-D" parameter through script manipulation, however there is no easier way. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIID-81) Cached plans are too big - can cause out of memory errors

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-81?page=com.atlassian.jira.plugi... ] Steven Hawkins reassigned TEIID-81: ----------------------------------- Assignee: Steven Hawkins > Cached plans are too big - can cause out of memory errors > --------------------------------------------------------- > > Key: TEIID-81 > URL: https://jira.jboss.org/jira/browse/TEIID-81 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.x > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.1.0 > > > Defect Tracker #12381: Running the coper load tests led to this conclusion: > Each cached plan takes on average 31 KB of memory. > At 140 unique queries / connection and 128 connection this requires over 550 MB of memory just for the plan cache. > Half of the memory was consumed by char[]. Over 10% of the memory was used by ElementSymbol objects. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Work started: (TEIID-81) Cached plans are too big - can cause out of memory errors

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-81?page=com.atlassian.jira.plugi... ] Work on TEIID-81 started by Steven Hawkins. > Cached plans are too big - can cause out of memory errors > --------------------------------------------------------- > > Key: TEIID-81 > URL: https://jira.jboss.org/jira/browse/TEIID-81 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.x > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.1.0 > > > Defect Tracker #12381: Running the coper load tests led to this conclusion: > Each cached plan takes on average 31 KB of memory. > At 140 unique queries / connection and 128 connection this requires over 550 MB of memory just for the plan cache. > Half of the memory was consumed by char[]. Over 10% of the memory was used by ElementSymbol objects. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-508) Change the handling of dependentsets and subquery values

by Steven Hawkins (JIRA)

Change the handling of dependentsets and subquery values -------------------------------------------------------- Key: TEIID-508 URL: https://jira.jboss.org/jira/browse/TEIID-508 Project: Teiid Issue Type: Task Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.1.1 Related to the reference handling, subquery values and dependent sets should be evaluated through the command context rather than having values set on them directly. -- 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, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-507) DependentCriteriaProcessor issues

by Steven Hawkins (JIRA)

DependentCriteriaProcessor issues --------------------------------- Key: TEIID-507 URL: https://jira.jboss.org/jira/browse/TEIID-507 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.1.0 The DependentCriteriaProcessor needs to check if setcriteria is negated and needs to preevaluate the values in the set criteria. -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (TEIID-427) Access file error exception when RuntimeIndexSelector trying to load indexes from zip file

by Salvatore Incandela (JIRA)

Access file error exception when RuntimeIndexSelector trying to load indexes from zip file ------------------------------------------------------------------------------------------ Key: TEIID-427 URL: https://jira.jboss.org/jira/browse/TEIID-427 Project: Teiid Issue Type: Bug Affects Versions: 6.0.0 Environment: Ubuntu 8.10, Eclipse 3.4.2, Java 1.6.0.12 Reporter: Salvatore Incandela Assignee: Steven Hawkins loadIndexesFromZipFile() method extract folders as file, during the unzip process, this cause an access file error, because the directories will included into the array indexes. [code] File entryFile = new File(getIndexDirectoryPath(), entry.getName()); FileUtils.write(zipInputStream, entryFile, length); if (SimpleIndexUtil.indexFileExists(entryFile)) { tmp.add(new Index(entryFile.getAbsolutePath(), true)); } [/code] I tried a this solution, it seems to work: [code] File entryFile = new File(getIndexDirectoryPath(), entry.getName()); if (entry.isDirectory()) { entryFile.mkdir(); } else { FileUtils.write(zipInputStream, entryFile, length); } if (SimpleIndexUtil.indexFileExists(entryFile)) { tmp.add(new Index(entryFile.getAbsolutePath(), true)); } [/code] In this case the indexFileExist() excludes all the directories, form the array indexes. -- 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, 2 months

2
11
0 / 0

[JBoss JIRA] Created: (TEIID-506) Remove JGroups dependency from common internal

by Steven Hawkins (JIRA)

Remove JGroups dependency from common internal ---------------------------------------------- Key: TEIID-506 URL: https://jira.jboss.org/jira/browse/TEIID-506 Project: Teiid Issue Type: Task Components: Common Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.1.0 -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Resolved: (TEIID-323) PSC nomenclature is underused and confusing and complex

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-323?page=com.atlassian.jira.plug... ] Van Halbert resolved TEIID-323. ------------------------------- Resolution: Done branch remove_psc was created, coded, reviewed (by many) checked in and merged back into trunk. > PSC nomenclature is underused and confusing and complex > ------------------------------------------------------- > > Key: TEIID-323 > URL: https://jira.jboss.org/jira/browse/TEIID-323 > Project: Teiid > Issue Type: Task > Components: Console, Server > Affects Versions: 6.1.0 > Reporter: Ramesh Reddy > Assignee: Van Halbert > Priority: Minor > Fix For: 6.1.0 > > > Currently there is possibility in the configuration to bundle multiple services under some thing called PSC which is a grouping of the services. This feature is introduces lot of unnecessary complexity in the code, and using the Console with these confusing. > . > If you ever navigated between "MetaMatrixFullServer" and "QueryServer" and "ODBCServer" and/or configuring the connectors for those you know the pain. > The original intent was to move a bundle of connectors from one server to another. Now a days connectors are always bundled with their VDBs. We can reduce this complexity in code and UI. > Suggestions are welcome how we can reduce this clutter. -- 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, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2009