January 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4298) Support in Odata4 for the Partner NavigationProperty attribute

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4298?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-4298. --------------------------------- Resolution: Done > Support in Odata4 for the Partner NavigationProperty attribute > -------------------------------------------------------------- > > Key: TEIID-4298 > URL: https://issues.jboss.org/browse/TEIID-4298 > Project: Teiid > Issue Type: Enhancement > Components: OData > Affects Versions: 9.0 > Reporter: Mirco Marchitiello > Assignee: Ramesh Reddy > Labels: alpha2 > Fix For: 9.2, 9.1.3, 8.12.9.6_3 > > > in Teiid 9.0 it would be useful to create a bidirectional link between tables, like in odata2 > for example: > <EntityType Name="Product"> > <Key> > <PropertyRef Name="ProductID"/> > </Key> > <Property Name="ProductID" Type="Edm.Int32" Nullable="false" p5:StoreGeneratedPattern="Identity"/> > <Property Name="ProductName" Type="Edm.String" Nullable="false" MaxLength="40"/> > <Property Name="SupplierID" Type="Edm.Int32"/> > <Property Name="CategoryID" Type="Edm.Int32"/> > <Property Name="QuantityPerUnit" Type="Edm.String" MaxLength="20"/> > <Property Name="UnitPrice" Type="Edm.Decimal" Precision="19" Scale="4"/> > <Property Name="UnitsInStock" Type="Edm.Int16"/> > <Property Name="UnitsOnOrder" Type="Edm.Int16"/><Property Name="ReorderLevel" Type="Edm.Int16"/> > <Property Name="Discontinued" Type="Edm.Boolean" Nullable="false"/> > <NavigationProperty Name="Category" Type="NorthwindModel.Category" Partner="Products"> > <ReferentialConstraint Property="CategoryID" ReferencedProperty="CategoryID"/> > </NavigationProperty> > <NavigationProperty Name="Order_Details" Type="Collection(NorthwindModel.Order_Detail)" Partner="Product"/> > <NavigationProperty Name="Supplier" Type="NorthwindModel.Supplier" Partner="Products"> > <ReferentialConstraint Property="SupplierID" ReferencedProperty="SupplierID"/> > </NavigationProperty> > </EntityType> > <EntityType Name="Category"> > <Key> > <PropertyRef Name="CategoryID"/> > </Key> > <Property Name="CategoryID" Type="Edm.Int32" Nullable="false" p5:StoreGeneratedPattern="Identity"/> > <Property Name="CategoryName" Type="Edm.String" Nullable="false" MaxLength="15"/> > <Property Name="Description" Type="Edm.String" MaxLength="max"/> > <Property Name="Picture" Type="Edm.Binary" MaxLength="max"/> > <NavigationProperty Name="Products" Type="Collection(NorthwindModel.Product)" Partner="Category"/> > </EntityType> > It seems that the two tables are related through NavigationProperty and Partner > In fact I can see all the Categories of a certain Product > http://services.odata.org/V4/Northwind/Northwind.svc/Products(10)/Category > or viceversa the products of a certain Category > http://services.odata.org/V4/Northwind/Northwind.svc/Categories(8)/Products > While in Teiid using odata2 this works just by creating a FK from one table to the other one, with odata4 this does not happen -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4717) Add Support for 'ALLOW FILTERING' in Teiid Cassandra Translator

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4717?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4717: --------------------------------------- The importer currently only detects primary keys. There would need to be more logic to detect other indexes. Otherwise it may need to place the hint anytime the primary key is not used. > Add Support for 'ALLOW FILTERING' in Teiid Cassandra Translator > --------------------------------------------------------------- > > Key: TEIID-4717 > URL: https://issues.jboss.org/browse/TEIID-4717 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Vijay K > Labels: cassandra > Fix For: 9.3 > > > At certain times it is unavoidable to use few columns in the where clause which are not part of the index, in that case Cassandra driver throws error > {color:red}Bad Request: Cannot execute this query as it might involve data filtering and thus may have unpredictable performance. If you want to execute this query despite the performance unpredictability, use ALLOW FILTERING{color} > As as user I should be able to configure the Cassandra translator to append *ALLOW FILTERING* to the generated query (CQL) > References: > https://www.datastax.com/dev/blog/allow-filtering-explained-2 > https://developer.jboss.org/thread/239011 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4298) Support in Odata4 for the Partner NavigationProperty attribute

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4298?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4298: --------------------------------------- Can this be marked as resolved again? > Support in Odata4 for the Partner NavigationProperty attribute > -------------------------------------------------------------- > > Key: TEIID-4298 > URL: https://issues.jboss.org/browse/TEIID-4298 > Project: Teiid > Issue Type: Enhancement > Components: OData > Affects Versions: 9.0 > Reporter: Mirco Marchitiello > Assignee: Ramesh Reddy > Labels: alpha2 > Fix For: 9.2, 9.1.3, 8.12.9.6_3 > > > in Teiid 9.0 it would be useful to create a bidirectional link between tables, like in odata2 > for example: > <EntityType Name="Product"> > <Key> > <PropertyRef Name="ProductID"/> > </Key> > <Property Name="ProductID" Type="Edm.Int32" Nullable="false" p5:StoreGeneratedPattern="Identity"/> > <Property Name="ProductName" Type="Edm.String" Nullable="false" MaxLength="40"/> > <Property Name="SupplierID" Type="Edm.Int32"/> > <Property Name="CategoryID" Type="Edm.Int32"/> > <Property Name="QuantityPerUnit" Type="Edm.String" MaxLength="20"/> > <Property Name="UnitPrice" Type="Edm.Decimal" Precision="19" Scale="4"/> > <Property Name="UnitsInStock" Type="Edm.Int16"/> > <Property Name="UnitsOnOrder" Type="Edm.Int16"/><Property Name="ReorderLevel" Type="Edm.Int16"/> > <Property Name="Discontinued" Type="Edm.Boolean" Nullable="false"/> > <NavigationProperty Name="Category" Type="NorthwindModel.Category" Partner="Products"> > <ReferentialConstraint Property="CategoryID" ReferencedProperty="CategoryID"/> > </NavigationProperty> > <NavigationProperty Name="Order_Details" Type="Collection(NorthwindModel.Order_Detail)" Partner="Product"/> > <NavigationProperty Name="Supplier" Type="NorthwindModel.Supplier" Partner="Products"> > <ReferentialConstraint Property="SupplierID" ReferencedProperty="SupplierID"/> > </NavigationProperty> > </EntityType> > <EntityType Name="Category"> > <Key> > <PropertyRef Name="CategoryID"/> > </Key> > <Property Name="CategoryID" Type="Edm.Int32" Nullable="false" p5:StoreGeneratedPattern="Identity"/> > <Property Name="CategoryName" Type="Edm.String" Nullable="false" MaxLength="15"/> > <Property Name="Description" Type="Edm.String" MaxLength="max"/> > <Property Name="Picture" Type="Edm.Binary" MaxLength="max"/> > <NavigationProperty Name="Products" Type="Collection(NorthwindModel.Product)" Partner="Category"/> > </EntityType> > It seems that the two tables are related through NavigationProperty and Partner > In fact I can see all the Categories of a certain Product > http://services.odata.org/V4/Northwind/Northwind.svc/Products(10)/Category > or viceversa the products of a certain Category > http://services.odata.org/V4/Northwind/Northwind.svc/Categories(8)/Products > While in Teiid using odata2 this works just by creating a FK from one table to the other one, with odata4 this does not happen -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4723) Add support for Cassandra 3.x

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4723?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4723. ----------------------------------- Fix Version/s: (was: 9.2.1) Resolution: Duplicate Issue Marking as a duplicate of TEIID-4476 > Add support for Cassandra 3.x > ----------------------------- > > Key: TEIID-4723 > URL: https://issues.jboss.org/browse/TEIID-4723 > Project: Teiid > Issue Type: Component Upgrade > Components: Connector API > Affects Versions: 9.1.1 > Reporter: Vijay K > Assignee: Steven Hawkins > Priority: Critical > > The latest version of Teiid right now supports Cassandra 2.1.3, which should be upgraded to 3.9 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4723) Add support for Cassandra 3.x

