October 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2578) add/remove schema elements

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2578?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2578: ------------------------------------- >>import operations have different semantics than the declarations in a vdb.xml where schema imports can be redone on restart/demand and vdb imports are based upon the service. Yes, these semantics are different. The way I am viewing this is, the act of restart/redpolying of the VDB or someone explicitly updating the schema, both are actions taken by the user. With this we are some what similar to other databases. >>there is no service / runtime vdb created for the ddl based vdbs. all of the admin VDBOperations won't work correct? They should work, the service is required so that we can tie a deployment artifact to the VDB. Since here there is no deployment of the VDB then that layer is not needed. I had to move some functionalities of other services around but it should work. I see the benefits of deployment and repository based vdbs, we need to articulate both positions in examples and documents to choose what is better for the user. > add/remove schema elements > -------------------------- > > Key: TEIID-2578 > URL: https://issues.jboss.org/browse/TEIID-2578 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 9.2 > > > Schemas are currently static after load. Modifications can only happen with restarts or new versions. We should allow add/drop at runtime. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4510) JDG Complex POJO 1-n relationship wrong results when joining parent and child table

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4510?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4510: --------------------------------- Fix Version/s: 8.12.7.6_3 > JDG Complex POJO 1-n relationship wrong results when joining parent and child table > ----------------------------------------------------------------------------------- > > Key: TEIID-4510 > URL: https://issues.jboss.org/browse/TEIID-4510 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 9.2, 8.12.6.6_3 > Reporter: Jan Stastny > Assignee: Van Halbert > Priority: Blocker > Fix For: 9.2, 8.12.7.6_3 > > > When using infinispan-cache-dsl translator to access JDG cache incorrect results are returned for joins between the parent and child table. > POJO proto schema: > {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} > Source 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 TRUE, 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 TRUE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'phones') > ) OPTIONS (UPDATABLE TRUE); > {code} > Tested scenario: > {code:sql} > SELECT COUNT(*) FROM PhoneNumber WHERE id=1 > {code} > returns 2. > {code:sql} > SELECT COUNT(*) FROM Person p, PhoneNumber pn WHERE p.id=pn.id AND p.id=1 > {code} > or > {code:sql} > SELECT COUNT(*) FROM Person p INNER JOIN PhoneNumber pn ON p.id=pn.id WHERE p.id=1 > {code} > both return only 1. > NOTE: issue appears also when using only nested descriptors in the proto schema. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4456) Enable the abiltiy to support nested and non-nested message descriptors

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4456?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4456: --------------------------------- Fix Version/s: 8.12.7.6_3 > Enable the abiltiy to support nested and non-nested message descriptors > ----------------------------------------------------------------------- > > Key: TEIID-4456 > URL: https://issues.jboss.org/browse/TEIID-4456 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.12.x, 9.1, 8.12.7.6_3 > > > Protobuf definition files can have messages defined in a nested and non-nested form. > Nested: > {code} > package bigdata; > message DataEntity { > .. > optional MetaData context = 6; > message MetaData { > ... > } > } > {code} > Non-nested: > {code} > package bigdata; > message DataEntity { > .. > optional MetaData context = 6; > } > message MetaData { > ... > } > {code} > The ProtobufMetadataProcessor needs to be changed to so that it can create the metadata from either use case. > Currently it obtains the child descriptor messages from the parent descriptor. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4478) The 1-to-1 relationship currently doesn't work and doesn't error either

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4478?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4478: --------------------------------- Fix Version/s: 8.12.7.6_3 > The 1-to-1 relationship currently doesn't work and doesn't error either > ----------------------------------------------------------------------- > > Key: TEIID-4478 > URL: https://issues.jboss.org/browse/TEIID-4478 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 9.1 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Critical > Fix For: 9.1, 8.12.7.6_3 > > > The 1-to-1 relationship currently doesn't work or produce an exception. It appears to not be specifically handled. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4526) Integrate with Debezium for CDC for maintaining materialized views

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4526?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4526: ------------------------------- Summary: Integrate with Debezium for CDC for maintaining materialized views (was: Integrate with Debezium for CDC) > Integrate with Debezium for CDC for maintaining materialized views > ------------------------------------------------------------------ > > Key: TEIID-4526 > URL: https://issues.jboss.org/browse/TEIID-4526 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Critical > > Integrate with Debezium so that Teiid will be able to consume and react to the row-level change events and do something interesting with them, such as update the materialized view(s). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4526) Integrate with Debezium for CDC

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4526?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4526: ---------------------------------- Priority: Critical (was: Blocker) This cannot block a release without being scoped in terms of effort / level of integration. There are existing hooks that we provide for emitting and reacting to events which can be already be leveraged with minimal work. However anything that is new feature work needs to be well defined first. > Integrate with Debezium for CDC > ------------------------------- > > Key: TEIID-4526 > URL: https://issues.jboss.org/browse/TEIID-4526 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Critical > > Integrate with Debezium so that Teiid will be able to consume and react to the row-level change events and do something interesting with them, such as update the materialized view(s). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4526) Integrate with Debezium for CDC

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4526?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4526: ------------------------------- Priority: Blocker (was: Major) > Integrate with Debezium for CDC > ------------------------------- > > Key: TEIID-4526 > URL: https://issues.jboss.org/browse/TEIID-4526 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Blocker > > Integrate with Debezium so that Teiid will be able to consume and react to the row-level change events and do something interesting with them, such as update the materialized view(s). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4526) Integrate with Debezium for CDC

