May 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4754) Wrong result with bidirectional relationship

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4754?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4754: --------------------------------- Fix Version/s: 8.12.11.6_3 > Wrong result with bidirectional relationship > -------------------------------------------- > > Key: TEIID-4754 > URL: https://issues.jboss.org/browse/TEIID-4754 > Project: Teiid > Issue Type: Bug > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.2, 9.1.4, 8.12.x-6.4, 8.12.11.6_3 > > > From the forum post, two tables that relate to each other: > EmployeeMasterEntity (PK EmployeeID, FK Departments) > OrganizationalUnitEntity (PK OrganizationalUnitID, FK Managers) > With data like: > EmployeeMasterEntity > EmployeeID Department > 1 10000001 > 2 10000002 > 3 10000001 > > OrganizationalUnitEntity > OrganizationaUnitID UnitManager > 10000001 1 > 10000002 2 > 10000003 2 > Will not return the correct results for a query such as: > http://localhost:8080/odata4/TestOdata.1/InterlemView/EmployeeMasterEntit... > This is due to using the wrong relationship for the navigation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4732) Teiid Server does not honor columns name in external materialization

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4732?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4732: --------------------------------- Fix Version/s: 8.12.11.6_3 > Teiid Server does not honor columns name in external materialization > -------------------------------------------------------------------- > > Key: TEIID-4732 > URL: https://issues.jboss.org/browse/TEIID-4732 > Project: Teiid > Issue Type: Bug > Components: Common > Affects Versions: 9.1.2 > Environment: * WildFly 10 > * Teiid Server 9.1.2 > * CentOs 7 > * MySQL 5.6.35 > Reporter: Pedro Inácio > Assignee: Steven Hawkins > Fix For: 9.0.6, 9.1.3, 8.7.12.6_2, 8.12.11.6_3 > > Attachments: NumberingPlan.csv, externalMaterializationOrderProblem-vdb.xml, mySqlCreateTable.sql, numberingPlan-vdb.xml > > > When defining a View with external materialization, if the view does not specify the columns in the same order as they are defined in the Materialized Table, Teiid Server inserts data in the wrong columns (in the order that is defined in the view). It appears that Teiid Server does not use the columns names but instead uses the column indexes. > Example: > If the view is defined like this: > {code:sql} > CREATE VIEW my_view ( > cns varchar(400), > country_code varchar(400) > ) > {code} > And the tables in the database are defined like this: > {code:sql} > CREATE TABLE my_view_cache_staging ( > country_code VARCHAR(400), > cns VARCHAR(400) > > ); > CREATE TABLE my_view_cache ( > country_code VARCHAR(400), > cns VARCHAR(400) > ); > {code} > Then when loadMatView runs, it will insert in country_code column in database the values from cns (view) and in cns column in database the values from country_code (view). > But if the view is defined like this: > {code:sql} > CREATE VIEW my_view ( > country_code varchar(400), > cns varchar(400) > ) > {code} > Then Teiid will insert the data "correctly". > It appears that loadMatView is using indexes instead of column names to insert the data. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4749) Cassandra type mapping

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4749?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4749. ----------------------------------- Resolution: Deferred We should wait for a specific community or customer request to pursue this. For uuid and inet values, they can simply be converted to string. For the collection types offering array/json support may need to be optional behavior given that objecttable can currently be used. > Cassandra type mapping > ---------------------- > > Key: TEIID-4749 > URL: https://issues.jboss.org/browse/TEIID-4749 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.3 > > > With TEIID-4476 there are more cassandra types mapped. When possible we should avoid mapping to Teiid object. Lists most naturally can be mapped to an array. Several of the other types may be appropriate to map this way, or even to json (for map support). > We also need to then ensure update handling with the conversion of the runtime type back to the expected Cassandra object type. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4722) TEIID30019: java.lang.AssertionError: Assertion failed assertion due to guard against a corner condition.

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4722?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4722: --------------------------------- Fix Version/s: 8.12.11.6_3 > TEIID30019: java.lang.AssertionError: Assertion failed assertion due to guard against a corner condition. > ----------------------------------------------------------------------------------------------------------- > > Key: TEIID-4722 > URL: https://issues.jboss.org/browse/TEIID-4722 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7.10.6_2 > Reporter: Johnathon Lee > Assignee: Steven Hawkins > Fix For: 9.2, 9.1.3, 8.7.12.6_2, 8.12.11.6_3 > > > Assertion failure: > {code:java} > ERROR [org.teiid.PROCESSOR] (Worker1_QueryProcessorQueue19151) TEIID30019 Unexpected exception for request WrzxYIqVWQ8G.11: java.lang.AssertionError: Assertion failed. > at org.teiid.core.util.Assertion.failed(Assertion.java:73) [teiid-common-core-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2] > at org.teiid.core.util.Assertion.assertTrue(Assertion.java:68) [teiid-common-core-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2] > at org.teiid.core.util.Assertion.assertTrue(Assertion.java:60) [teiid-common-core-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2] > at org.teiid.query.processor.relational.MergeJoinStrategy.setProcessingSortRight(MergeJoinStrategy.java:367) [teiid-engine-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2] > at org.teiid.query.processor.relational.DependentAccessNode.prepareNextCommand(DependentAccessNode.java:162) [teiid-engine-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2] > at org.teiid.query.processor.relational.AccessNode.openInternal(AccessNode.java:259) [teiid-engine-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2] > at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:371) [teiid-engine-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2] > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.7.10.6_2-redhat-2.jar:8.7.10.6_2-redhat-2] > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4892) oData v4 error using $expand

