March 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Moved: (TEIID-399) Oracle Spatial SQL translator drops the LIMIT clause.

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-399?page=com.atlassian.jira.plug... ] Steven Hawkins moved JBEDSP-966 to TEIID-399: --------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-399 (was: JBEDSP-966) Component/s: Misc. Connectors (was: Connectors) Affects Version/s: 6.0.0 (was: 5.5.2) (was: 5.5.3) (was: 5.5.1) > Oracle Spatial SQL translator drops the LIMIT clause. > ----------------------------------------------------- > > Key: TEIID-399 > URL: https://jira.jboss.org/jira/browse/TEIID-399 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 6.0.0 > Reporter: John Doyle > Assignee: John Doyle > > The LIMIT SQL clause is not having an effect on our SQL queries. In our case, we are using the Oracle Spatial connector which interfaces with an Oracle 10g database. What configuration or connector changes are needed so we can leverage the LIMIT clause for controlling the fetch size of our result sets which are derived from Oracle? > I am running the following query: > SELECT SEQ_NUM > FROM IBSBINO_Physical.IBSBINO > LIMIT 5 > I expect to get back 5 rows of data, but get back the entire table > instead. -- 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] Updated: (TEIID-156) Console should allow for setting arbitrary propeties

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-156?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-156: ------------------------------- Affects Version/s: 6.2.0 (was: 6.0.0) > Console should allow for setting arbitrary propeties > ---------------------------------------------------- > > Key: TEIID-156 > URL: https://jira.jboss.org/jira/browse/TEIID-156 > Project: Teiid > Issue Type: Feature Request > Components: Console > Affects Versions: 6.2.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 6.1.0 > > > It would be especially useful for custom connectors, or even our own connectors with mid release enhancements, to allow the console to set arbitrary properties rather than requiring hand modification of the config. -- 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] Updated: (TEIID-323) PSC nomenclature is underused and confusing and complex

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-323?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-323: ------------------------------- Fix Version/s: 6.2.0 (was: 6.1.0) > 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.0.0 > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Priority: Minor > Fix For: 6.2.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, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-243) Add the ability to support vararg functions

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-243?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-243: --------------------------------- Fix Version/s: 6.2.0 (was: 6.1.0) > Add the ability to support vararg functions > ------------------------------------------- > > Key: TEIID-243 > URL: https://jira.jboss.org/jira/browse/TEIID-243 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 6.2.0 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > It would be good to add resolving/metadata support for vararg functions. For example coalesce is a vararg function, and in general UDFs would benefit from utilizing varargs. -- 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-345) Consolidate ifnull, nvl, and coalesce support

by Steven Hawkins (JIRA)

