November 2016 - teiid-issues - Jboss List Archives

[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 commented on TEIID-4610: --------------------------------------- I don't quite follow what is going on here. In the user query you have concat('&quot',char(59)), which will be replaced with the literal value '"'. In the source query you are showing ''' - but there is no where in our logic where the xml escape value would be changed into a the replacement character. Can you confirm this is your exact user query and/or provide a log? > 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 > > Impala regexp_replace function appears to collide with prepared values only when attemping to replace apostrophe. > Error: > {{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 00:00:00.0'] SQL: SELECT regexp_replace(g_0.`string_column`, '\'', ''') FROM some_impala_table g_0 WHERE g_0.`date_key` = ? AND g_0.`customer_id` = 112]}} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4596) Teiid does not return genereted keys after executeBatch

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4596?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4596: ------------------------------------- [~jdurani] can you attach your test please? > Teiid does not return genereted keys after executeBatch > ------------------------------------------------------- > > Key: TEIID-4596 > URL: https://issues.jboss.org/browse/TEIID-4596 > Project: Teiid > Issue Type: Enhancement > Components: Documentation > Reporter: Juraj Duráni > Assignee: Ramesh Reddy > Priority: Minor > > Currently, Teiid does not return genereted keys after inserting value using PreparedStatement.executeBatch() method. JDBC ([4.1|http://download.oracle.com/otndocs/jcp/jdbc-4_1-mrel-spec/index.html]) does not require this : > {quote} > It is implementation-defined as to whether _getGeneratedKeys_ will return generated values after invoking the _executeBatch_ method. > {quote} > However, it would be nice to have this behavior documented - https://teiid.gitbooks.io/documents/content/client-dev/JDBC_Support.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4596) Teiid does not return genereted keys after executeBatch

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4596?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-4596: ----------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) > Teiid does not return genereted keys after executeBatch > ------------------------------------------------------- > > Key: TEIID-4596 > URL: https://issues.jboss.org/browse/TEIID-4596 > Project: Teiid > Issue Type: Enhancement > Components: Documentation > Reporter: Juraj Duráni > Assignee: Ramesh Reddy > Priority: Minor > > Currently, Teiid does not return genereted keys after inserting value using PreparedStatement.executeBatch() method. JDBC ([4.1|http://download.oracle.com/otndocs/jcp/jdbc-4_1-mrel-spec/index.html]) does not require this : > {quote} > It is implementation-defined as to whether _getGeneratedKeys_ will return generated values after invoking the _executeBatch_ method. > {quote} > However, it would be nice to have this behavior documented - https://teiid.gitbooks.io/documents/content/client-dev/JDBC_Support.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4582) Enable flexibiliy in use of colon delimiter when defining cacheTypeMap property

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4582?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4582: ------------------------------- Git Pull Request: https://github.com/teiid/teiid/pull/840, https://github.com/teiid/teiid-documents/pull/80 (was: https://github.com/teiid/teiid/pull/840) > Enable flexibiliy in use of colon delimiter when defining cacheTypeMap property > ------------------------------------------------------------------------------- > > Key: TEIID-4582 > URL: https://issues.jboss.org/browse/TEIID-4582 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Trivial > Fix For: 9.2 > > > The cacheTypeMap property syntax is the following: > cacheName:className;pkFieldName > where the colon and semi-colon are used. Change to be flexibile to also support colon for the second delimiter. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4582) Enable flexibiliy in use of colon delimiter when defining cacheTypeMap property

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4582?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4582: ------------------------------- Fix Version/s: 9.2 > Enable flexibiliy in use of colon delimiter when defining cacheTypeMap property > ------------------------------------------------------------------------------- > > Key: TEIID-4582 > URL: https://issues.jboss.org/browse/TEIID-4582 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Trivial > Fix For: 9.2 > > > The cacheTypeMap property syntax is the following: > cacheName:className;pkFieldName > where the colon and semi-colon are used. Change to be flexibile to also support colon for the second delimiter. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4582) Enable flexibiliy in use of colon delimiter when defining cacheTypeMap property

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4582?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4582: ------------------------------- Git Pull Request: https://github.com/teiid/teiid/pull/840 > Enable flexibiliy in use of colon delimiter when defining cacheTypeMap property > ------------------------------------------------------------------------------- > > Key: TEIID-4582 > URL: https://issues.jboss.org/browse/TEIID-4582 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Trivial > > The cacheTypeMap property syntax is the following: > cacheName:className;pkFieldName > where the colon and semi-colon are used. Change to be flexibile to also support colon for the second delimiter. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4558) Query Plan Analyzer

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4558?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4558: ---------------------------------- Fix Version/s: 9.2 Assigning to 9.2 to improve text plan. Any additional information about problem nodes should be handled as annotations that will be available on the xml plan as well. > Query Plan Analyzer > ------------------- > > Key: TEIID-4558 > URL: https://issues.jboss.org/browse/TEIID-4558 > Project: Teiid > Issue Type: Feature Request > Components: Tools > Affects Versions: 9.2 > Reporter: Van Halbert > Fix For: 9.2 > > > Provide a tool that would take a query plan and provide feed back. > Example: > - indicate where there maybe a problem in the structure of the query that may impact performance > - indicate in the plan where there maybe issues (like table scan, no rows, etc.) > - provide recommendations for improving performance > etc.. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4603) Insert issue when cache contains multiple pojo's with the same key value

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4603?page=com.atlassian.jira.plugin... ] Work on TEIID-4603 stopped by Van Halbert. ------------------------------------------ > Insert issue when cache contains multiple pojo's with the same key value > ------------------------------------------------------------------------ > > Key: TEIID-4603 > URL: https://issues.jboss.org/browse/TEIID-4603 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Blocker > Fix For: 9.2 > > > There is an INSERT issue when there are multiple pojo's stored in the same cache and the keys' overlap (meaning the different types of pojo's have the same key). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4603) Insert issue when cache contains multiple pojo's with the same key value

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4603?page=com.atlassian.jira.plugin... ] Work on TEIID-4603 started by Van Halbert. ------------------------------------------ > Insert issue when cache contains multiple pojo's with the same key value > ------------------------------------------------------------------------ > > Key: TEIID-4603 > URL: https://issues.jboss.org/browse/TEIID-4603 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Blocker > Fix For: 9.2 > > > There is an INSERT issue when there are multiple pojo's stored in the same cache and the keys' overlap (meaning the different types of pojo's have the same key). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4517) Add support for deleting child objects

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4517?page=com.atlassian.jira.plugin... ] Work on TEIID-4517 started by Van Halbert. ------------------------------------------ > Add support for deleting child objects > -------------------------------------- > > Key: TEIID-4517 > URL: https://issues.jboss.org/browse/TEIID-4517 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 9.2, 8.12.7.6_3 > Reporter: Jan Stastny > Assignee: Van Halbert > Priority: Critical > Fix For: 9.2 > > > Infinispan cache dsl translator currently doesn't support deleting child objects when using complex POJO classes. > Example of complex POJO: > {code:plain} > package org.jboss.qe.jdg.remote.protobuf.complex; > /* @Indexed */ > message Person { > > /* @IndexedField(index=true, store=false) */ > required int32 id = 1; > > /* @IndexedField */ > required string name = 2; > > /* @IndexedField */ > optional string email = 3; > > /* @IndexedField(index=true, store=false) */ > repeated PhoneNumber phones = 4; > /* @Indexed */ > message Address { > > /* @IndexedField */ > required string Address = 1; > > /* @IndexedField(index=true, store=false) */ > required string City = 2; > > /* @IndexedField(index=true, store=false) */ > required string State = 3; > } > /* @IndexedField(index=true, store=false) */ > optional Address address = 5; > } > > /* @Indexed */ > message PhoneNumber { > > /* @IndexedField */ > required string number = 1; > } > {code} > Mapped metadata: > {code:sql} > CREATE FOREIGN TABLE Address ( > Address string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'address.Address', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > City string NOT NULL OPTIONS (NAMEINSOURCE 'address.City', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > State string NOT NULL OPTIONS (NAMEINSOURCE 'address.State', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'address') > ) OPTIONS (UPDATABLE TRUE); > > CREATE FOREIGN TABLE Person ( > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > name string NOT NULL OPTIONS (NAMEINSOURCE 'name', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > email string OPTIONS (NAMEINSOURCE 'email', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > CONSTRAINT PK_ID PRIMARY KEY(id) > ) OPTIONS (UPDATABLE TRUE); > > CREATE FOREIGN TABLE PhoneNumber ( > number string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'phones.number', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'phones') > ) OPTIONS (UPDATABLE TRUE); > {code} > Expected usage: > {code:sql} > DELETE FROM PhoneNumber WHERE id=3 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2016