by Marco Monti (JIRA)

Marco Monti created TEIID-4892: ---------------------------------- Summary: oData v4 error using $expand Key: TEIID-4892 URL: https://issues.jboss.org/browse/TEIID-4892 Project: Teiid Issue Type: Bug Components: OData Affects Versions: 9.1.4 Environment: Teiid 9.1.4 with WildFly 10.0.0.Final running on Windows server 2012 R2 Datacenter Edition. Reporter: Marco Monti Assignee: Steven Hawkins Attachments: server.log Hello, we are querying Teiid 9.1.4 using the following oData v4 syntax: {{http://host:port/odata4/<vdbname>/<model-name>/<table-name>?$expand=<navigation>}} It doesn't matter what navigation property we choose; we always get following error message: {{{"error":{"code":null,"message":"String index out of range: -1"}}}} Please find the attached logfile. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4446) Rationalize precision/scale

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4446?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4446: --------------------------------- Fix Version/s: 8.12.11.6_3 > Rationalize precision/scale > --------------------------- > > Key: TEIID-4446 > URL: https://issues.jboss.org/browse/TEIID-4446 > Project: Teiid > Issue Type: Quality Risk > Components: OData, ODBC, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1, 8.12.11.6_3 > > > Our handling of precision/scale is inconsistent. There are assumptions being made in the JDBC client, types.dat, the parser, and other paths that need to be explicit and consistent. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4891) Fix and cleanup JDG quickstarts

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4891?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-4891: ------------------------------------ Should the current jdg quickstarts be moved out of the teiid-quickstarts and into a quickstart project under the Teiid JDG repo? > Fix and cleanup JDG quickstarts > ------------------------------- > > Key: TEIID-4891 > URL: https://issues.jboss.org/browse/TEIID-4891 > Project: Teiid > Issue Type: Task > Components: JDG Connector, Quick Starts > Affects Versions: 9.3, 8.12.x-6.4 > Reporter: Van Halbert > Assignee: Van Halbert > > Fix and clean up the JDG related quickstarts that include: > - update instructions > - update CLI scripts > - update vdb's > - update module dependencies -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4891) Fix and cleanup JDG quickstarts

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4891?page=com.atlassian.jira.plugin... ] Work on TEIID-4891 stopped by Van Halbert. ------------------------------------------ > Fix and cleanup JDG quickstarts > ------------------------------- > > Key: TEIID-4891 > URL: https://issues.jboss.org/browse/TEIID-4891 > Project: Teiid > Issue Type: Task > Components: JDG Connector, Quick Starts > Affects Versions: 9.3, 8.12.x-6.4 > Reporter: Van Halbert > Assignee: Van Halbert > > Fix and clean up the JDG related quickstarts that include: > - update instructions > - update CLI scripts > - update vdb's > - update module dependencies -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4891) Fix and cleanup JDG quickstarts

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4891?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4891: ------------------------------- Git Pull Request: https://github.com/teiid/teiid-quickstarts/pull/199, https://github.com/teiid/teiid-quickstarts/pull/200 (was: https://github.com/teiid/teiid-quickstarts/pull/199) PR 200 updates the remote-materializaiton quick start > Fix and cleanup JDG quickstarts > ------------------------------- > > Key: TEIID-4891 > URL: https://issues.jboss.org/browse/TEIID-4891 > Project: Teiid > Issue Type: Task > Components: JDG Connector, Quick Starts > Affects Versions: 9.3, 8.12.x-6.4 > Reporter: Van Halbert > Assignee: Van Halbert > > Fix and clean up the JDG related quickstarts that include: > - update instructions > - update CLI scripts > - update vdb's > - update module dependencies -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4749) Cassandra type mapping

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4749?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-4749: ------------------------------------- Assignee: Steven Hawkins (was: Kylin Soong) > Cassandra type mapping > ---------------------- > > Key: TEIID-4749 > URL: https://issues.jboss.org/browse/TEIID-4749 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.3 > > > With TEIID-4476 there are more cassandra types mapped. When possible we should avoid mapping to Teiid object. Lists most naturally can be mapped to an array. Several of the other types may be appropriate to map this way, or even to json (for map support). > We also need to then ensure update handling with the conversion of the runtime type back to the expected Cassandra object type. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2017