May 2018 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4864) Excel translator does not update document

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4864?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4864: --------------------------------------- Concurrent reads are supported because we are creating different workbooks for each thread. However updates would require a read/write lock. I'll see how quickly this can be done. > Excel translator does not update document > ----------------------------------------- > > Key: TEIID-4864 > URL: https://issues.jboss.org/browse/TEIID-4864 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.12.9.6_3 > Environment: JDV 6.3.4 > Reporter: Michael Echevarria > Fix For: 10.3 > > Attachments: colors.xlsx, error.log > > > *Changed to enhancement* > When attempting to update a row that is in an excel source, an Unsupported Execution createUpdateExecution is thrown. > Source file and log attached -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5341) Cannot extract time components from TIME column with Oracle

by Jan Martiska (JIRA)

Jan Martiska created TEIID-5341: ----------------------------------- Summary: Cannot extract time components from TIME column with Oracle Key: TEIID-5341 URL: https://issues.jboss.org/browse/TEIID-5341 Project: Teiid Issue Type: Bug Components: Misc. Connectors Affects Versions: 8.12.12.6_4 Reporter: Jan Martiska Assignee: Steven Hawkins This query against an Oracle-backed VDB: {noformat} SELECT hour(timevalue) FROM BQT1.SmallA {noformat} will fail with this error: {noformat} 13:16:42,493 WARN [org.teiid.CONNECTOR] (Worker9_QueryProcessorQueue157) Connector worker process failed for atomic-request=eiMf6Yh5oppn.9.0.25: org.teiid.translator.jdbc.JDBCExecutionException: 30076 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT c_0 FROM (SELECT EXTRACT(HOUR FROM case when g_0.timevalue is null then null else to_date('1970-01-01 ' || to_char(g_0.timevalue, 'HH24:MI:SS'), 'YYYY-MM-DD HH24:MI:SS') end) AS c_0 FROM smalla g_0 WHERE case when g_0.timevalue is null then null else to_date('1970-01-01 ' || to_char(g_0.timevalue, 'HH24:MI:SS'), 'YYYY-MM-DD HH24:MI:SS') end IS NOT NULL) WHERE ROWNUM <= 100] at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131) [translator-jdbc-8.12.13.6_4-redhat-64-3.jar:8.12.13.6_4-redhat-64-3] at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:361) at sun.reflect.GeneratedMethodAccessor170.invoke(Unknown Source) [:1.8.0_151] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_151] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_151] at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) at com.sun.proxy.$Proxy79.execute(Unknown Source) at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306) at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112) at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_151] at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:284) at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_151] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_151] at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_151] Caused by: java.sql.SQLException: ORA-30076: invalid extract field for extract source at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:450) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:399) at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1059) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:522) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:257) at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:587) at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:225) at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:53) at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:774) at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:925) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1111) at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:4798) at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:4845) at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery(OraclePreparedStatementWrapper.java:1501) at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:462) at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:123) [translator-jdbc-8.12.13.6_4-redhat-64-3.jar:8.12.13.6_4-redhat-64-3] ... 17 more {noformat} this seems to affect TIME columns which are converted from timestamps in the view model: {noformat} CREATE VIEW smalla (...) TimeValue time, (...) AS SELECT (...) convert(TimeValue, time) AS TimeValue {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4760) optional object name manipulations while executing IMPORT FOREIGN SCHEMA

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4760?page=com.atlassian.jira.plugin... ] Work on TEIID-4760 started by Steven Hawkins. --------------------------------------------- > optional object name manipulations while executing IMPORT FOREIGN SCHEMA > ------------------------------------------------------------------------ > > Key: TEIID-4760 > URL: https://issues.jboss.org/browse/TEIID-4760 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Bram Gadeyne > Assignee: Steven Hawkins > Labels: ddl, import, import_wizard > Fix For: 10.3 > > > While executing IMPORT FOREIGN SCHEMA, table (and other object) names are added to the schema with their original names. > In our previous virtual database we imported two schema's that contain the same objects but one is a production and another is a historical database. > We then change the name for e.g. table1 to prod_table1 or wh_table1 according to the schema it came from. Some software that interacts with teiid can not distinguish between different schemas and can not handle duplicate table names. So for this reason, this would also come in handy. > It would come in handy if it is possible to add a prefix to names while importing objects. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4691) Consider replacing JGroups based custom replication with native

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4691?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4691: ---------------------------------- Fix Version/s: (was: 10.3) > Consider replacing JGroups based custom replication with native > --------------------------------------------------------------- > > Key: TEIID-4691 > URL: https://issues.jboss.org/browse/TEIID-4691 > Project: Teiid > Issue Type: Enhancement > Components: Server > Reporter: Ramesh Reddy > Fix For: 10.x > > > JGroups is responsible for node to node communication. JGroups FRAG2 chunks up the messages that are sizeable by flow control. If you use TCP it will automatically break up the messages into the MTU. Using Jumbo Frames would be recommended. > Note that this will affect how we do the materialization replication among nodes currently. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5323) info logging of commands is too high by default for teiid embedded

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5323?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5323. ----------------------------------- Resolution: Done Updated the code and the docs to reference that user commands are at the debug level, and that source commands are logged to the .SOURCE child context - also at a debug level. > info logging of commands is too high by default for teiid embedded > ------------------------------------------------------------------ > > Key: TEIID-5323 > URL: https://issues.jboss.org/browse/TEIID-5323 > Project: Teiid > Issue Type: Task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.3 > > > From TEIID-5007 we had not resolved: Another issue that affects non-Wildfly usage are the defaults for command logging. For backwards compatibility the splitting of logging source/user level queries means that the user queries are logged at an info level - this may be too verbose. We could introduce a breaking/configurable change to alter this behavior. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5327) Add support to push timestampadd to oracle

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5327?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5327: --------------------------------------- This will only work when the interval value is a literal. The oracle parser will only accept a literal. Is this high enough value to add additional pushdown restrictions for that? > Add support to push timestampadd to oracle > ------------------------------------------ > > Key: TEIID-5327 > URL: https://issues.jboss.org/browse/TEIID-5327 > Project: Teiid > Issue Type: Enhancement > Components: Server > Affects Versions: 8.12.12.6_4 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 10.3 > > > Add pushdown support for timestampadd function to Oracle. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5285) Add high-level feature for redirection of updates

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5285?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5285: ---------------------------------- Fix Version/s: 10.x (was: 10.3) Marking as stopped progress. I don't see this becoming a robust feature for 10.3. We need to further clarify the usage scenarios: Teiid Spring Boot Teiid Side Car (do we have effective documentation for this?) Let's also clarify what the configuration looks like - extension metadata on the affected source tables, that can be enabled/disabled down to a table level (via env variables or feature flags?). Are we attempting to hide / remove the source table? There's not a great way to do that and still access it from the generated view / triggers - unless we're considering data roles. Or a new metadata flag could be needed, similar to hidden, that instead means "protected" (can only be accessed from views/non-anon procedures). > Add high-level feature for redirection of updates > ------------------------------------------------- > > Key: TEIID-5285 > URL: https://issues.jboss.org/browse/TEIID-5285 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine, Teiid Spring Boot > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.x > > > In microservices testing it is desirable to test against production/live data but not commit any updates. We should offer a simple solution that can defined by extension metadata and enabled/disabled by a feature flag. We may need to make simplifying assumptions about the scope (per session, per application, etc.) and durability of the updates. > Under the covers this will be achieved by using views, update triggers, and a store for the updates and when not enabled the expectation is that all operations should pass through. However the application will be limited to using Teiid SQL and will be required to use the Teiid or pg driver, or Teiid spring boot. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5285) Add high-level feature for redirection of updates

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5285?page=com.atlassian.jira.plugin... ] Work on TEIID-5285 stopped by Steven Hawkins. --------------------------------------------- > Add high-level feature for redirection of updates > ------------------------------------------------- > > Key: TEIID-5285 > URL: https://issues.jboss.org/browse/TEIID-5285 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine, Teiid Spring Boot > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.3 > > > In microservices testing it is desirable to test against production/live data but not commit any updates. We should offer a simple solution that can defined by extension metadata and enabled/disabled by a feature flag. We may need to make simplifying assumptions about the scope (per session, per application, etc.) and durability of the updates. > Under the covers this will be achieved by using views, update triggers, and a store for the updates and when not enabled the expectation is that all operations should pass through. However the application will be limited to using Teiid SQL and will be required to use the Teiid or pg driver, or Teiid spring boot. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2703) Refactor value retrieval to class based

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2703?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2703: ---------------------------------- Fix Version/s: (was: 10.3) > Refactor value retrieval to class based > --------------------------------------- > > Key: TEIID-2703 > URL: https://issues.jboss.org/browse/TEIID-2703 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.x > > > Similar to Hibernate, we need to introduce encapsulated value retrieval methods. The current approach (which is legacy back to the mmx days) typically uses a switch block with other checks, which can largely be avoided and should improve performance. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4932) Support defining UDFs based upon a class and or function

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4932?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4932: ---------------------------------- Fix Version/s: 10.x (was: 10.3) > Support defining UDFs based upon a class and or function > -------------------------------------------------------- > > Key: TEIID-4932 > URL: https://issues.jboss.org/browse/TEIID-4932 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.x > > > With the new ddl support, we should allow an import to work against a class to define UDFs. > We should also in general support inferring arguments for UDFs and UDFs that are defined by a method. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 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 2018