September 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2664) Misc OData issues

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2664?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2664: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1008698|https://bugzilla.redhat.com/show_bug.cgi?id=1008698] from NEW to ASSIGNED > Misc OData issues > ----------------- > > Key: TEIID-2664 > URL: https://issues.jboss.org/browse/TEIID-2664 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.3 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.4.1, 8.5 > > > Make TeiidProviderProducer's client connection a bounded concurrent map where entries can be expired on given cached time. -- 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-2664) Misc OData issues

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2664?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2664: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1008698 > Misc OData issues > ----------------- > > Key: TEIID-2664 > URL: https://issues.jboss.org/browse/TEIID-2664 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.3 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.4.1, 8.5 > > > Make TeiidProviderProducer's client connection a bounded concurrent map where entries can be expired on given cached time. -- 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-2664) Misc OData issues

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2664?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2664: ------------------------------------- The fix included - Synchronization and support of concurrent modification of Map that holds the metadata objects - Make this map also bound to 100 entries by default - Make the entries soft references such that in case of low memory these metadata caches will be purged - Register TeiidProviderProducer as VDBLifeCycleListener, such that when the VDB unloads the metadata is immediately purged. > Misc OData issues > ----------------- > > Key: TEIID-2664 > URL: https://issues.jboss.org/browse/TEIID-2664 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.3 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.4.1, 8.5 > > > Make TeiidProviderProducer's client connection a bounded concurrent map where entries can be expired on given cached time. -- 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-2664) Misc OData issues

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2664?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-2664: -------------------------------- Fix Version/s: 8.4.1 8.5 (was: 8.6) > Misc OData issues > ----------------- > > Key: TEIID-2664 > URL: https://issues.jboss.org/browse/TEIID-2664 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.3 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.4.1, 8.5 > > > Make TeiidProviderProducer's client connection a bounded concurrent map where entries can be expired on given cached time. -- 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-2664) Misc OData issues

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2664: ----------------------------------- Summary: Misc OData issues Key: TEIID-2664 URL: https://issues.jboss.org/browse/TEIID-2664 Project: Teiid Issue Type: Feature Request Components: Server Affects Versions: 8.3 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.6 Make TeiidProviderProducer's client connection a bounded concurrent map where entries can be expired on given cached time. -- 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-2657) ava.lang.NoClassDefFoundError: org/jaxen/NamespaceContext

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2657?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2657: --------------------------------------- Resolved in master/8.6. > ava.lang.NoClassDefFoundError: org/jaxen/NamespaceContext > --------------------------------------------------------- > > Key: TEIID-2657 > URL: https://issues.jboss.org/browse/TEIID-2657 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.4.1, 8.6 > > > When attempting to query an XML text file in ER1 I am getting A java.lang.NoClassDefFoundError: org/jaxen/NamespaceContext error: > 14:03:13,829 ERROR [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue2) TEIID30019 Unexpected exception for request Nob5JdZX4Frm.0: org.teiid.core.TeiidRuntimeException: org/jaxen/NamespaceContext > at org.teiid.query.processor.relational.XMLTableNode$1.run(XMLTableNode.java:232) [teiid-engine-8.4.1-redhat-1.jar:8.4.1-redhat-1] > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:269) [teiid-engine-8.4.1-redhat-1.jar:8.4.1-redhat-1] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.4.1-redhat-1.jar:8.4.1-redhat-1] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.4.1-redhat-1.jar:8.4.1-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0] > Caused by: java.lang.NoClassDefFoundError: org/jaxen/NamespaceContext > at nu.xom.NodeFactory.startMakingDocument(Unknown Source) [xom-1.2.7-redhat-3.jar:1.2.7-redhat-3] > at nux.xom.xquery.StreamingPathFilter$StreamingPathFilterNodeFactory.startMakingDocument(StreamingPathFilter.java:389) [nux-1.6.jar:1.6] > at nu.xom.XOMHandler.startDocument(Unknown Source) [xom-1.2.7-redhat-3.jar:1.2.7-redhat-3] > at net.sf.saxon.event.ContentHandlerProxy.open(ContentHandlerProxy.java:261) [saxonhe-9.2.1.5.jar:] > at org.teiid.query.xquery.saxon.ContentHandlerProxyReceiver.open(StreamingUtils.java:265) [teiid-engine-8.4.1-redhat-1.jar:8.4.1-redhat-1] > at net.sf.saxon.event.ProxyReceiver.open(ProxyReceiver.java:80) [saxonhe-9.2.1.5.jar:] > at net.sf.saxon.event.ReceivingContentHandler.startDocument(ReceivingContentHandler.java:204) [saxonhe-9.2.1.5.jar:] > at org.apache.xerces.parsers.AbstractSAXParser.startDocument(Unknown Source) > at org.apache.xerces.impl.dtd.XMLDTDValidator.startDocument(Unknown Source) > at org.apache.xerces.impl.XMLDocumentScannerImpl.startEntity(Unknown Source) > at org.apache.xerces.impl.XMLVersionDetector.startDocumentParsing(Unknown Source) > at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) > at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) > at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) > at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) > at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) > at net.sf.saxon.event.Sender.sendSAXSource(Sender.java:397) [saxonhe-9.2.1.5.jar:] > at net.sf.saxon.event.Sender.send(Sender.java:182) [saxonhe-9.2.1.5.jar:] > at net.sf.saxon.Configuration.buildDocument(Configuration.java:3317) [saxonhe-9.2.1.5.jar:] > at net.sf.saxon.Configuration.buildDocument(Configuration.java:3262) [saxonhe-9.2.1.5.jar:] > at org.teiid.query.xquery.saxon.SaxonReader.parse(StreamingUtils.java:169) [teiid-engine-8.4.1-redhat-1.jar:8.4.1-redhat-1] > at nu.xom.Builder.build(Unknown Source) [xom-1.2.7-redhat-3.jar:1.2.7-redhat-3] > at nu.xom.Builder.build(Unknown Source) [xom-1.2.7-redhat-3.jar:1.2.7-redhat-3] > at org.teiid.query.xquery.saxon.XQueryEvaluator.evaluateXQuery(XQueryEvaluator.java:134) [teiid-engine-8.4.1-redhat-1.jar:8.4.1-redhat-1] > at org.teiid.query.processor.relational.XMLTableNode$1.run(XMLTableNode.java:226) [teiid-engine-8.4.1-redhat-1.jar:8.4.1-redhat-1] > ... 6 more > Caused by: java.lang.ClassNotFoundException: org.jaxen.NamespaceContext from [Module "org.jboss.teiid:main" from local module loader @4bce79b8 (finder: local module finder @609945e9 (roots: /home/wgibson/apps/DV6-ER1/PASS-FOUR/jboss-eap-6.1/modules,/home/wgibson/apps/DV6-ER1/PASS-FOUR/jboss-eap-6.1/modules/system/layers/ds,/home/wgibson/apps/DV6-ER1/PASS-FOUR/jboss-eap-6.1/modules/system/layers/base))] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:196) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) [jboss-modules.jar:1.2.0.Final-redhat-1] > ... 31 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-2507) Better handling of user scoped lookups/matviews

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2507?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2507. --------------------------------- > Better handling of user scoped lookups/matviews > ----------------------------------------------- > > Key: TEIID-2507 > URL: https://issues.jboss.org/browse/TEIID-2507 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4 > > > With the inclusion of column and row security logic, it's more likely that lookups can produce user specific results. The current logic however treats lookups as always globally scoped. -- 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-2539) Add "allow-join" metadata based join processing on Foreign keys

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2539?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2539. --------------------------------- > Add "allow-join" metadata based join processing on Foreign keys > --------------------------------------------------------------- > > Key: TEIID-2539 > URL: https://issues.jboss.org/browse/TEIID-2539 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5 > > > MongoDB source generally does not support any joins between it collection of documents. However, one document can be embedded in other parent document, then those documents can be viewed as JOIN based documents. > Teiid's MongoDB translator takes the above as an approach to define each collection as a table, and provides ways to embed related tables into parent document for supporting the JOIN in SQL. > However, there may be situations, there is PK-FK relation between two tables, but they are not embeded, in those situations based on the capabilities of translator the query engine still pushes the join into translator for processing, but translator can not handle the join. In these situations, where the collections are not embedded the query engine need to behave as if translator does not support JOIN. > The proposal here is to add a extension metadata on FOREIGN KEY called "allow-joins=false", which query engine will consult along with the capabilities of the translator before it pushes the JOIN to the source translator. > This would be useful in non-relational translators to selectively support JOINS where possible. -- 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-2182) Mechanism to hook up event listener into Teiid runtime

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2182?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2182. --------------------------------- > Mechanism to hook up event listener into Teiid runtime > ------------------------------------------------------ > > Key: TEIID-2182 > URL: https://issues.jboss.org/browse/TEIID-2182 > Project: Teiid > Issue Type: Feature Request > Components: AdminApi, Server > Affects Versions: 8.1 > Environment: Windows 7 64 bit > Reporter: Anil Allewar > Assignee: Ramesh Reddy > Fix For: 8.3 > > > It would be to useful allow the installation of custom listeners since we don't have a global vdb table that could have customizable triggers. This could cover for example custom strategies for external materialization initialization. > This would also help in where an application wants to listen to when a VDB was added, made active, destroyed so that it can handle those events as required by the application. > Please see the thread below for the context & details > https://community.jboss.org/message/756060 -- 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-2580) xsi:nil is not honored by xmltable

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2580?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2580. --------------------------------- > xsi:nil is not honored by xmltable > ---------------------------------- > > Key: TEIID-2580 > URL: https://issues.jboss.org/browse/TEIID-2580 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.1, 8.5 > > > If an element is returnable by xmltable, but marked as nil more than likely an exception will be produced when attempting to convert the empty string value to a result. > For example: > {code} > select * from xmltable('/a/b' passing convert('<a xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><b xsi:nil="true"/><b>1</b></a>', xml) columns val integer path '.') as x > {code} > will error converting the first b element to an integer. -- 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