October 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1236) Provide sample DS.xml files for all the data sources that Teiid supports.

by Ramesh Reddy (JIRA)

Provide sample DS.xml files for all the data sources that Teiid supports. ------------------------------------------------------------------------- Key: TEIID-1236 URL: https://jira.jboss.org/browse/TEIID-1236 Project: Teiid Issue Type: Task Components: Build/Kits Affects Versions: 7.1 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Priority: Minor Fix For: 7.1.1 Currently there are no sample -ds.xml files defined any where to create a LDAP, or SalesForce. Also Text and web Services are there but in a sample example. It would be nice to have one set of examples as JBoss AS does. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-1331) VDBMetaDataInstanceClassFactory is using old value

by Cristiano Nicolai (JIRA)

VDBMetaDataInstanceClassFactory is using old value -------------------------------------------------- Key: TEIID-1331 URL: https://jira.jboss.org/browse/TEIID-1331 Project: Teiid Issue Type: Bug Components: Jopr Plugin Affects Versions: 7.2 Environment: JbossAS 5.1 Reporter: Cristiano Nicolai Assignee: Steven Hawkins When updating ManagementComponent values via ProfileService, VDBMetaDataInstanceClassFactory class is using ManagedProperty.getValue to retrieve the updated value instead of MetaValue value received parameter. The value returned by ManagedProperty.getValue is the actual one, not the new value that was submitted. Basically should use: MetaValueFactory.getInstance().unwrap(value); Instead of: MetaValueFactory.getInstance().unwrap(property.getValue()); In all properties manipulated by the setValue method. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

3
9
0 / 0

[JBoss JIRA] Created: (TEIID-1235) The bind address 0.0.0.0 is always resolving to localhost

by Ramesh Reddy (JIRA)

The bind address 0.0.0.0 is always resolving to localhost --------------------------------------------------------- Key: TEIID-1235 URL: https://jira.jboss.org/browse/TEIID-1235 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 7.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.1.1 When bind address 0.0.0.0 used the server should allow connection using any IP address on that box. Including 127.0.0.1 or any number static or dynamic ip for that server. JBoss AS connects correctly, it is issue with address binding for the Teiid socket connections (JDBC, ADMIN, ODBC) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1256) Clear caches when VDB with same version re-deployed

by Ramesh Reddy (JIRA)

Clear caches when VDB with same version re-deployed --------------------------------------------------- Key: TEIID-1256 URL: https://jira.jboss.org/browse/TEIID-1256 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.1.1 When a VDB with same name and version is re-deployed, the new re-deployed VDB may have its metadata changed. In this case if Teiid has any PreparedPlanCache ResultSetCache they need to flushed for that VDB, otherwise it will produce wrong results. One issue is there could be active connections on VDB, those need to be terminated also. Based on how failover is configured they may re-connect on the next query automatically. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

2
5
0 / 0

[JBoss JIRA] Created: (TEIID-1231) Model visibility should only refer to whether entries are in metadata

by Steve Hawkins (JIRA)

Model visibility should only refer to whether entries are in metadata --------------------------------------------------------------------- Key: TEIID-1231 URL: https://jira.jboss.org/browse/TEIID-1231 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 7.1.1 Reporter: Steve Hawkins Assignee: Steve Hawkins Fix For: 7.1.1 Visibility should only apply to whether a table/model shows up in the system tables and should have nothing to do with whether it can be accessed. If a designer user wants to make a model non-accessable with the ease of the visibility mechansim, then they should create a data role ("default") that does not have permissions for model. Our roles would then need a boolean attribute (any-authenticated) to denote that any authenticated user has the role. Designer/JOPR will also need to add support for the "any-authenticated" attribute. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1238) WS Connector config/configname should not be specific to ws-security

by Steven Hawkins (JIRA)

WS Connector config/configname should not be specific to ws-security -------------------------------------------------------------------- Key: TEIID-1238 URL: https://jira.jboss.org/browse/TEIID-1238 Project: Teiid Issue Type: Quality Risk Components: Misc. Connectors Affects Versions: 7.1.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.1.1 Since the WS Connector config/configname can utilize the CXF configuration for more than just ws-security (logging, hostname verification, etc.). The property names should not be specific to WSSecurity. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1195) Error message that a VDB was deployed in "deployed in inactive state" is insufficient for users to easily correct problem

by Paul Nittel (JIRA)

Error message that a VDB was deployed in "deployed in inactive state" is insufficient for users to easily correct problem ------------------------------------------------------------------------------------------------------------------------- Key: TEIID-1195 URL: https://jira.jboss.org/browse/TEIID-1195 Project: Teiid Issue Type: Bug Affects Versions: 7.1 Environment: All Reporter: Paul Nittel Assignee: Steve Hawkins Attachments: server.log.zip Admittedly this stems from another bug (where VDBs with even a warning are not deployed), but the lack of details surrounding the decision to deploy in an inactive state causes confusion. Even though my logging is set to DEBUG, the server log contains no details as to why the VDB was not made active. Please see the attached log file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

