December 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2757) XML reserved characters not support in Odata

by Patrick Deenen (JIRA)

[ https://issues.jboss.org/browse/TEIID-2757?page=com.atlassian.jira.plugin... ] Patrick Deenen commented on TEIID-2757: --------------------------------------- I originally added this issue to the customer portal, which transferred here by Marc. I understand that this is a limitation of XML, hence it may not be classified as a bug. But it does limit the use of TEIID in real business scenarios where the source data is not cleaned or prepared for XML as is the case for our current customer. I do have requested to the customer to update the ETL processing to remove invalid characters, but still feels not comfortable because simple characters in the source data can break the system. This should IMHO not be the case. I would expect enterprise reliability from an enterprise product. That said I would settle for a simple configuration option which enables the replacement of invalid characters by white spaces if they cannot be replaced by XML entities. > XML reserved characters not support in Odata > -------------------------------------------- > > Key: TEIID-2757 > URL: https://issues.jboss.org/browse/TEIID-2757 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.4 > Environment: EAP version 6.1 with Teiid 8.5 > Reporter: Marc Shirley > Assignee: Steven Hawkins > > The odata framework sometimes has problems with transforming characters (reserved in XML) from the source data to the XML result. The result is an exception: TEIID16013 Error occured producing OData result.: java.lang.RuntimeException: com.ctc.wstx.exc.WstxIOException: Invalid white space character (0x1b) in text to output (in xml 1.1, could output as a character entity). -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2746) Add additional metadata validation rules

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2746?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2746. ----------------------------------- Resolution: Done Added just a validation of key columns. There is still a lot more that could be wrong with manually constructed metadata. > Add additional metadata validation rules > ---------------------------------------- > > Key: TEIID-2746 > URL: https://issues.jboss.org/browse/TEIID-2746 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.6 > > > In situations where metadata is constructed manually in a custom translator (not through the MetadataFactory, vdb, nor DDL), we do not validate all aspects for correctness. We should validate some additional scenarios that could lead to issues - for example one possible scenario is https://community.jboss.org/message/846138 -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2365) Reduce the usage of output names on the server side

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2365?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2365. --------------------------------- > Reduce the usage of output names on the server side > --------------------------------------------------- > > Key: TEIID-2365 > URL: https://issues.jboss.org/browse/TEIID-2365 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.5 > > > Parsed objects retain much of the original parse string, which is generally unnecessary on the server side. The use of output names should reduced to unnecessary memory consumption. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2617) Deleting a Data Source for a Deployed/Active VDB in Teiid Designer via Servers view does not set VDB inactive

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2617?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2617. --------------------------------- > Deleting a Data Source for a Deployed/Active VDB in Teiid Designer via Servers view does not set VDB inactive > ------------------------------------------------------------------------------------------------------------- > > Key: TEIID-2617 > URL: https://issues.jboss.org/browse/TEIID-2617 > Project: Teiid > Issue Type: Bug > Reporter: Barry LaFond > Assignee: Steven Hawkins > > 1) Created simple Parts model and deployed it in a PartsVDB and tested. > 2) Selected and removed/deleted the Parts Data Source in the Servers view > 3) Console logged the following: > {code} > 10:59:22,711 INFO [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue11) zBnnx+1aVUjv OracleExecutionFactory Commit=true;DatabaseProductName=Oracle;DatabaseProductVersion=Oracle Database 11g Release 11.1.0.0.0 - Production;DriverMajorVersion=10;DriverMajorVersion=2;DriverName=Oracle JDBC driver;DriverVersion=10.2.0.4.0;IsolationLevel=2 > 10:59:40,554 INFO [org.teiid.RUNTIME] (MSC service thread 1-8) TEIID40012 For PartsVDB.1 VDB, Data Source "PartsOracle11" not found. > 10:59:40,554 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) JBAS010409: Unbound data source [java:/PartsOracle11] > {code} > 4) VDB was not set to inactive and I was still able to connect to it in Data Tools explorer and try to "Sample Contents", or basically preview it. > {code} > 10:59:40,902 ERROR [org.jboss.remoting.remote.connection] (Remoting "blafond-thinkpad-t520:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Connection reset by peer > 11:02:59,017 WARN [org.teiid.CONNECTOR] (Worker3_QueryProcessorQueue22) +l1hF0r0+BN4 Connector worker process failed for atomic-request=+l1hF0r0+BN4.3.0.3: org.teiid.translator.TranslatorException: TEIID30481 Failed to find the Connection Factory with JNDI name PartsOracle11. Please check the name or deploy the Connection Factory with specified name. > at org.teiid.dqp.internal.datamgr.ConnectorManager.getConnectionFactory(ConnectorManager.java:251) [teiid-engine-8.4.1.jar:8.4.1] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:211) [teiid-engine-8.4.1.jar:8.4.1] > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:446) [teiid-engine-8.4.1.jar:8.4.1] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:159) [teiid-engine-8.4.1.jar:8.4.1] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:156) [teiid-engine-8.4.1.jar:8.4.1] > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.6.0_27] > at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.6.0_27] > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) [teiid-engine-8.4.1.jar:8.4.1] > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:269) [teiid-engine-8.4.1.jar:8.4.1] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.4.1.jar:8.4.1] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.4.1.jar:8.4.1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) [rt.jar:1.6.0_27] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.6.0_27] > at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_27] > Caused by: javax.naming.NameNotFoundException: PartsOracle11 -- service jboss.naming.context.java.PartsOracle11 > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:103) [jboss-as-naming-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:197) [jboss-as-naming-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:120) [jboss-as-naming-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:183) [jboss-as-naming-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179) [jboss-as-naming-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at javax.naming.InitialContext.lookup(InitialContext.java:409) [rt.jar:1.6.0_27] > at org.teiid.dqp.internal.datamgr.ConnectorManager.getConnectionFactory(ConnectorManager.java:247) [teiid-engine-8.4.1.jar:8.4.1] > ... 13 more > 11:02:59,024 WARN [org.teiid.PROCESSOR] (Worker2_QueryProcessorQueue23) +l1hF0r0+BN4 TEIID30020 Processing exception for request +l1hF0r0+BN4.3 'TEIID30504 PartsOracle11: TEIID30481 Failed to find the Connection Factory with JNDI name PartsOracle11. Please check the name or deploy the Connection Factory with specified name.'. Originally TeiidProcessingException 'PartsOracle11 -- service jboss.naming.context.java.PartsOracle11' ServiceBasedNamingStore.java:103. Enable more detailed logging to see the entire stacktrace. > {code} -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2572) Add native-query functionality to pushdown functions

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2572?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2572. --------------------------------- > Add native-query functionality to pushdown functions > ---------------------------------------------------- > > Key: TEIID-2572 > URL: https://issues.jboss.org/browse/TEIID-2572 > Project: Teiid > Issue Type: Enhancement > Components: Connector API > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.5 > > > Source functions should also support the parameterized native-query extension property to easily add calls that use non-standard or mapped function syntax. > For an operator like pg bit shift left: > {code} > create foreign function bsl (arg1 integer, arg2 integer) returns integer OPTIONS ("teiid_rel:native-query" '$1 << $2') > {code} > For an oracle sequence: > {code} > create foreign function seq_nextval () returns integer OPTIONS ("teiid_rel:native-query" 'seq.nextval') > {code} -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2530) Provide support for native queries in MongoDB

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2530?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2530. --------------------------------- > Provide support for native queries in MongoDB > --------------------------------------------- > > Key: TEIID-2530 > URL: https://issues.jboss.org/browse/TEIID-2530 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.4 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > > Provide support for native queries in MongoDB. user should be able to pas in java script and Teiid should execute and return the results -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2527) Dynamically change the sources in a multi-source model

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2527?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2527. --------------------------------- > Dynamically change the sources in a multi-source model > ------------------------------------------------------ > > Key: TEIID-2527 > URL: https://issues.jboss.org/browse/TEIID-2527 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine, Server > Reporter: Mark Addleman > Assignee: Steven Hawkins > Fix For: 8.5 > > > As a step toward a more dynamic VDB, it would be useful to allow data sources to be dynamically added/removed from a multi-source model. For more, see https://community.jboss.org/message/821113 -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2756) Web services war misses key in i18n.properties

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2756?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2756. --------------------------------- > Web services war misses key in i18n.properties > ---------------------------------------------- > > Key: TEIID-2756 > URL: https://issues.jboss.org/browse/TEIID-2756 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.5 > Environment: EAP version 6.1 with TEIID 8.5 > Reporter: Marc Shirley > Assignee: Steven Hawkins > > Generated sources for Web Services war not complete. The i18n.properties file misses the key ‘TeiidWSProvider.8’. In some cases this creates an exception. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2547) Fix drools-integration

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2547?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2547. --------------------------------- > Fix drools-integration > ---------------------- > > Key: TEIID-2547 > URL: https://issues.jboss.org/browse/TEIID-2547 > Project: Teiid > Issue Type: Sub-task > Components: Quick Starts > Reporter: Van Halbert > Assignee: Van Halbert > > Fix the .rar deployment based on the new EAP deployment requirements. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2483) Error trying to connect to Teiid using 8.3 code in Designer against an 8.4 server

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2483?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2483. --------------------------------- > Error trying to connect to Teiid using 8.3 code in Designer against an 8.4 server > --------------------------------------------------------------------------------- > > Key: TEIID-2483 > URL: https://issues.jboss.org/browse/TEIID-2483 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.4 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Fix For: 8.4 > > > This is the stacktrace I got when testing the connection to Van's new cluster at > redhat-stl-eng3.usersys.redhat.com. > org.teiid.adminapi.AdminProcessingException: TEIID70036 java.lang.IllegalArgumentException > at org.teiid.adminapi.AdminFactory$AdminImpl.getVDBs(AdminFactory.java:1433) > at org.teiid.adminapi.AdminFactory$AdminImpl.getVDBs(AdminFactory.java:1) > at org.teiid83.runtime.ExecutionAdmin.refreshVDBs(ExecutionAdmin.java:658) > at org.teiid83.runtime.ExecutionAdmin.init(ExecutionAdmin.java:575) > at org.teiid83.runtime.ExecutionAdmin.<init>(ExecutionAdmin.java:136) > at org.teiid83.runtime.ExecutionAdminFactory.createExecutionAdmin(ExecutionAdminFactory.java:29) > at > org.teiid.designer.runtime.registry.TeiidRuntimeRegistry.getExecutionAdmin(TeiidRuntimeRegistry.java:102) > at org.teiid.designer.runtime.TeiidServer.connect(TeiidServer.java:212) > at org.teiid.designer.runtime.TeiidServer.reconnect(TeiidServer.java:232) > at org.teiid.designer.runtime.ui.server.RefreshServerAction$1.run(RefreshServerAction.java:58) > <snip> > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584) > at org.eclipse.equinox.launcher.Main.run(Main.java:1438) > at org.eclipse.equinox.launcher.Main.main(Main.java:1414) > Caused by: java.lang.IllegalArgumentException > at org.jboss.dmr.ModelValue.getKeys(ModelValue.java:124) > at org.jboss.dmr.ModelNode.keys(ModelNode.java:1194) > at org.teiid.adminapi.AdminFactory$AdminImpl.getDomainAwareList(AdminFactory.java:1349) > at org.teiid.adminapi.AdminFactory$AdminImpl.getVDBs(AdminFactory.java:1430) > ... 48 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, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues December 2013