February 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4718) Enable JDG resource adapter to support HotRod SSL

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4718?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-4718: ------------------------------------ This can be closed as the changes have been pushed into the community. > Enable JDG resource adapter to support HotRod SSL > ------------------------------------------------- > > Key: TEIID-4718 > URL: https://issues.jboss.org/browse/TEIID-4718 > Project: Teiid > Issue Type: Enhancement > Components: JDG Connector > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 9.3 > > > Enable the JDG resource adapter to support the HotRod encryption [1] > http://infinispan.org/docs/9.0.x/infinispan_server_guide/infinispan_serve... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4718) Enable JDG resource adapter to support HotRod SSL

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4718?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4718: ------------------------------- Fix Version/s: (was: 8.12.9.6_3) > Enable JDG resource adapter to support HotRod SSL > ------------------------------------------------- > > Key: TEIID-4718 > URL: https://issues.jboss.org/browse/TEIID-4718 > Project: Teiid > Issue Type: Enhancement > Components: JDG Connector > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 9.3 > > > Enable the JDG resource adapter to support the HotRod encryption [1] > http://infinispan.org/docs/9.0.x/infinispan_server_guide/infinispan_serve... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4518) Add support for JDG 7.1

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4518?page=com.atlassian.jira.plugin... ] Work on TEIID-4518 started by Van Halbert. ------------------------------------------ > Add support for JDG 7.1 > ----------------------- > > Key: TEIID-4518 > URL: https://issues.jboss.org/browse/TEIID-4518 > Project: Teiid > Issue Type: Enhancement > Components: JDG Connector > Affects Versions: 8.12.7.6_3 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 9.3 > > > The JDG 7.1 modules need to be added as dependencies in the infinispan translator and connector module.xml files. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4739) Change JDG resource-adapter to support multiple Pojo's in the same cache

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4739?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-4739: ------------------------------------ This is about how to change the configuration of the resource adapter so that a single RA can support multiple pojo's. Right now a separate RA has to be defined for each pojo. One thought could be to only support simple pojo's (not complex). What would be needed to be configured: - the cache name - per pojo: class name and primary key could enable specifying muliple pojos on the cache map: cacheName:className:pkey;className:pkey;[....] > Change JDG resource-adapter to support multiple Pojo's in the same cache > ------------------------------------------------------------------------ > > Key: TEIID-4739 > URL: https://issues.jboss.org/browse/TEIID-4739 > Project: Teiid > Issue Type: Enhancement > Components: JDG Connector > Reporter: Van Halbert > Assignee: Van Halbert > > Change the JDG Resource-adapter to support multiple pojo's in the same cache, instead of having to configure multiple resource-adapters. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4516) Add support for updating child objects

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4516?page=com.atlassian.jira.plugin... ] Work on TEIID-4516 stopped by Van Halbert. ------------------------------------------ > Add support for updating child objects > -------------------------------------- > > Key: TEIID-4516 > URL: https://issues.jboss.org/browse/TEIID-4516 > Project: Teiid > Issue Type: Feature Request > Components: JDG Connector > Affects Versions: 8.12.7.6_3, 9.2 > Reporter: Jan Stastny > Assignee: Van Halbert > Priority: Critical > Fix For: 9.3 > > > When using complex pojo with JDG 6.6, updating child tables doesn't do anything. It doesn't update the rows, but neither throws exception. > The problem appears for both usages of JDG cache (annotated POJOs, protobuf+marshaller). I have following pojo structure: > {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} > That is, one top-level POJO class Person, and two child POJO classes: Address(1-to-1) and PhoneNumber(1-to-N). Neither Address nor PhoneNumber tables could be updated. The DDL is following: > {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} > INSERT queries to prepare data: > {code:sql} > INSERT INTO Person(id,name,email) VALUES (1,'name1','email1') > INSERT INTO Address(id,Address,City,State) VALUES (1,'address1','city1','state1') > INSERT INTO PhoneNumber(id, number) VALUES (1, '001234567') > INSERT INTO PhoneNumber(id, number) VALUES (1, '001234568') > {code} > UPDATE queries and queries for checking results: > * 1-to-1 > {code:sql}UPDATE Address SET city='newCity' WHERE id=1{code} > {code:sql}SELECT * FROM Person,Address{code} > * 1-to-n > {code:sql}UPDATE PhoneNumber SET number='newNumber' WHERE id=1{code} > {code:sql}SELECT * FROM Person,PhoneNumber{code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 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 stopped 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: JDG Connector > Affects Versions: 8.12.7.6_3, 9.2 > Reporter: Jan Stastny > Assignee: Van Halbert > Priority: Critical > Fix For: 9.3 > > > 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, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4789) OData - Allow reading/writing messages in GZIP format

by Juraj Duráni (JIRA)

Juraj Duráni created TEIID-4789: ----------------------------------- Summary: OData - Allow reading/writing messages in GZIP format Key: TEIID-4789 URL: https://issues.jboss.org/browse/TEIID-4789 Project: Teiid Issue Type: Enhancement Components: OData Reporter: Juraj Duráni Assignee: Juraj Duráni Priority: Minor Allow writing and reading messages in GZIP format for OData interfaces. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4786) Report more information with max block exception

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4786?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4786. ----------------------------------- Resolution: Done Added more information, including the size. > Report more information with max block exception > ------------------------------------------------ > > Key: TEIID-4786 > URL: https://issues.jboss.org/browse/TEIID-4786 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.3 > > > When the max block exception occurs in the buffer manager it reports the batch manager and batch id - but those can only be traced back to a query based upon a detail/trace log of buffer manager activity. We should provide more information, which at the very least should include the number of rows/columns, how large it actually is, column types, etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4626) Add a full snapshot refresh strategy based upon table modifications

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4626?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-4626. --------------------------------- Resolution: Done - Changed to recursive look up - Excluded the Triggers while DDL export - Changed LAZY -->LAZY-SNAPSHOT, SNAPSHOT --> TTL-SNAPSHOT > Add a full snapshot refresh strategy based upon table modifications > ------------------------------------------------------------------- > > Key: TEIID-4626 > URL: https://issues.jboss.org/browse/TEIID-4626 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 9.3 > > > using the existing full materialization refresh logic we can trigger a refresh based upon a notion of how dirty a table is based upon a proportion of rows updated to the rows in the table. This would also require some change to the status table to capture the number of transitive row updates. This could then be hooked up to debezium as the event source. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4626) Add a full snapshot refresh strategy based upon table modifications

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4626?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4626: --------------------------------------- Also this is still a SNAPSHOT refresh strategy. So we could use terms like LAZY-SNAPSHOT or EAGER-SNAPSHOT, but it will be confusing to just say LAZY. > Add a full snapshot refresh strategy based upon table modifications > ------------------------------------------------------------------- > > Key: TEIID-4626 > URL: https://issues.jboss.org/browse/TEIID-4626 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 9.3 > > > using the existing full materialization refresh logic we can trigger a refresh based upon a notion of how dirty a table is based upon a proportion of rows updated to the rows in the table. This would also require some change to the status table to capture the number of transitive row updates. This could then be hooked up to debezium as the event source. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2017