4
6
0 / 0

[JBoss JIRA] Created: (TEIID-1252) LOB handling strategry issues

by Steven Hawkins (JIRA)

LOB handling strategry issues ----------------------------- Key: TEIID-1252 URL: https://jira.jboss.org/browse/TEIID-1252 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 7.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.1.1 LOBs returned from sources cause executions to stay alive until the user query has been completed - this is true even if the LOB values are not returned to the user. Whenever an execution is kept alive, it's associated connection is held until the execution is closed - thus source connections may be held out of their pool indefinately. Currently each source execution will attempt to obtain a new connection from the pool, which with LOB handling will cause potentially many connections even to the same source to be held out of the their pool indefinitely. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

1
4
0 / 0

[JBoss JIRA] Created: (TEIID-1302) Selecting data from salesforce results in a IndexOutOfBoundsException

by Wanja Pernath (JIRA)

Selecting data from salesforce results in a IndexOutOfBoundsException --------------------------------------------------------------------- Key: TEIID-1302 URL: https://jira.jboss.org/browse/TEIID-1302 Project: Teiid Issue Type: Bug Components: Salesforce Connector Affects Versions: 7.1 Environment: Fedora 12, x86_64, java 6u21 Reporter: Wanja Pernath Assignee: Steven Hawkins Fix For: 7.1.1 After importing of the salesforce data structure via designer, connection with an EAP 5.1 runtime with Teiid7.1 installed, I get an IndexOutOfBoundsException when I am trying to do simple SELECTing of salesforce data: SELECT * from sfdc.salesforce.Opportunity o WHERE (1 = 1) and (o.Fiscal = '2011 2') and (o.Country_of_Order__c = 'Germany') Exception: 2010-10-12 20:10:32,376 ERROR [org.teiid.PROCESSOR] (Worker2_QueryProcessorQueue21) Unexpected exception for request cy2xWqMIKJHq.0 java.lang.IndexOutOfBoundsException: Index: 200, Size: 200 at java.util.ArrayList.RangeCheck(ArrayList.java:547) at java.util.ArrayList.get(ArrayList.java:322) at org.teiid.translator.salesforce.execution.QueryExecutionImpl.loadBatch(QueryExecutionImpl.java:190) at org.teiid.translator.salesforce.execution.QueryExecutionImpl.getRow(QueryExecutionImpl.java:165) at org.teiid.translator.salesforce.execution.QueryExecutionImpl.next(QueryExecutionImpl.java:157) at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:285) at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:270) at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:181) at org.teiid.dqp.internal.process.DataTierTupleSource.access$000(DataTierTupleSource.java:53) at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:89) at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:86) at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:107) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:188) at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:116) at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:290) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) The connector only works if I am selecting data of an Account: SELECT * from sfdc.salesforce.Account WHERE (1 = 1) and Name like 'Bit%' and BillingCountry = 'Germany'; (97 results) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

3
7
0 / 0

[JBoss JIRA] Created: (TEIID-1279) Got an Unexpected exception when starting the server, after digging, I think the message should have indicated that the UDF requires static methods

by Van Halbert (JIRA)

Got an Unexpected exception when starting the server, after digging, I think the message should have indicated that the UDF requires static methods --------------------------------------------------------------------------------------------------------------------------------------------------- Key: TEIID-1279 URL: https://jira.jboss.org/browse/TEIID-1279 Project: Teiid Issue Type: Bug Components: Server Reporter: Van Halbert Assignee: Steven Hawkins Priority: Minor Fix For: 7.1.1 When trying to start the server got this exception: Caused by: Unexpected exception while loading org.teiid.translator.jdbc.modeshape.functions.Cast.public java.lang.Object org.teiid.translator.jdbc.modeshape.functions.Cast.cast(java.lang.String,java.lang.String) with args= [class java.lang.String, class java.lang.String] at org.teiid.query.function.FunctionTree.addFunction(FunctionTree.java:315) at org.teiid.query.function.FunctionTree.addSource(FunctionTree.java:138) at org.teiid.query.function.FunctionTree.<init>(FunctionTree.java:82) at org.teiid.query.metadata.TransformationMetadata.<init>(TransformationMetadata.java:160) at org.teiid.deployers.CompositeVDB.buildTransformationMetaData(CompositeVDB.java:102) at org.teiid.deployers.CompositeVDB.update(CompositeVDB.java:84) at org.teiid.deployers.CompositeVDB.<init>(CompositeVDB.java:64) at org.teiid.deployers.VDBRepository.addVDB(VDBRepository.java:82) at org.teiid.deployers.VDBDeployer.deploy(VDBDeployer.java:145) at org.teiid.deployers.VDBDeployer.deploy(VDBDeployer.java:60) at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62) at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179) After digging into the code, I realized that the function methods are required to be static. It sure would have been nice if the error would have indicated the reason. And I can see this error happening in development. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2010