December 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4627) High-level event handling

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4627?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4627: --------------------------------------- Nearly there for the first iteration. As a simplification the events will only be processed via the evendistributor, rather than initiated by Teiid changes. > High-level event handling > ------------------------- > > Key: TEIID-4627 > URL: https://issues.jboss.org/browse/TEIID-4627 > Project: Teiid > Issue Type: Enhancement > Components: Grammar, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.2 > > > We should look into high-level plugability of event handling at a row level. This could even be handled at the language level with new trigger semantics for source tables: create trigger on tbl on cdc (insert|update...) - which could potentially even specify the topic mapping other details. There is complexity for multi-source models here though. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4641) Create upsert/delete refresh support

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4641?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-4641: -------------------------------- Fix Version/s: 9.2 > Create upsert/delete refresh support > ------------------------------------ > > Key: TEIID-4641 > URL: https://issues.jboss.org/browse/TEIID-4641 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 9.2 > > > There must be an alternative to the implied default of the table rename strategy - which is problematic when a source is not transactional or even when it is - as a multi-part swap can leave the table non-existent for a brief window or the source may have issues with ddl under an xa transaction - TEIID-4579 > This is true for the non-transactional source incremental refresh as well, which is a delete then insert - it leaves the live table briefly in an inconsistent state. > A upsert/delete approach addresses both of these concerns at the expense of performance - especially when the source does not directly support upsert as the engine must implement a compensating procedure. However now that we have pushdown support for upsert, we'll continue to add source support. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3520) Add support for Swagger Translator

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3520?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-3520: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1401535, https://bugzilla.redhat.com/show_bug.cgi?id=1401626 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1401626) > Add support for Swagger Translator > ---------------------------------- > > Key: TEIID-3520 > URL: https://issues.jboss.org/browse/TEIID-3520 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 9.0 > > > http://swagger.io is popular REST service description framework, it defines a specification http://swagger.io/specification/ for REST service definition. > Teiid WS translator should add the ability to read this file (like WSDL) and provide the REST methods as endpoints that can be consumed from Teiid. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4625) Consider consolidating/managing materialization status tables

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-4625?page=com.atlassian.jira.plugin... ] Kylin Soong commented on TEIID-4625: ------------------------------------ Does the status table for both internal and external or only external? If use hibernate it's easy to auto-create tables, but the read write still in ddl procedure or in Java code? > Consider consolidating/managing materialization status tables > ------------------------------------------------------------- > > Key: TEIID-4625 > URL: https://issues.jboss.org/browse/TEIID-4625 > Project: Teiid > Issue Type: Enhancement > Components: Server > Reporter: Steven Hawkins > Assignee: Kylin Soong > Fix For: 9.2 > > > To enhance usability we should consider consolidating/managing status tables. Management would include auto creation similar (which could just leverage hibernate similar to the database log logic, regardless of whether we use hibernate to read/write). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4625) Consider consolidating/managing materialization status tables

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-4625?page=com.atlassian.jira.plugin... ] Kylin Soong reassigned TEIID-4625: ---------------------------------- Assignee: Kylin Soong > Consider consolidating/managing materialization status tables > ------------------------------------------------------------- > > Key: TEIID-4625 > URL: https://issues.jboss.org/browse/TEIID-4625 > Project: Teiid > Issue Type: Enhancement > Components: Server > Reporter: Steven Hawkins > Assignee: Kylin Soong > Fix For: 9.2 > > > To enhance usability we should consider consolidating/managing status tables. Management would include auto creation similar (which could just leverage hibernate similar to the database log logic, regardless of whether we use hibernate to read/write). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4643) Add encrypt/decrypt functions

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-4643?page=com.atlassian.jira.plugin... ] Kylin Soong reassigned TEIID-4643: ---------------------------------- Assignee: Kylin Soong > Add encrypt/decrypt functions > ----------------------------- > > Key: TEIID-4643 > URL: https://issues.jboss.org/browse/TEIID-4643 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Kylin Soong > Fix For: 9.2 > > > We should add encrypt/decrypt functions similar to the approach of the hash functions added with TEIID-4532 (explicitly named functions for algorithm and probably key length) that are nominally compatible with pgcrypto and other databases. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4441) Add FTP/SFTP based access to the File Resource Adapter

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-4441?page=com.atlassian.jira.plugin... ] Kylin Soong commented on TEIID-4441: ------------------------------------ I have concern of how to to implement the FTP VirtualFile, need your weight. Current FTP VirtualFile not reference a real physic file, rather than reference a Inputstream, which opened by FTP session(FTPClient), but FTPClient.retrieveFileStream must be call complete command after stream be closed: {code} FTPClient client = ... try { InputStream in = client.retrieveFileStream("pathToFile"); ... in.close() } finally { client.completePendingCommand(); } {code} More details from [1], especially the sentence "To finalize the file transfer you must call completePendingCommand and check its return value to verify success" So if we create a JDBC connection, try to open more stream, there will be a error throw, I think my initial thoughts that cache ftp file to local tmp filesystem may be good solution for this issue. [1] http://commons.apache.org/proper/commons-net/apidocs/org/apache/commons/n... > Add FTP/SFTP based access to the File Resource Adapter > ------------------------------------------------------ > > Key: TEIID-4441 > URL: https://issues.jboss.org/browse/TEIID-4441 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Kylin Soong > Fix For: Open To Community, 9.2 > > > This has been requested few times in the community, it would be nice to give provide this functionality. Using http://commons.apache.org/proper/commons-net/ seems to be right decision. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4610) Impala regexp_replace function colliding with prepared values

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4610?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4610. ----------------------------------- Fix Version/s: 9.2 Resolution: Done Added a doc note that disabling useBindVariables may be needed and referenced this issue. > Impala regexp_replace function colliding with prepared values > ------------------------------------------------------------- > > Key: TEIID-4610 > URL: https://issues.jboss.org/browse/TEIID-4610 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.13.3 > Reporter: Scott Wallace > Assignee: Steven Hawkins > Fix For: 9.2 > > Attachments: server.log > > > Impala regexp_replace function appears to collide with prepared values only when attemping to replace apostrophe. > select impala.regexp_replace(string_column,char(39),concat('&apos',char(59))) > from some_impala_table > where date_key = concat(substring('2016-01-15',1,7),'-01') > and customer_id = 112 > Error: > {noformat} > org.teiid.runtime.client.TeiidClientException: java.lang.RuntimeException: Remote org.teiid.core.TeiidProcessingException: TEIID30504 warehouse: 500051 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: ['2016-01-01'] SQL: SELECT regexp_replace(g_0.`string_column`, '\'', ''') FROM some_impala_table g_0 WHERE g_0.`process_date_key` = ? AND g_0.`customer_id` = 112] > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4610) Impala regexp_replace function colliding with prepared values

