March 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3015) ODATA: Duplicate NavigationProperty name

by Ivan Lucas Vargas (JIRA)

[ https://issues.jboss.org/browse/TEIID-3015?page=com.atlassian.jira.plugin... ] Ivan Lucas Vargas commented on TEIID-3015: ------------------------------------------ [~shawkins], ok, I got your point. I'm using the version 8.13.2 of teiid. Also, I'm using odata2 format. And, my vdb is built by using the jdev9 (not the dynamic xml). > ODATA: Duplicate NavigationProperty name > ---------------------------------------- > > Key: TEIID-3015 > URL: https://issues.jboss.org/browse/TEIID-3015 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.3 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Beta3 > Fix For: 8.8, 8.7.1 > > > Entity 1: TransferRule > Entity 2: FinancialAccount > TransferRule > - sourceAccount : FinancialAccount > - destination : FinancialAccount > - other attributes > the mapping to this for odata resolves to > <NavigationProperty Name="financialaccount" Relationship="LivingODS.transferrule_destinationfinancial_account_id_fk" FromRole="transferrule" ToRole="financialaccount" /> > <NavigationProperty Name="financialaccount" Relationship="LivingODS.transferrule_sourcefinancial_account_id_fk" FromRole="transferrule" > ToRole="financialaccount" /> > The navigation property name is duplicated with in transfer rule entity. > Hence some of the Odata client see it as ambiguous element > Is there a way to customise the Name to > Name="src_financialaccount" and > Name="dest_financialaccount" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4084) Improve with clause performance via inlining

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4084?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4084. ----------------------------------- Resolution: Done Implemented in the rewriter as an early optimization with a better replacement strategy that what was used to inline just scalar with clauses. Also added the no_inline hint to prevent inlining if desired. > Improve with clause performance via inlining > -------------------------------------------- > > Key: TEIID-4084 > URL: https://issues.jboss.org/browse/TEIID-4084 > Project: Teiid > Issue Type: Feature Request > Components: Grammar, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > We should inline a with clause item that is only referenced a single time with a hint to prevent this behavior. Scalar with clauses could still be inlined multiple times. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4101) Internal materialization documentation should be more clear about implicit loading

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4101?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-4101: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1320286 Bugzilla Update: Perform > Internal materialization documentation should be more clear about implicit loading > ----------------------------------------------------------------------------------- > > Key: TEIID-4101 > URL: https://issues.jboss.org/browse/TEIID-4101 > Project: Teiid > Issue Type: Enhancement > Components: Documentation > Affects Versions: 8.12.3 > Reporter: Andrej Šmigala > Assignee: Steven Hawkins > Priority: Minor > > {quote}An internal materialized view table is initially in an invalid state (there is no data). If teiid_rel:ALLOW_MATVIEW_MANAGEMENT is not specified, the first user query will trigger an implicit loading of the data.{quote} > The documentation should probably explicitly say that setting the teiid_rel:ALLOW_MATVIEW_MANAGEMENT property to true will trigger the loading when the vdb is deployed. > https://docs.jboss.org/author/display/teiid812final/Internal+Materialization -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4101) Internal materialization documentation should be more clear about implicit loading

by Andrej Šmigala (JIRA)

Andrej Šmigala created TEIID-4101: ------------------------------------- Summary: Internal materialization documentation should be more clear about implicit loading Key: TEIID-4101 URL: https://issues.jboss.org/browse/TEIID-4101 Project: Teiid Issue Type: Enhancement Components: Documentation Affects Versions: 8.12.3 Reporter: Andrej Šmigala Assignee: Steven Hawkins Priority: Minor {quote}An internal materialized view table is initially in an invalid state (there is no data). If teiid_rel:ALLOW_MATVIEW_MANAGEMENT is not specified, the first user query will trigger an implicit loading of the data.{quote} The documentation should probably explicitly say that setting the teiid_rel:ALLOW_MATVIEW_MANAGEMENT property to true will trigger the loading when the vdb is deployed. https://docs.jboss.org/author/display/teiid812final/Internal+Materialization -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4098) Always preserve columns order in google spreadsheets models

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4098?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4098. ----------------------------------- Resolution: Done Converted to using a linkedhashmap in WorkSheet to preserve ordering. > Always preserve columns order in google spreadsheets models > ----------------------------------------------------------- > > Key: TEIID-4098 > URL: https://issues.jboss.org/browse/TEIID-4098 > Project: Teiid > Issue Type: Quality Risk > Components: Misc. Connectors > Affects Versions: 8.7 > Reporter: Marco Ardito > Assignee: Steven Hawkins > Priority: Minor > Fix For: 9.0, 8.12.5, 8.13.3 > > > I recently started using google spreadsheet datasources, and noticed that - at least sometime - the DDL model created by teiid has all columns but in a different (sort of random) order. This happened in particular using a google spreadsheet generated (linked to) google form, see forum reference attached. > Google form allows users to fill a lot of fields, which are collected as record columns in the google spreadsheet, then teiid makes that data available for integration with other sources - which is awesome, btw. > Creating a view in the VDB works anyway, since the query selects column "letters" like SELECT A,B,C and the right columns are selected, but having the model completely different from the source is weird and makes it difficult to work with it directly, if needed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4098) Always preserve columns order in google spreadsheets models

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4098?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4098: ---------------------------------- Issue Type: Quality Risk (was: Feature Request) Component/s: Misc. Connectors Fix Version/s: 9.0 8.12.5 8.13.3 Affects Version/s: 8.7 (was: 9.0) > Always preserve columns order in google spreadsheets models > ----------------------------------------------------------- > > Key: TEIID-4098 > URL: https://issues.jboss.org/browse/TEIID-4098 > Project: Teiid > Issue Type: Quality Risk > Components: Misc. Connectors > Affects Versions: 8.7 > Reporter: Marco Ardito > Assignee: Steven Hawkins > Priority: Minor > Fix For: 9.0, 8.12.5, 8.13.3 > > > I recently started using google spreadsheet datasources, and noticed that - at least sometime - the DDL model created by teiid has all columns but in a different (sort of random) order. This happened in particular using a google spreadsheet generated (linked to) google form, see forum reference attached. > Google form allows users to fill a lot of fields, which are collected as record columns in the google spreadsheet, then teiid makes that data available for integration with other sources - which is awesome, btw. > Creating a view in the VDB works anyway, since the query selects column "letters" like SELECT A,B,C and the right columns are selected, but having the model completely different from the source is weird and makes it difficult to work with it directly, if needed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4100) Full odata expand support

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4100: ------------------------------------- Summary: Full odata expand support Key: TEIID-4100 URL: https://issues.jboss.org/browse/TEIID-4100 Project: Teiid Issue Type: Feature Request Components: OData Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.1 To move TEIID-3039 we need to have xml document model style processing for expand support. That is top down generation that supports arbitrary descendants - with targeted optimizations for projection minimization and dependent joins. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4099) Improve with clause performance with incremental materialization

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4099: ------------------------------------- Summary: Improve with clause performance with incremental materialization Key: TEIID-4099 URL: https://issues.jboss.org/browse/TEIID-4099 Project: Teiid Issue Type: Enhancement Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.1 When a with clause item is first referenced it is fully materialized before use. We should generally allow iterative processing for full table scans - in scenarios where the table hasn't been augmented to add inferred indexes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4084) Improve with clause performance via inlining

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4084?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4084: ---------------------------------- Component/s: Grammar Description: We should inline a with clause item that is only referenced a single time with a hint to prevent this behavior. Scalar with clauses could still be inlined multiple times. (was: There are couple of things we can do here. The first would just be to inline a with clause item that is only referenced a single time (we may need to allow a hint to prevent this behavior). The other would be to generally allow more iterative processing - currently all results need to built into the common table before it can be accessed, but that should be able to be relaxed and done on demand.) Summary: Improve with clause performance via inlining (was: Improve with clause performance) Splitting into two jiras. > Improve with clause performance via inlining > -------------------------------------------- > > Key: TEIID-4084 > URL: https://issues.jboss.org/browse/TEIID-4084 > Project: Teiid > Issue Type: Feature Request > Components: Grammar, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > We should inline a with clause item that is only referenced a single time with a hint to prevent this behavior. Scalar with clauses could still be inlined multiple times. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3725) In the JDG translators, enable named cache swapping so that materialization can be supported

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3725?page=com.atlassian.jira.plugin... ] Work on TEIID-3725 stopped by Van Halbert. ------------------------------------------ > In the JDG translators, enable named cache swapping so that materialization can be supported > -------------------------------------------------------------------------------------------- > > Key: TEIID-3725 > URL: https://issues.jboss.org/browse/TEIID-3725 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.12 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 9.0, 8.12.5 > > > The JDG translators, that in order to support materialization, will need to enable the named cache that's referenced by the connection, to be swapped. This is due to JDG doesn't currently support renaming a cache (i.e., like table rename in JDBC). And because of that, it limits how the cache can be refreshed (don't want to clear it before re-loading). > Ideas are: > 1. configure translator with the 2 cache names to use (a) initial cache to read from and (b) the staging cache to use > perform materialize load > call SYSADMIN.setProperty to trigger the swapping of the cache names > 2 ??? > Note: because there's no persistence in Teiid so that any cache name changes will outlive a server restart, when a restart occurs, the translator will read from the cache identified as the initial cache to read from. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2016