October 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4503) Unhandled charset conversion exception in lobworkitem

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4503?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4503. ----------------------------------- Resolution: Done Improved the exception handling on the value objects and in the lobworkitem. > Unhandled charset conversion exception in lobworkitem > ----------------------------------------------------- > > Key: TEIID-4503 > URL: https://issues.jboss.org/browse/TEIID-4503 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.2 > > > If getTextFiles is used on the File translator, the encoding is not validated so an exception can arise in the lobworkitem (or elsewhere) that is not handled gracefully. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4492) When using annotations, add option that specifies all child classes to register as part of the JDG schema

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4492?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4492: ------------------------------- Fix Version/s: 8.12.x > When using annotations, add option that specifies all child classes to register as part of the JDG schema > --------------------------------------------------------------------------------------------------------- > > Key: TEIID-4492 > URL: https://issues.jboss.org/browse/TEIID-4492 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.12.x, 9.2 > > Attachments: jdg-remote-cache-pojos.jar, jdg-remote-cache-vdb.xml, standalone.xml > > > When using protobuf annotations, need to specify all the child related (e.g, 1-to-1 relationship or 1-to-many relationship) pojo's that also need to be registered with the JDG schema. When these are registered, JDG will auto generate the .proto file and marshallers used by the schema. Which is the information used by the hot rod translator to create the source models. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 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: ------------------------------- Fix Version/s: 8.12.x > 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 > > > 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)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4504) Provide an option to ignore the atomic block handling of triggers

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4504: ------------------------------------- Summary: Provide an option to ignore the atomic block handling of triggers Key: TEIID-4504 URL: https://issues.jboss.org/browse/TEIID-4504 Project: Teiid Issue Type: Enhancement Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.2 While BEGIN ATOMIC is mandated by the spec, it may not be desirable to force a transaction block in all circumstances and instead rely on the autoCommit transaction. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4492) When using annotations, add option that specifies all child classes to register as part of the JDG schema

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4492?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4492: ------------------------------- Attachment: standalone.xml JDG 6.6 standalone.xml used to define the cache > When using annotations, add option that specifies all child classes to register as part of the JDG schema > --------------------------------------------------------------------------------------------------------- > > Key: TEIID-4492 > URL: https://issues.jboss.org/browse/TEIID-4492 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 9.2 > > Attachments: jdg-remote-cache-pojos.jar, jdg-remote-cache-vdb.xml, standalone.xml > > > When using protobuf annotations, need to specify all the child related (e.g, 1-to-1 relationship or 1-to-many relationship) pojo's that also need to be registered with the JDG schema. When these are registered, JDG will auto generate the .proto file and marshallers used by the schema. Which is the information used by the hot rod translator to create the source models. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4492) When using annotations, add option that specifies all child classes to register as part of the JDG schema

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4492?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4492: ------------------------------- Attachment: jdg-remote-cache-vdb.xml VDB that was used to access jdg cache. > When using annotations, add option that specifies all child classes to register as part of the JDG schema > --------------------------------------------------------------------------------------------------------- > > Key: TEIID-4492 > URL: https://issues.jboss.org/browse/TEIID-4492 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 9.2 > > Attachments: jdg-remote-cache-pojos.jar, jdg-remote-cache-vdb.xml, standalone.xml > > > When using protobuf annotations, need to specify all the child related (e.g, 1-to-1 relationship or 1-to-many relationship) pojo's that also need to be registered with the JDG schema. When these are registered, JDG will auto generate the .proto file and marshallers used by the schema. Which is the information used by the hot rod translator to create the source models. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4492) When using annotations, add option that specifies all child classes to register as part of the JDG schema

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4492?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4492: ------------------------------- Attachment: jdg-remote-cache-pojos.jar see quickstart/addressbook.proto for an example descriptor. > When using annotations, add option that specifies all child classes to register as part of the JDG schema > --------------------------------------------------------------------------------------------------------- > > Key: TEIID-4492 > URL: https://issues.jboss.org/browse/TEIID-4492 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 9.2 > > Attachments: jdg-remote-cache-pojos.jar > > > When using protobuf annotations, need to specify all the child related (e.g, 1-to-1 relationship or 1-to-many relationship) pojo's that also need to be registered with the JDG schema. When these are registered, JDG will auto generate the .proto file and marshallers used by the schema. Which is the information used by the hot rod translator to create the source models. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4492) When using annotations, add option that specifies all child classes to register as part of the JDG schema

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4492?page=com.atlassian.jira.plugin... ] Van Halbert edited comment on TEIID-4492 at 10/11/16 8:14 AM: -------------------------------------------------------------- Example: {code} <resource-adapter id="infinispanRemQSDSL"> <module slot="main" id="org.jboss.teiid.resource-adapter.infinispan.dsl"/> <connection-definitions> <connection-definition class-name="org.teiid.resource.adapter.infinispan.dsl.InfinispanManagedConnectionFactory" jndi-name="java:/infinispanRemoteDSL" enabled="true" use-java-context="true" pool-name="infinispanRemoteDSL"> <config-property name="Module"> com.client.quickstart.addressbook.pojos </config-property> <config-property name="RemoteServerList"> 127.0.0.1:11322 </config-property> <config-property name="ChildClasses"> com.client.quickstart.addressbook.pojos.domain.Address,com.client.quickstart.addressbook.pojos.domain.PhoneNumber </config-property> <config-property name="CacheTypeMap"> addressbook_indexed:com.client.quickstart.addressbook.pojos.domain.Person;id </config-property> </connection-definition> </connection-definitions> </resource-adapter> {code} was (Author: van.halbert): Example: <resource-adapter id="infinispanRemQSDSL"> <module slot="main" id="org.jboss.teiid.resource-adapter.infinispan.dsl"/> <connection-definitions> <connection-definition class-name="org.teiid.resource.adapter.infinispan.dsl.InfinispanManagedConnectionFactory" jndi-name="java:/infinispanRemoteDSL" enabled="true" use-java-context="true" pool-name="infinispanRemoteDSL"> <config-property name="Module"> com.client.quickstart.addressbook.pojos </config-property> <config-property name="RemoteServerList"> 127.0.0.1:11322 </config-property> <config-property name="ChildClasses"> com.client.quickstart.addressbook.pojos.domain.Address,com.client.quickstart.addressbook.pojos.domain.PhoneNumber </config-property> <config-property name="CacheTypeMap"> addressbook_indexed:com.client.quickstart.addressbook.pojos.domain.Person;id </config-property> </connection-definition> </connection-definitions> </resource-adapter> > When using annotations, add option that specifies all child classes to register as part of the JDG schema > --------------------------------------------------------------------------------------------------------- > > Key: TEIID-4492 > URL: https://issues.jboss.org/browse/TEIID-4492 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 9.2 > > Attachments: jdg-remote-cache-pojos.jar > > > When using protobuf annotations, need to specify all the child related (e.g, 1-to-1 relationship or 1-to-many relationship) pojo's that also need to be registered with the JDG schema. When these are registered, JDG will auto generate the .proto file and marshallers used by the schema. Which is the information used by the hot rod translator to create the source models. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4492) When using annotations, add option that specifies all child classes to register as part of the JDG schema

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4492?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-4492: ------------------------------------ Example: <resource-adapter id="infinispanRemQSDSL"> <module slot="main" id="org.jboss.teiid.resource-adapter.infinispan.dsl"/> <connection-definitions> <connection-definition class-name="org.teiid.resource.adapter.infinispan.dsl.InfinispanManagedConnectionFactory" jndi-name="java:/infinispanRemoteDSL" enabled="true" use-java-context="true" pool-name="infinispanRemoteDSL"> <config-property name="Module"> com.client.quickstart.addressbook.pojos </config-property> <config-property name="RemoteServerList"> 127.0.0.1:11322 </config-property> <config-property name="ChildClasses"> com.client.quickstart.addressbook.pojos.domain.Address,com.client.quickstart.addressbook.pojos.domain.PhoneNumber </config-property> <config-property name="CacheTypeMap"> addressbook_indexed:com.client.quickstart.addressbook.pojos.domain.Person;id </config-property> </connection-definition> </connection-definitions> </resource-adapter> > When using annotations, add option that specifies all child classes to register as part of the JDG schema > --------------------------------------------------------------------------------------------------------- > > Key: TEIID-4492 > URL: https://issues.jboss.org/browse/TEIID-4492 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 9.2 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 9.2 > > > When using protobuf annotations, need to specify all the child related (e.g, 1-to-1 relationship or 1-to-many relationship) pojo's that also need to be registered with the JDG schema. When these are registered, JDG will auto generate the .proto file and marshallers used by the schema. Which is the information used by the hot rod translator to create the source models. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 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 commented on TEIID-4456: ------------------------------------ NOTE: this fix doesn't change how the pojo's are exposed as tables, only how the metadata is derived from the descriptor. The resource-adapter configuration cacheTypeMap indicates the root class for which all relationships will be aligned. Using the MessageDescriptor property (bigdata.DataEntity), it gives the root descriptor location in the protobuf descriptor file for which will be the 1st (primary) table created. Then reading the details of the root descriptor, can determine what other relationships or column attribute that will be created. In this case, there's a complex object (e., MetatData) that represents a 1-to-1 relationship. So the logic has to derive the message descriptor for that object. The initial logic was expecting the message descriptor to be defined within the current (parent) descriptor. The change will now look for the descriptor outside (non-nested) of the parent descriptor. To test this, move the descriptor for Metadata from being defined within the parent to be at the top level. Why this is important is because for an existing JDG instance, the MetaData message descriptor could be shared among several other messages defined in the same .proto file. > 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: 9.1 > > > 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)

8 years, 2 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