May 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4663) Support a more secure block mode for client/server encryption

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4663?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4663: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1451866|https://bugzilla.redhat.com/show_bug.cgi?id=1451866] from NEW to ASSIGNED > Support a more secure block mode for client/server encryption > ------------------------------------------------------------- > > Key: TEIID-4663 > URL: https://issues.jboss.org/browse/TEIID-4663 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Driver, Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0.6, 9.1.2, 9.2, 8.12.x-6.4, 8.12.11.6_3 > > > ECB is the current default for the socket transport encryption of secure messages. While this is relatively ok for small messages as we also have a message key acting as a CTR counter to some of the blocks, it does not provide strong security - especially for large data volume scenarios, such as when using larger login payloads or the secure requests option. We should default instead to CBC with an explicit initialization vector. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4919) Sybase 15.7: running into'CREATE TABLE' command is not allowed within a multi-statement transaction in the 'tempdb' database.

by Ivan Chan (JIRA)

Ivan Chan created TEIID-4919: -------------------------------- Summary: Sybase 15.7: running into'CREATE TABLE' command is not allowed within a multi-statement transaction in the 'tempdb' database. Key: TEIID-4919 URL: https://issues.jboss.org/browse/TEIID-4919 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 9.1.1 Reporter: Ivan Chan Assignee: Steven Hawkins When I try to build VDB with sybase ASE 15.7 odb schema, I run into the following error: Caused by: java.sql.SQLException: The 'CREATE TABLE' command is not allowed within a multi-statement transaction in the 'tempdb' database. at com.sybase.jdbc4.jdbc.SybConnection.getAllExceptions(Unknown Source) at com.sybase.jdbc4.jdbc.SybStatement.handleSQLE(Unknown Source) at com.sybase.jdbc4.jdbc.SybStatement.nextResult(Unknown Source) at com.sybase.jdbc4.jdbc.SybStatement.nextResult(Unknown Source) at com.sybase.jdbc4.jdbc.SybStatement.queryLoop(Unknown Source) at com.sybase.jdbc4.jdbc.SybStatement.executeQuery(Unknown Source) at com.sybase.jdbc4.jdbc.SybCallableStatement.executeQuery(Unknown Source) at com.sybase.jdbc4.jdbc.SybDatabaseMetaData.if(Unknown Source) at com.sybase.jdbc4.jdbc.SybDatabaseMetaData.getColumns(Unknown Source) at org.apache.commons.dbcp.DelegatingDatabaseMetaData.getColumns(DelegatingDatabaseMetaData.java:218) at org.teiid.translator.jdbc.JDBCMetdataProcessor.getColumns(JDBCMetdataProcessor.java:382) at org.teiid.translator.jdbc.JDBCMetdataProcessor.getTables(JDBCMetdataProcessor.java:334) at org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:173) at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:306) ... 182 more I am using this driver: jconn4.jar [ com.sybase.jdbc4.jdbc.SybDriver ] And org.teiid.translator.jdbc.sybase.SybaseExecutionFactor -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4918) Enhance infinispan 7.1 support for muti-threaded puts or using putAll

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4918?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-4918: ------------------------------------ It was indicated that bulk insert could be used and in 7.1 or 7.2 the RemoteCache bulk insert would be enhanced to use in built multithreading to do the puts on the JDG server > Enhance infinispan 7.1 support for muti-threaded puts or using putAll > --------------------------------------------------------------------- > > Key: TEIID-4918 > URL: https://issues.jboss.org/browse/TEIID-4918 > Project: Teiid > Issue Type: Enhancement > Components: Infinispan > Affects Versions: 9.3 > Reporter: Van Halbert > Assignee: Ramesh Reddy > > For performance reasons, it was requested that the infinispan connector/translator be enhanced to be multi-threaded when doing batch inserts or try using the putAll option. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4918) Enhance infinispan 7.1 support for muti-threaded puts or using putAll

by Van Halbert (JIRA)

