September 2016 - teiid-issues - Jboss List Archives

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

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4456?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4456: ------------------------------- Git Pull Request: https://github.com/teiid/teiid/pull/805 > 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 > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Van Halbert > > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4318) Add option to define or determine ProtoField 1-to-x relationships

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4318?page=com.atlassian.jira.plugin... ] Van Halbert closed TEIID-4318. ------------------------------ Resolution: Duplicate Issue This is being resolved in TEIID-4456 and the improvement of handling nested and non-nested protobuf messages. > Add option to define or determine ProtoField 1-to-x relationships > ----------------------------------------------------------------- > > Key: TEIID-4318 > URL: https://issues.jboss.org/browse/TEIID-4318 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 9.x > Reporter: Van Halbert > Assignee: Van Halbert > > Now that the infinispan hotrod translator/connector support the use of Java Protobuf Annotations for defining the metadata and configuring the cache, now the logic needs to be able to determine the 1-to-n relationships that can be defined from the parent object. > Example: a Person can have 0 to many phone numbers > The following is how to define with annotation: > {code} > Person { > ... > @ProtoField(number = 4, collectionImplementation = ArrayList.class) > public List<PhoneNumber> phones; > ... > } > {code} > The connector will need to be able to make this determination so that it can register PhoneNumber when configuring the cache. Example: > {code} > String protoSchema = protoSchemaBuilder > .fileName(protoName) > .addClass(Person.class) > .addClass(PhoneNumber.class) > .build(ctx); > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

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

by Van Halbert (JIRA)

Van Halbert created TEIID-4478: ---------------------------------- Summary: 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.2 Reporter: Van Halbert Assignee: Steven Hawkins Priority: Critical 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, 7 months

1
0
0 / 0

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

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4478?page=com.atlassian.jira.plugin... ] Van Halbert reassigned TEIID-4478: ---------------------------------- Assignee: Van Halbert (was: Steven Hawkins) > 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.2 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Critical > > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4469) Insert with query expression does not apply source hint to target

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4469?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4469: --------------------------------- Fix Version/s: 8.7.10_6.2 > Insert with query expression does not apply source hint to target > ----------------------------------------------------------------- > > Key: TEIID-4469 > URL: https://issues.jboss.org/browse/TEIID-4469 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7.1.6_2 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 9.1, 9.0.5, 8.7.10_6.2 > > > "INSERT INTO ... SELECT ..." statements result in a ProjectIntoNode which seems to prevent any source hints from being passed down to the relevant source. These work correctly with an "INSERT INTO ... VALUES ..." statement. I've included example user and final query plan data below for the non-working [1] and working [2] insert statements. > [1] source hint not applied to ProjectIntoNode: > USER COMMAND: > INSERT /*+sh test:'append' */ INTO test.TEST (ID, "VALUE") SELECT X.id AS ID, X."value" AS "VALUE" FROM (SELECT bqt.SMALLA.INTKEY AS id, bqt.SMALLA.INTNUM AS "value" FROM bqt.SMALLA WHERE bqt.SMALLA.INTKEY = 0) AS X > ... > OPTIMIZATION COMPLETE: > PROCESSOR PLAN: > ProjectIntoNode(0) output=[Count] test.TEST > AccessNode(1) output=[bqt.SMALLA.INTKEY AS ID, bqt.SMALLA.INTNUM AS "VALUE"] SELECT /*+sh test:'append' */ g_0.INTKEY, g_0.INTNUM FROM bqt.SMALLA AS g_0 WHERE g_0.INTKEY = 0 > [2] source hint applied to AccessNode: > USER COMMAND: > INSERT /*+sh test:'append' */ INTO test.TEST (ID, "VALUE") VALUES ('-1', '-1') > ... > OPTIMIZATION COMPLETE: > PROCESSOR PLAN: > AccessNode(0) output=[Count] INSERT /*+sh test:'append' */ INTO test.TEST (ID, "VALUE") VALUES ('-1', '-1') -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

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

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4456?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4456: ------------------------------- Description: 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. was: Protobuf definition files can have messages defined in a nested and non-nested from. 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. > 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 > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Van Halbert > > 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, 7 months

1
0
0 / 0

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

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4456?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4456: ------------------------------- Description: Protobuf definition files can have messages defined in a nested and non-nested from. 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. was: Change configuration to enable the specification of all the protobuf descriptors to use. Currently, only the root protobuf descriptor is configured in the resource-adapter. Example: {code} <config-property name="MessageDescriptor"> bigdata.DataEntity </config-property> {code} and expect the .proto file to configure the relationship for the child descriptor within the parent: Example: {code} package bigdata; message DataEntity { .. optional MetaData context = 6; message MetaData { ... } } {code} and the metadata process can derive the children descriptors from the root descriptor. However, if all message descriptors are specified, that would allow for defining children message at the root level (outside the parent). And would allow the message descriptor to be shared among other messages. > 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 > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Van Halbert > > Protobuf definition files can have messages defined in a nested and non-nested from. > 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, 7 months

1
0
0 / 0

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

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4456?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4456: ------------------------------- Summary: Enable the abiltiy to support nested and non-nested message descriptors (was: Enable the abiltiy to specify all the message descriptors when using protobuf configuration) > 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 > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Van Halbert > > Change configuration to enable the specification of all the protobuf descriptors to use. > Currently, only the root protobuf descriptor is configured in the resource-adapter. Example: > {code} > <config-property name="MessageDescriptor"> > bigdata.DataEntity > </config-property> > {code} > > and expect the .proto file to configure the relationship for the child descriptor within the parent: > Example: > {code} > package bigdata; > message DataEntity { > .. > optional MetaData context = 6; > message MetaData { > ... > } > } > {code} > and the metadata process can derive the children descriptors from the root descriptor. > However, if all message descriptors are specified, that would allow for defining children message at the root level (outside the parent). And would allow the message descriptor to be shared among other messages. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4448) Multi-way join predicate inappropriately removed

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4448?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4448: --------------------------------- Fix Version/s: 8.7.10_6.2 > Multi-way join predicate inappropriately removed > ------------------------------------------------ > > Key: TEIID-4448 > URL: https://issues.jboss.org/browse/TEIID-4448 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 9.1, 8.13.7, 9.0.5, 8.7.10_6.2 > > > In a situation where copy criteria can work against a multi-way join predicate, such that the predicate is not pushed: > t1.a = coalesce(t2.b, t3.c, t4.d) ... t1.a = t4.d > The multi-way predicate can be marked as optional and removed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4443) STRING_AGG should not be decomposable

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4443?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4443: --------------------------------- Fix Version/s: 8.7.10_6.2 > STRING_AGG should not be decomposable > ------------------------------------- > > Key: TEIID-4443 > URL: https://issues.jboss.org/browse/TEIID-4443 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1, 8.7.10_6.2 > > > AggregateSymbol.canStage is returning true for string_agg - even though that is not correct, which can lead to an arrayindexoutofbounds exception when evaluating the final value based upon the partial as no separator will be in the tuple. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues September 2016