by Vijay K (JIRA)

Vijay K created TEIID-4723: ------------------------------ Summary: Add support for Cassandra 3.x Key: TEIID-4723 URL: https://issues.jboss.org/browse/TEIID-4723 Project: Teiid Issue Type: Component Upgrade Components: Connector API Affects Versions: 9.1.1 Reporter: Vijay K Assignee: Steven Hawkins Priority: Critical Fix For: 9.2.1 The latest version of Teiid right now supports Cassandra 2.1.3, which should be upgraded to 3.9 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4717) Add Support for 'ALLOW FILTERING' in Teiid Cassandra Translator

by Vijay K (JIRA)

[ https://issues.jboss.org/browse/TEIID-4717?page=com.atlassian.jira.plugin... ] Vijay K edited comment on TEIID-4717 at 1/25/17 7:44 AM: --------------------------------------------------------- I would prefer the first option "translator to infer this hint automatically from the index metadata on the source table". If we can discuss and decide on the design, I can do the implementation. was (Author: vijaynm): I would prefer the first option "translator to infer this hint automatically from the index metadata on the source table" > Add Support for 'ALLOW FILTERING' in Teiid Cassandra Translator > --------------------------------------------------------------- > > Key: TEIID-4717 > URL: https://issues.jboss.org/browse/TEIID-4717 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Vijay K > Labels: cassandra > Fix For: 9.3 > > > At certain times it is unavoidable to use few columns in the where clause which are not part of the index, in that case Cassandra driver throws error > {color:red}Bad Request: Cannot execute this query as it might involve data filtering and thus may have unpredictable performance. If you want to execute this query despite the performance unpredictability, use ALLOW FILTERING{color} > As as user I should be able to configure the Cassandra translator to append *ALLOW FILTERING* to the generated query (CQL) > References: > https://www.datastax.com/dev/blog/allow-filtering-explained-2 > https://developer.jboss.org/thread/239011 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4717) Add Support for 'ALLOW FILTERING' in Teiid Cassandra Translator

by Vijay K (JIRA)

[ https://issues.jboss.org/browse/TEIID-4717?page=com.atlassian.jira.plugin... ] Vijay K commented on TEIID-4717: -------------------------------- I would prefer the first option "translator to infer this hint automatically from the index metadata on the source table" > Add Support for 'ALLOW FILTERING' in Teiid Cassandra Translator > --------------------------------------------------------------- > > Key: TEIID-4717 > URL: https://issues.jboss.org/browse/TEIID-4717 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Vijay K > Labels: cassandra > Fix For: 9.3 > > > At certain times it is unavoidable to use few columns in the where clause which are not part of the index, in that case Cassandra driver throws error > {color:red}Bad Request: Cannot execute this query as it might involve data filtering and thus may have unpredictable performance. If you want to execute this query despite the performance unpredictability, use ALLOW FILTERING{color} > As as user I should be able to configure the Cassandra translator to append *ALLOW FILTERING* to the generated query (CQL) > References: > https://www.datastax.com/dev/blog/allow-filtering-explained-2 > https://developer.jboss.org/thread/239011 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4629) Offer a ddl solution to replace the vdb.xml

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4629?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4629: --------------------------------------- So create database and create schema would not change the current. That will seem more verbose, but it will be consistent with other ddl. TEIID-4536 would make it so the statements to define a schema could be associated with the create schema statement, so USE schema would not be needed. > Offer a ddl solution to replace the vdb.xml > ------------------------------------------- > > Key: TEIID-4629 > URL: https://issues.jboss.org/browse/TEIID-4629 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine, Server > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 9.2 > > > Based upon the work on TEIID-2578 we should first offer the ability to replace the vdb.xml with ddl. We can additionally include some of the work to represent additional pieces of the vdb as api level metadata objects (instead of in the admin layer) where possible. Ideally this should support as much alter functionality as possible. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4719) Add a ddl equivalent to the metadata tag

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4719?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4719: ------------------------------------- To be same as XML, Yes the schema already exists, we are just adding the text content from the repo as is into it, then the repo should the rest during the load. > Add a ddl equivalent to the metadata tag > ---------------------------------------- > > Key: TEIID-4719 > URL: https://issues.jboss.org/browse/TEIID-4719 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > > Generally we'll need something that is equivalent to the metadata tag - that can specify a repo and options. In a zip deployment this will allow splitting the ddl over multiple files. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4629) Offer a ddl solution to replace the vdb.xml

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4629?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4629: ------------------------------------- So support the context establishment with both. > Offer a ddl solution to replace the vdb.xml > ------------------------------------------- > > Key: TEIID-4629 > URL: https://issues.jboss.org/browse/TEIID-4629 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine, Server > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 9.2 > > > Based upon the work on TEIID-2578 we should first offer the ability to replace the vdb.xml with ddl. We can additionally include some of the work to represent additional pieces of the vdb as api level metadata objects (instead of in the admin layer) where possible. Ideally this should support as much alter functionality as possible. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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 January 2017