January 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4714) Google translator allows to be inserted duplicate key

by Lucie Fabrikova (JIRA)

Lucie Fabrikova created TEIID-4714: -------------------------------------- Summary: Google translator allows to be inserted duplicate key Key: TEIID-4714 URL: https://issues.jboss.org/browse/TEIID-4714 Project: Teiid Issue Type: Bug Affects Versions: 9.2 Reporter: Lucie Fabrikova Assignee: Steven Hawkins Attachments: googlespreadsheetcrud-vdb.xml It is possible to insert duplicate key, e.g. by running following query multiple times: INSERT INTO SmallA (IntKey, StringKey) VALUES (1, '1') -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4713) HANA translator evaluates > as >=

by Lucie Fabrikova (JIRA)

Lucie Fabrikova created TEIID-4713: -------------------------------------- Summary: HANA translator evaluates > as >= Key: TEIID-4713 URL: https://issues.jboss.org/browse/TEIID-4713 Project: Teiid Issue Type: Bug Affects Versions: 9.2 Reporter: Lucie Fabrikova Assignee: Steven Hawkins Attachments: sap-hana_crud-vdb.xml HANA translator evaluates > as >= in following query: DELETE FROM SmallA WHERE FloatNum > 11814.4 I observed rows where FloatNum = 11814.4 were also deleted. Next observations: - query DELETE FROM SmallA WHERE FloatNum = 11814.4 deleted no rows. - <= was evaluated as < -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4712) Google translator throws exception for DELETE where <>

by Lucie Fabrikova (JIRA)

Lucie Fabrikova created TEIID-4712: -------------------------------------- Summary: Google translator throws exception for DELETE where <> Key: TEIID-4712 URL: https://issues.jboss.org/browse/TEIID-4712 Project: Teiid Issue Type: Bug Affects Versions: 9.2 Reporter: Lucie Fabrikova Assignee: Steven Hawkins Attachments: googlespreadsheetcrud-vdb.xml, server.log Google translator throws exception "Invalid query parameter value for sq." for query DELETE FROM smalla WHERE col <> colValue (see attachment - server log after running query "delete from smalla where shortvalue <> 5303") I observed the exception is thrown for all types. Next, I observed following behavior for operator <>: - for datatypes double, float, bigdecimal, timestamp: SELECT returns no rows, UPDATE affects no rows -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[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 reopened TEIID-4298: --------------------------------- > 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)

9 years, 2 months

1
0
0 / 0