Van Halbert created TEIID-4918: ---------------------------------- Summary: Enhance infinispan 7.1 support for muti-threaded puts or using putAll Key: TEIID-4918 URL: https://issues.jboss.org/browse/TEIID-4918 Project: Teiid Issue Type: Enhancement Components: Infinispan Affects Versions: 9.3 Reporter: Van Halbert Assignee: Ramesh Reddy For performance reasons, it was requested that the infinispan connector/translator be enhanced to be multi-threaded when doing batch inserts or try using the putAll option. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4858) hive translator is extremely slow

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4858?page=com.atlassian.jira.plugin... ] Work on TEIID-4858 started by Steven Hawkins. --------------------------------------------- > hive translator is extremely slow > --------------------------------- > > Key: TEIID-4858 > URL: https://issues.jboss.org/browse/TEIID-4858 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Connector > Affects Versions: 8.12.9.6_3 > Environment: Tested against JDV 6.3.4 and the Cloudera quickstart 5.8 VM with the Cloudera sample data loaded into hive > Reporter: Michael Echevarria > Assignee: Steven Hawkins > Fix For: 9.3 > > Attachments: fast.log, override1.png, override2.png, slow.log > > > When querying a table through the hive translator the results take close to 30 seconds to return. > When querying a table through jdbc default results take under 1 second to return. > Both use the same underlying jboss server datasource. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4575) No such accessible property/method in the class after deploy vdb

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4575?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4575: ---------------------------------- Fix Version/s: (was: 9.3) Moving out of the 9.3 release as the JDG logic has shifted to another repository and these may become support rather than project concerns. > No such accessible property/method in the class after deploy vdb > ---------------------------------------------------------------- > > Key: TEIID-4575 > URL: https://issues.jboss.org/browse/TEIID-4575 > Project: Teiid > Issue Type: Bug > Components: Documentation, JDG Connector > Affects Versions: 9.2 > Reporter: Matej Kralik > Assignee: Van Halbert > Attachments: JDGproject.zip > > > When I want to deploy dynamic VDB with JDG materialization, the server shows me : TEIID31111 No such accessible property/method ISBN on class org.teiid.jdg.pojo.Book. > I looked at Book.java and ISBN is there. > The class is generated in the teiid designer. In the attachment is the project with dynamicVDB and generated JDG module. > Stacktrace: > {code:java} > 12:34:07,140 WARN [org.teiid.CONNECTOR] (Worker0_QueryProcessorQueue223) Connector worker process failed for atomic-request=e3xcwoJghvNm.0.69.131: org.teiid.translator.TranslatorException: TEIID31111 No such accessible property/method ISBN on class org.teiid.jdg.pojo.Book. > at org.teiid.translator.object.ObjectUpdateExecution.evaluate(ObjectUpdateExecution.java:524) [translator-object-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.translator.object.ObjectUpdateExecution.handleInsert(ObjectUpdateExecution.java:219) [translator-object-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.translator.object.ObjectUpdateExecution.executeUpdate(ObjectUpdateExecution.java:150) [translator-object-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.translator.object.ObjectUpdateExecution.execute(ObjectUpdateExecution.java:108) [translator-object-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem$1.execute(ConnectorWorkItem.java:402) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:364) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at sun.reflect.GeneratedMethodAccessor169.invoke(Unknown Source) [:1.8.0_91] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_91] > at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_91] > at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at com.sun.proxy.$Proxy46.execute(Unknown Source) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:142) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.query.processor.relational.ProjectIntoNode.checkExitConditions(ProjectIntoNode.java:264) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.query.processor.relational.ProjectIntoNode.nextBatchDirect(ProjectIntoNode.java:164) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:282) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:145) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.query.processor.BatchIterator.finalRow(BatchIterator.java:69) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.common.buffer.AbstractTupleSource.getCurrentTuple(AbstractTupleSource.java:70) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.query.processor.BatchIterator.getCurrentTuple(BatchIterator.java:84) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.common.buffer.AbstractTupleSource.hasNext(AbstractTupleSource.java:92) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.query.processor.proc.ProcedurePlan.executePlan(ProcedurePlan.java:608) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.query.processor.proc.CreateCursorResultSetInstruction.process(CreateCursorResultSetInstruction.java:69) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.query.processor.proc.ExecDynamicSqlInstruction$1.process(ExecDynamicSqlInstruction.java:218) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.query.processor.proc.ProcedurePlan.processProcedure(ProcedurePlan.java:389) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.query.processor.proc.ProcedurePlan.nextBatchDirect(ProcedurePlan.java:298) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.query.processor.proc.ProcedurePlan.nextBatch(ProcedurePlan.java:270) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.query.processor.relational.PlanExecutionNode.nextBatchDirect(PlanExecutionNode.java:118) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:282) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:150) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:282) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:145) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:164) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:146) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:472) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:348) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:274) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_91] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_91] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_91] > Caused by: javax.script.ScriptException: TEIID31111 No such accessible property/method ISBN on class org.teiid.jdg.pojo.Book. > at org.teiid.query.eval.TeiidScriptEngine$1.eval(TeiidScriptEngine.java:132) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.translator.object.ObjectUpdateExecution.evaluate(ObjectUpdateExecution.java:521) [translator-object-8.12.5.redhat-8.jar:8.12.5.redhat-8] > ... 47 more > 12:34:07,146 WARN [org.teiid.MATVIEWS] (Worker0_QueryProcessorQueue225) org.teiid.jdbc.TeiidSQLException: TEIID30504 BookCacheSource: TEIID31111 No such accessible property/method ISBN on class org.teiid.jdg.pojo.Book. > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4792) Unable to use WHERE clause against a JDG data source - ISPN000402: The type com.redhat.demo.sko.pojo.Call has no property named .....

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4792?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4792: ---------------------------------- Fix Version/s: (was: 9.3) Moving out of the 9.3 release as the JDG logic has shifted to another repository and these may become support rather than project concerns. > Unable to use WHERE clause against a JDG data source - ISPN000402: The type com.redhat.demo.sko.pojo.Call has no property named ..... > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-4792 > URL: https://issues.jboss.org/browse/TEIID-4792 > Project: Teiid > Issue Type: Bug > Components: JDG Connector > Environment: Mac OS > JDV 6.3.4 > JDG 6.6.1 > JBDS 10.3.0 with JBDSIS 10.0.2 > Reporter: Cojan van Ballegooijen > Assignee: Van Halbert > Attachments: Call_JDG_Module.zip, ChurnPrediction-vdb.xml, Contract_JDG_Module.zip, Screen Shot 2017-03-01 at 16.32.19.png, module pojo.xml, module.xml > > > SELECT * FROM Calls."Call" works as expected and returns all rows > Adding a where clause > SELECT * FROM Calls."Call" WHERE Calls."Call".Intlcalls > 0 > generate the following error: > org.teiid.runtime.client.TeiidClientException: java.lang.RuntimeException: Remote org.teiid.core.TeiidException: org.hibernate.hql.ParsingException: ISPN000402: The type com.redhat.demo.sko.pojo.Call has no property named 'Intlmins'. > Elapsed Time: 0 hr, 0 min, 0 sec, 191 ms. > If I join two VBL together and run the join query it returns the same error. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4857) Add file metadata such as creation and last modified date to file translator functions

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4857?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4857. ----------------------------------- Fix Version/s: 9.3 Resolution: Done Added to master and updated the docs. > Add file metadata such as creation and last modified date to file translator functions > -------------------------------------------------------------------------------------- > > Key: TEIID-4857 > URL: https://issues.jboss.org/browse/TEIID-4857 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 9.3 > > > Add file metadata such as creation date and last modified date to the data returned by the file translator functions (getFiles/getTextFiles). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4857) Add file metadata such as creation and last modified date to file translator functions

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4857?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4857: ---------------------------------- Issue Type: Enhancement (was: Feature Request) > Add file metadata such as creation and last modified date to file translator functions > -------------------------------------------------------------------------------------- > > Key: TEIID-4857 > URL: https://issues.jboss.org/browse/TEIID-4857 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Marc Shirley > Assignee: Steven Hawkins > > Add file metadata such as creation date and last modified date to the data returned by the file translator functions (getFiles/getTextFiles). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4857) Add file metadata such as creation and last modified date to file translator functions

by Marc Shirley (JIRA)

[ https://issues.jboss.org/browse/TEIID-4857?page=com.atlassian.jira.plugin... ] Marc Shirley commented on TEIID-4857: ------------------------------------- Correct. There was no talk of it being a function to apply towards the clob/blob values. It was only requested as additional columns being returned by the file translator functionality. > Add file metadata such as creation and last modified date to file translator functions > -------------------------------------------------------------------------------------- > > Key: TEIID-4857 > URL: https://issues.jboss.org/browse/TEIID-4857 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Marc Shirley > Assignee: Steven Hawkins > > Add file metadata such as creation date and last modified date to the data returned by the file translator functions (getFiles/getTextFiles). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2017