September 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2649) NoClassDefFoundError when trying to run adminshell

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2649?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2649: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1004770|https://bugzilla.redhat.com/show_bug.cgi?id=1004770] from ASSIGNED to MODIFIED > NoClassDefFoundError when trying to run adminshell > -------------------------------------------------- > > Key: TEIID-2649 > URL: https://issues.jboss.org/browse/TEIID-2649 > Project: Teiid > Issue Type: Bug > Components: Tools > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Blocker > > adminshell is throwing the following exception when trying to be run: > Exception in thread "main" java.lang.NoClassDefFoundError: jline/History > at java.lang.Class.getDeclaredMethods0(Native Method) > at java.lang.Class.privateGetDeclaredMethods(Class.java:2521) > at java.lang.Class.getDeclaredMethods(Class.java:1845) > at org.codehaus.groovy.reflection.CachedClass$3$1.run(CachedClass.java:83) > at java.security.AccessController.doPrivileged(Native Method) > at org.codehaus.groovy.reflection.CachedClass$3.initValue(CachedClass.java:80) > at org.codehaus.groovy.reflection.CachedClass$3.initValue(CachedClass.java:78) > at org.codehaus.groovy.util.LazyReference.getLocked(LazyReference.java:46) > at org.codehaus.groovy.util.LazyReference.get(LazyReference.java:33) > at org.codehaus.groovy.reflection.CachedClass.getMethods(CachedClass.java:249) > at groovy.lang.MetaClassImpl.populateMethods(MetaClassImpl.java:341) > at groovy.lang.MetaClassImpl.fillMethodIndeMetaClassImpl.java:291) > at groovy.lang.MetaClassImpl.initialize(MetaClassImpl.java:2912) > at org.codehaus.groovy.reflection.ClassInfo.getMetaClassUnderLock(ClassInfo.java:166) > at org.codehaus.groovy.reflection.ClassInfo.getMetaClass(ClassInfo.java:182) > at org.codehaus.groovy.runtime.metaclass.MetaClassRegistryImpl.getMetaClass(MetaClassRegistryImpl.java:210) > at org.codehaus.groovy.runtime.InvokerHelper.getMetaClass(InvokerHelper.java:701) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.createCallConstructorSite(CallSiteArray.java:69) > at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:52) > at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:192) > at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:200) > at org.codehaus.groovy.tools.shell.Main.main(Main.groovy:124) > at org.teiid.adminshell.GroovyAdminShell.main(GroovyAdminShell.java:30) > Caused by: java.lang.ClassNotFoundException: jline.History > at java.net.URLClassLoader$1.run(URLClassLoader.java:366) > at java.net.URLClassLoader$1.run(URLClassLoader.java:355) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:354) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > ... 23 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2652) Dependencies set on OLAP translator's module.xml are incomplete

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2652?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2652: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1004892|https://bugzilla.redhat.com/show_bug.cgi?id=1004892] from ASSIGNED to MODIFIED > Dependencies set on OLAP translator's module.xml are incomplete > --------------------------------------------------------------- > > Key: TEIID-2652 > URL: https://issues.jboss.org/browse/TEIID-2652 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: CR2 > Fix For: 8.4.1, 8.5 > > > The OLAP translator is missing dependency on OLAP4J library -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2650) A jboss server in domain mode does not advertise its teiid runtime-version

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2650?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2650: ------------------------------------- Based on the above comment can this be marked as resolved? > A jboss server in domain mode does not advertise its teiid runtime-version > -------------------------------------------------------------------------- > > Key: TEIID-2650 > URL: https://issues.jboss.org/browse/TEIID-2650 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4 > Reporter: Paul Richardson > Assignee: Ramesh Reddy > Priority: Blocker > Fix For: 8.4.1, 8.5 > > > A standalone jboss server installed with teiid advertises its teiid runtime version at the path /subsystem=teiid/runtime-version. > Likewise, a domain jboss server installed with teiid in the 'ha' profile should advertise its runtime version at the path /profile=ha/subsystem=teiid/runtime-version. > However, whereas the standalone returns the correct value for this attribute, the domain mode server fails, only returning 'undefined'. > This attribute is essential to designer in determining what version is the teiid instance. This in turns determines the functionality of the modelling that is available and which teiid client should be used for connection. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2652) Dependencies set on OLAP translator's module.xml are incomplete

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2652?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2652. --------------------------------- Labels: CR2 (was: ) Resolution: Done 1) Updated OLAP4J to 1.1.0 version 2) Included the olap4j-1.1.0.jar, olap4j-xmla-1.1.0.jar in the kit, added a module for it 3) Updated the olap datasource documentation space with edits for datasource creation files and readme 4) Provided instructions for Mondrian only setup where a sample module directory with out the jars. 5) Provided a sample dynamic vdb that uses XMLA protocol 6) Tested connectivity with XMLA and Mondrian direct with the sample VDB and validated that the query also works with Mondrian's FoodMart sample database. > Dependencies set on OLAP translator's module.xml are incomplete > --------------------------------------------------------------- > > Key: TEIID-2652 > URL: https://issues.jboss.org/browse/TEIID-2652 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: CR2 > Fix For: 8.4.1, 8.5 > > > The OLAP translator is missing dependency on OLAP4J library -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2644) Support retrieving result sets from any out parameter

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2644?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2644: --------------------------------------- An overview of what works and doesn't work currently: Working: An oracle stored function returning a ref cursor as the result set An oracle stored function returning a table type, but it looks to using the native-query form of SELECT * FROM TABLE(func(params...)) - we could also look at generating this form of the sql as the native-query logic is not yet good for handling vararg procedrues. Not working: An oracle stored procedure/function with an out parameter ref cursor as the result set (the driver for this issue). A stored procedure with an out parameter of a table type as the result set. A stored procedure with an expression as a parameter value (from the associated forum posting). Usability issue abound though with ref cursors in general as they are untyped. All the import logic will see when used as an out parameter is a column typed as OTHER. > Support retrieving result sets from any out parameter > ----------------------------------------------------- > > Key: TEIID-2644 > URL: https://issues.jboss.org/browse/TEIID-2644 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.6 > > > Currently Teiid expects the driver (for example DataDirect) or in case of oracle the return parameter to be result set. In scenarios were a wrapping stored function cannot be created we should also offer support for retrieving any out parameter as the result set. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-586) Like pushdown handling

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-586?page=com.atlassian.jira.plugin.... ] Steven Hawkins commented on TEIID-586: -------------------------------------- I may defer this until it is hit as an issue, and just add a KI with the workaround to specify SIMILAR or a REGEX LIKE which would not be supported by the source (although for performance you would want partial matching pushed down as mentioned in the description). Another option would be to disable the like support by default for ldap and salesforce and add a pushdown function to represent the native like handling - e.g. ldap.match(col, 'a*b') Generally speaking there we have an issue with any string comparison including like on any database when the column is using an alternative collation (including ones that are case insensitive) - as the results may not match Teiid's. As our metadata system is too rigid/class based, we'd have to introduce a different value holder for strings that included the collation. > Like pushdown handling > ---------------------- > > Key: TEIID-586 > URL: https://issues.jboss.org/browse/TEIID-586 > Project: Teiid > Issue Type: Bug > Components: LDAP Connector, Query Engine, Salesforce Connector > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.6 > > > Both salesforce and ldap like semantics are not the same as SQL. We could capture this with more capabilities supportsLikeCaseSensitive and supportsLikeWildcardSingleCharacter repectively, or another approach would be to allow the connector to generically indicate partial support and have the query engine both push down the conjunct and leave a copy to be applied after the query. With either explicit supports or generic partial support it would only applicable to top level where clause conjuncts. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2558) Add translator support for dependent join pushdown

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2558?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2558. ----------------------------------- Resolution: Done Marking as done for 8.5. Depending upon stakeholder feedback we'll need to expand the hint and the options supported at the translator level. > Add translator support for dependent join pushdown > -------------------------------------------------- > > Key: TEIID-2558 > URL: https://issues.jboss.org/browse/TEIID-2558 > Project: Teiid > Issue Type: Sub-task > Components: Connector API > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.5 > > > JDBC translators should offer built-in support for dependent join pushdown - possibly with index creation and other options. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2559) Add additional make dep hint options

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2559?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2559. ----------------------------------- Resolution: Done Marking as done for 8.5. Depending upon stakeholder feedback we'll need to expand the hint and the options supported at the translator level. > Add additional make dep hint options > ------------------------------------ > > Key: TEIID-2559 > URL: https://issues.jboss.org/browse/TEIID-2559 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.5 > > > make dep hints should support additional options to facilitate TEIID-2249. This includes: > min - the minimum number of rows to trigger a dependent join full pushdown > max - the maximum number of rows allowed before rejecting the dependent join (this would apply in both full pushdown and partial non-pushdown scenarios - in the latter though it will likely refer to the number of distinct values) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-247) Add support for array types

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-247?page=com.atlassian.jira.plugin.... ] Steven Hawkins resolved TEIID-247. ---------------------------------- Resolution: Done Marking as resolved for 8.5. Will open new issues as needed as described in the previous comment. > Add support for array types > --------------------------- > > Key: TEIID-247 > URL: https://issues.jboss.org/browse/TEIID-247 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, JDBC Driver, Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.5 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Add language support for array types. Push down and client support should also be added. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2653) Add capability to force quotes around the column names containing spaces in "Name in Source" property.

by Van Halbert (JIRA)

Van Halbert created TEIID-2653: ---------------------------------- Summary: Add capability to force quotes around the column names containing spaces in "Name in Source" property. Key: TEIID-2653 URL: https://issues.jboss.org/browse/TEIID-2653 Project: Teiid Issue Type: Enhancement Components: Server Affects Versions: 7.7.7 Reporter: Van Halbert Assignee: Steven Hawkins Add capability to force quotes around the column names containing spaces in "Name in Source" property. The same as tablenames with spaces quote the "Name in Source" property. >From the table editor you can put quotes around the columns but it is very time consuming. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues September 2013