by Scott Wallace (JIRA)

[ https://issues.jboss.org/browse/TEIID-4610?page=com.atlassian.jira.plugin... ] Scott Wallace commented on TEIID-4610: -------------------------------------- [~shawkins] thanks as always for your feedback! No issue with marking resolved. > Impala regexp_replace function colliding with prepared values > ------------------------------------------------------------- > > Key: TEIID-4610 > URL: https://issues.jboss.org/browse/TEIID-4610 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.13.3 > Reporter: Scott Wallace > Assignee: Steven Hawkins > Attachments: server.log > > > Impala regexp_replace function appears to collide with prepared values only when attemping to replace apostrophe. > select impala.regexp_replace(string_column,char(39),concat('&apos',char(59))) > from some_impala_table > where date_key = concat(substring('2016-01-15',1,7),'-01') > and customer_id = 112 > Error: > {noformat} > org.teiid.runtime.client.TeiidClientException: java.lang.RuntimeException: Remote org.teiid.core.TeiidProcessingException: TEIID30504 warehouse: 500051 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: ['2016-01-01'] SQL: SELECT regexp_replace(g_0.`string_column`, '\'', ''') FROM some_impala_table g_0 WHERE g_0.`process_date_key` = ? AND g_0.`customer_id` = 112] > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4656) parseTimestamp issue with Oracle

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4656?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-4656: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1404859, https://bugzilla.redhat.com/show_bug.cgi?id=1404862 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1404859) > parseTimestamp issue with Oracle > -------------------------------- > > Key: TEIID-4656 > URL: https://issues.jboss.org/browse/TEIID-4656 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector, Query Engine > Affects Versions: 8.12 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.10.6_2, 9.2 > > > parseTimestamp is pushed as to_timestamp. However TO_TIMESTAMP is not generally valid unless the format string covers the entire string input value otherwise there is an exception about the picture ending. > This means in general that we cannot pushdown the parseDate/Time/Timestamp operations to oracle as that is behavioral different with the java format routines, which will process just to the end of the format string. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues December 2016