by Van Halbert (JIRA)

Van Halbert created TEIID-4526: ---------------------------------- Summary: Integrate with Debezium for CDC Key: TEIID-4526 URL: https://issues.jboss.org/browse/TEIID-4526 Project: Teiid Issue Type: Feature Request Components: Server Affects Versions: 9.2 Reporter: Van Halbert Assignee: Steven Hawkins Integrate with Debezium so that Teiid will be able to consume and react to the row-level change events and do something interesting with them, such as update the materialized view(s). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4525) postgresql translator - remove all nulls & non printable characters

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4525?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-4525: ------------------------------------- Component/s: JDBC Connector Fix Version/s: Open To Community 9.2 Priority: Minor (was: Major) Assignee: (was: Steven Hawkins) Thanks for capturing this Omar. > postgresql translator - remove all nulls & non printable characters > ------------------------------------------------------------------- > > Key: TEIID-4525 > URL: https://issues.jboss.org/browse/TEIID-4525 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Connector > Reporter: Omar Khan > Priority: Minor > Fix For: Open To Community, 9.2 > > > Would like to see the postgresql translator enhanced to add a feature to minimum remove nulls from text strings as some other databases i.e. Teradata allow for them where Postgres does not. This feature would behave in a similar manner as TrimSpaces, but simply remove all \u0000 characters. > Furthermore, if possible, would like the ability to remove non printable characters to as another option provide another additional stripping mechanism, allowing the postgresql database to serve as a data cleaner if need be. > Please refer to https://developer.jboss.org/thread/272644 for details -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4510) JDG Complex POJO 1-n relationship wrong results when joining parent and child table

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4510?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4510. ----------------------------------- Resolution: Done Merged the pull request. > JDG Complex POJO 1-n relationship wrong results when joining parent and child table > ----------------------------------------------------------------------------------- > > Key: TEIID-4510 > URL: https://issues.jboss.org/browse/TEIID-4510 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 9.2, 8.12.6.6_3 > Reporter: Jan Stastny > Assignee: Van Halbert > Priority: Blocker > Fix For: 9.2 > > > When using infinispan-cache-dsl translator to access JDG cache incorrect results are returned for joins between the parent and child table. > POJO proto schema: > {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} > Source 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 TRUE, 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 TRUE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'phones') > ) OPTIONS (UPDATABLE TRUE); > {code} > Tested scenario: > {code:sql} > SELECT COUNT(*) FROM PhoneNumber WHERE id=1 > {code} > returns 2. > {code:sql} > SELECT COUNT(*) FROM Person p, PhoneNumber pn WHERE p.id=pn.id AND p.id=1 > {code} > or > {code:sql} > SELECT COUNT(*) FROM Person p INNER JOIN PhoneNumber pn ON p.id=pn.id WHERE p.id=1 > {code} > both return only 1. > NOTE: issue appears also when using only nested descriptors in the proto schema. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2016