[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 updated TEIID-4298: -------------------------------- Fix Version/s: 9.1.3 > 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)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4703) The Oracle translator did not limit the number of values in "IN" clause, which were required by Oracle database.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4703?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4703. ----------------------------------- Resolution: Incomplete Description We'll need more details to confirm what you are seeing. In particular how you configured the translator and the user query. > The Oracle translator did not limit the number of values in "IN" clause, which were required by Oracle database. > ---------------------------------------------------------------------------------------------------------------- > > Key: TEIID-4703 > URL: https://issues.jboss.org/browse/TEIID-4703 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.13.4 > Reporter: SHI HONG CHIN > Assignee: Steven Hawkins > > Database: Oracle + Firebird + Microsoft SQL Server. > Oracle limit the maximum number of values in "IN" clause to 1000. > In teiid, I am using the built-in Oracle translator. > When running some SQL queries, Oracle database reported an error "No more data to read from socket". I had set the log level of Teiid to "ALL". According to the WildFly log files, Teiid executed a query with more than 10000 values in the "IN" clause. > I tried to copy the whole SQL from WildFly log file into Oracle SQL Developer and execute it, the same error occurred. Then, I tried to edit the query by delete many values from the "IN" clause and then run the query again, and the query success. > For teiid, as a workaround, I overrided the oracle translator and set the property of "MaxInCriteriaSize" to 50. After that, all SQL queries run success without any issue. > I suggest that, by default, the built-in Oracle translator limit the number of values in "IN" clause to maximum 1000 values, and this behavior can be changed through properties. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3952) Update to updatable internal materialized view should update the materialized view as well as the database

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3952?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3952: --------------------------------------- The initial commit is in. It takes a rewrite approach, rather than adding a new plan forms / moving logic into the optimizer. With a MATVIEW_WRITE_THROUGH extension boolean a materialized view will have updates written both to the target table and have view level operation called as well. Initially this is implemented differently for internal and external. External will issue the same update as what is targeting the view to the materialization target table. Internal will determine a primary key set and use the refreshMatViewRow procedure. The latter is a safer, but more costly, approach in that you are effectively checking that the values will conform to the view. If needed we can have external operate in this manner as well. There is also potentially more tweaks that could be made to the rewrites based upon checks of the materialization validity. > Update to updatable internal materialized view should update the materialized view as well as the database > ---------------------------------------------------------------------------------------------------------- > > Key: TEIID-3952 > URL: https://issues.jboss.org/browse/TEIID-3952 > Project: Teiid > Issue Type: Enhancement > Components: VDB > Affects Versions: 8.7 > Environment: Red Hat JBoss Data Virtualization 6.2 based on Teiid 8.7.x > Reporter: Andy Yuen > Assignee: Steven Hawkins > Labels: jboss > Fix For: 9.2 > > > Updating an updatable internal materized view updates the database but not the materialized view at present. The requested enhancement is that they, both, should be updated. > Setup > Client - SquirrelSQL to access JDV > JDV 6.2 - with an updatable nternal materialized view of one table from the data source > Data Source - just one data source: MySQL > I can see from the console that the target table/view has been materialized > Then I did the following: > 1) select a row from the materialized table > 2) update a field in a row in the materialized view > 3) select that row (value unchanged ie, same as int 1) - tried multiple times > 4) issue EXEC SYSADMIN.refreshMatViewRow(...) using primary key for the row that has been changed > 5) select that row (value unchanged) - now I can see the changed data > This behaviour is counter-intuitive because I was expecting that since it is an updatable materialized view, my change will write through the materialized view ie, change both the materialized view as well as the database. But in this case, it changed the database and not the materialized view? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3624) No way to associate enterprise data types in dynamic vdb constructs

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3624?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3624: --------------------------------------- This issue will add syntax to support simple type aliasing. The alias name should then be usable in the transformation. We'll also see how much affect this should have in the system/jdbc metadata. > No way to associate enterprise data types in dynamic vdb constructs > ------------------------------------------------------------------- > > Key: TEIID-3624 > URL: https://issues.jboss.org/browse/TEIID-3624 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 9.2 > > > I don't find any doc's on how to define enterprise data types in a dynamic vdb. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4711) Add multiple operator supports to Impala translator (case insensitive ilike, iregex, etc))

by Don Krapohl (JIRA)

Don Krapohl created TEIID-4711: ---------------------------------- Summary: Add multiple operator supports to Impala translator (case insensitive ilike, iregex, etc)) Key: TEIID-4711 URL: https://issues.jboss.org/browse/TEIID-4711 Project: Teiid Issue Type: Feature Request Components: JDBC Connector Affects Versions: 9.1.1 Reporter: Don Krapohl Assignee: Steven Hawkins Per https://www.cloudera.com/documentation/enterprise/5-8-x/topics/impala_ope... Impala post-2.5 supports several operations that should be pushed down. As a user I would like to be able to use the following SQL operations and have them pushed down in my queries using the Impala translator: ILIKE IREGEXP IS DISTINCT FROM RLIKE -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4710) Request id conflict with CommandContext connection

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4710?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4710. ----------------------------------- Resolution: Done Changed internal statements to generate random negative request ids and added a sanity check to make sure we are not inadvertently allowing a duplicate id. > Request id conflict with CommandContext connection > -------------------------------------------------- > > Key: TEIID-4710 > URL: https://issues.jboss.org/browse/TEIID-4710 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0.6, 9.2, 9.1.3 > > > When using the connection from the command context it executes within the context of the current session - but is not ensuring non-conflicting request ids are being used. This means that the current execution can be replaced or seemingly closed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2017