Consolidate ifnull, nvl, and coalesce support --------------------------------------------- Key: TEIID-345 URL: https://jira.jboss.org/jira/browse/TEIID-345 Project: Teiid Issue Type: Feature Request Components: Connector API, Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.1.0 We should use ifnull to represent the 2 arg function form and coalesce to represent the n arg (not available until var arg support). The rewriter should rewrite nvl as ifnull and connectors should express support for ifnull and coalesce only. -- 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] Closed: (TEIID-184) Add support for coalesce and nullif

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-184?page=com.atlassian.jira.plug... ] Steven Hawkins closed TEIID-184. -------------------------------- This has been added to the documentation, but full vararg coalesce is not yet supported. > Add support for coalesce and nullif > ----------------------------------- > > Key: TEIID-184 > URL: https://jira.jboss.org/jira/browse/TEIID-184 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.0.0 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Coalesce and nullif are SQL standard functions that can be implemented in the rewriter as case functions. -- 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-195) JDBC Connector type should make "Password" property optional

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-195?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-195. ---------------------------------- Fix Version/s: 6.0.0 (was: 6.1.0) Resolution: Done The JDBC connector as part of the connector refactoring no longer requires a username or password - except if a credential map is being used. > JDBC Connector type should make "Password" property optional > ------------------------------------------------------------ > > Key: TEIID-195 > URL: https://jira.jboss.org/jira/browse/TEIID-195 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Connector > Affects Versions: 6.0.0 > Reporter: Van Halbert > Priority: Minor > Fix For: 6.0.0 > > > The "username" and "password" properties of the JDBC connector binding should allow for null values. Some databases allow null passwords (and even null usernames). > Currently, Designer won't allow you to execute a VDB if password is blank. -- 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-38) supported non-deterministic functions are evaluated prior to push-down

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-38?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-38. --------------------------------- Resolution: Won't Fix Our approach to non-deterministic functions is not common among vendors. Preventing further push-down seems to be the wrong thing to do. We should simply live for now with the possibility that a non-deterministic push down may not yield the same result had it not been pushed down. > supported non-deterministic functions are evaluated prior to push-down > ---------------------------------------------------------------------- > > Key: TEIID-38 > URL: https://jira.jboss.org/jira/browse/TEIID-38 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.x > Reporter: Steven Hawkins > Priority: Optional > Fix For: 6.1.0 > > > Defect Tracker #24735: We currently will not actually push down non-deterministic functions even if they are supported, since the evaluateexpressionvisitor will replace them with constant values. For example rand will be pre-evaluated before being sent to sqlserver (however sqlserver does not correctly support non-deterministic functions anyway). We may need to actually not support non-deterministic functions in sqlserver or other sources that do not handle them properly. -- 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] Moved: (TEIID-398) mmadmin: exportDataRoles gives NPE if no roles present for VDB - Should throw better exception.

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-398?page=com.atlassian.jira.plug... ] Steven Hawkins moved JBEDSP-992 to TEIID-398: --------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-398 (was: JBEDSP-992) Component/s: Tools (was: Tools) Fix Version/s: 6.1.0 (was: 5.5.3 CCE) Affects Version/s: 6.0.0 (was: 5.5.2) > 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: Steven Hawkins > 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] Moved: (TEIID-397) Console Error after changing Root Admin password

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-397?page=com.atlassian.jira.plug... ] Steven Hawkins moved JBEDSP-987 to TEIID-397: --------------------------------------------- Project: Teiid (was: JBoss Enterprise Data Services Platform) Key: TEIID-397 (was: JBEDSP-987) Component/s: Console (was: Console) Fix Version/s: 6.1.0 (was: 5.5.3 CCE) Affects Version/s: 6.0.0 (was: 5.5.2) > Console Error after changing Root Admin password > ------------------------------------------------ > > Key: TEIID-397 > URL: https://jira.jboss.org/jira/browse/TEIID-397 > Project: Teiid > Issue Type: Bug > Components: Console > Affects Versions: 6.0.0 > Environment: Windows client running against Windows Server > Reporter: Warren Gibson > Fix For: 6.1.0 > > > 1. Went into Security/Summary and changed MetaMatrixAdmin password. > 2. Bounced the server. > 3. Console hung for about 10 minutes and finally returned with the below Error message. > 4. Console was unstable. > 5. Shut down Console and Restarted and everything seemed to be fine with the new password. > com.metamatrix.console.util.ExternalException[0]: com.metamatrix.api.exception.ComponentCommunicationException[0]: com.metamatrix.common.comm.exception.ConnectionException[0]: com.metamatrix.api.exception.security.LogonException[0]: [MetaMatrixAuthenticationException]The username "metamatrixadmin" and/or password and/or payload token could not be authenticated by any membership domain. > at com.metamatrix.platform.security.session.service.SessionServiceImpl.authenticateUser(SessionServiceImpl.java:431) > at com.metamatrix.platform.security.session.service.SessionServiceImpl.createSession(SessionServiceImpl.java:624) > at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at com.metamatrix.platform.service.proxy.SingleInvokationProxy.invoke(SingleInvokationProxy.java:48) > at $Proxy7.createSession(Unknown Source) > at com.metamatrix.platform.security.session.service.LogonHelper.logon(LogonHelper.java:69) > at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at com.metamatrix.platform.service.proxy.ProxyManager$WrappedDelegator.invoke(ProxyManager.java:41) > at $Proxy8.logon(Unknown Source) > at com.metamatrix.common.comm.platform.socket.SocketLogon.logon(SocketLogon.java:133) > at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at com.metamatrix.core.proxy.ServiceInvocation.invokeOn(ServiceInvocation.java:91) > at com.metamatrix.core.proxy.DefaultTerminalServiceInterceptor.invoke(DefaultTerminalServiceInterceptor.java:29) > at com.metamatrix.core.proxy.ServiceInvocation.invokeNext(ServiceInvocation.java:87) > at com.metamatrix.common.comm.platform.server.MessageServiceAgent.receiveLocal(MessageServiceAgent.java:90) > at com.metamatrix.common.comm.platform.server.MessageServiceAgent.receive(MessageServiceAgent.java:114) > at com.metamatrix.common.comm.platform.server.MessageFilterServiceAgent.receive(MessageFilterServiceAgent.java:99) > at com.metamatrix.platform.admin.apiimpl.RuntimeStateListenerAgent.receive(RuntimeStateListenerAgent.java:103) > at com.metamatrix.common.comm.platform.socket.SocketVMController.receive(SocketVMController.java:388) > at com.metamatrix.common.comm.platform.socket.server.ServerSynchronousWorkItem.process(ServerSynchronousWorkItem.java:36) > at com.metamatrix.common.comm.platform.socket.server.SocketServerWorker.process(SocketServerWorker.java:35) > at com.metamatrix.common.queue.QueueWorker.run(QueueWorker.java:64) -- 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2009