October 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4508) DDL procedure update count not handled correctly

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4508?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4508. ----------------------------------- Resolution: Done Normalized the handling. > DDL procedure update count not handled correctly > ------------------------------------------------ > > Key: TEIID-4508 > URL: https://issues.jboss.org/browse/TEIID-4508 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1, 9.0.5 > > > The handling for procedure.updateCount was based upon the index file logic that effectively needed to have 1 subtracted from the value. So when ddl specified 2, it was actually be interpreted as 1. The index metadata workaround needs to be moved and the rest of the handling needs to be made consistent. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4012) Implement XA transaction support for Teiid ODBC

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4012?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4012: --------------------------------------- To fully fix this is a bit larger than I would like, so initially we'll do TEIID-4513. The outline is that we need to use an XAConnection in the ODBC server logic rather than a regular connection. Then map the prepare/commit/rollback to the similar XAResource methods. This is complicated since the fixSQL logic expects to return string statements and also because we won't have a proper XAConnection start/end issued by the client - rather we'll just see the start transaction/commit and not know the xid. > Implement XA transaction support for Teiid ODBC > ----------------------------------------------- > > Key: TEIID-4012 > URL: https://issues.jboss.org/browse/TEIID-4012 > Project: Teiid > Issue Type: Feature Request > Components: ODBC > Affects Versions: 8.7.1.6_2 > Environment: Red Hat JBoss Data Virtualization 6.2.2 on EAP6.4.0 patched to version 6.4.5, > JBoss Developer Studio 8.1.0GA with Teiid Designer plugin 9.0.3.Final.v20150810-1438-B1157 > 64-bit Windows 7 environment > Reporter: Steve Tran > Assignee: Steven Hawkins > Fix For: 9.2 > > > Without XA support the pg client will hit the following error: > TEIID30020 Processing exception for request ... 'Group does not exist: pg_prepared_xacts' -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4012) Implement XA transaction support for Teiid ODBC

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4012?page=com.atlassian.jira.plugin... ] Work on TEIID-4012 stopped by Steven Hawkins. --------------------------------------------- > Implement XA transaction support for Teiid ODBC > ----------------------------------------------- > > Key: TEIID-4012 > URL: https://issues.jboss.org/browse/TEIID-4012 > Project: Teiid > Issue Type: Feature Request > Components: ODBC > Affects Versions: 8.7.1.6_2 > Environment: Red Hat JBoss Data Virtualization 6.2.2 on EAP6.4.0 patched to version 6.4.5, > JBoss Developer Studio 8.1.0GA with Teiid Designer plugin 9.0.3.Final.v20150810-1438-B1157 > 64-bit Windows 7 environment > Reporter: Steve Tran > Assignee: Steven Hawkins > Fix For: 9.2 > > > Without XA support the pg client will hit the following error: > TEIID30020 Processing exception for request ... 'Group does not exist: pg_prepared_xacts' -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4513) Create a dummy pg_prepared_xacts table

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4513: ------------------------------------- Summary: Create a dummy pg_prepared_xacts table Key: TEIID-4513 URL: https://issues.jboss.org/browse/TEIID-4513 Project: Teiid Issue Type: Sub-task Components: ODBC Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.2 We should provide a dummy table to prevent errors from recovery scans. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4507) Array index out of bounds exception with anon procedure and update count

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4507?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4507. ----------------------------------- Resolution: Done Updated the server and client handling to ensure backwards / forward fixing. > Array index out of bounds exception with anon procedure and update count > ------------------------------------------------------------------------ > > Key: TEIID-4507 > URL: https://issues.jboss.org/browse/TEIID-4507 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver, Query Engine > Affects Versions: 8.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1, 9.0.5 > > > If an anon procedure block that does not return a result set is executed and getUpdateCount is called, we'll throw an exception because the update count array will be empty. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4512) Issue with older drivers and useStreamsForLobs

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4512?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4512. ----------------------------------- Resolution: Done Checked if the length is an int value and called the older method. > Issue with older drivers and useStreamsForLobs > ---------------------------------------------- > > Key: TEIID-4512 > URL: https://issues.jboss.org/browse/TEIID-4512 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.1 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.2 > > > The newer JDBC 4 method with a long length is being called. Older drivers may have only implemented the method that supports an int length. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4512) Issue with older drivers and useStreamsForLobs

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4512: ------------------------------------- Summary: Issue with older drivers and useStreamsForLobs Key: TEIID-4512 URL: https://issues.jboss.org/browse/TEIID-4512 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 8.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.2 The newer JDBC 4 method with a long length is being called. Older drivers may have only implemented the method that supports an int length. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4509) Implement transaction detection for procedures

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4509?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4509. ----------------------------------- Resolution: Done Added logic in the instruction classes to determine if transactions are needed. > Implement transaction detection for procedures > ---------------------------------------------- > > Key: TEIID-4509 > URL: https://issues.jboss.org/browse/TEIID-4509 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.2 > > > Building on TEIID-4076 we should also detect when transactions are needed with virtual procedures. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4508) DDL procedure update count not handled correctly

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4508?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4508: ---------------------------------- Fix Version/s: 9.0.5 > DDL procedure update count not handled correctly > ------------------------------------------------ > > Key: TEIID-4508 > URL: https://issues.jboss.org/browse/TEIID-4508 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1, 9.0.5 > > > The handling for procedure.updateCount was based upon the index file logic that effectively needed to have 1 subtracted from the value. So when ddl specified 2, it was actually be interpreted as 1. The index metadata workaround needs to be moved and the rest of the handling needs to be made consistent. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4510) JDG Complex POJO 1-n relationship wrong results when joining parent and child table

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4510?page=com.atlassian.jira.plugin... ] Van Halbert edited comment on TEIID-4510 at 10/13/16 9:32 AM: -------------------------------------------------------------- Also, I did notice how you configured the "id" columns on the child tables. That column should not be selectable on the child. In order to get the ID, you must join with the parent object. If you use the import metadata option, that's the way it will be exposed. And from the unit test it has it defined as the following on the child tables: id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), This needs to be clear in the doc's if the metadata is to be manually created. was (Author: van.halbert): Also, I didn't notice how you configured the "id" columns on the child tables. That column should not be selectable on the child. In order to get the ID, you must join with the parent object. If you use the import metadata option, that's the way it will be exposed. And from the unit test it has it defined as the following on the child tables: id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE FALSE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), This needs to be clear in the doc's if the metadata is to be manually created. > JDG Complex POJO 1-n relationship wrong results when joining parent and child table > ----------------------------------------------------------------------------------- > > Key: TEIID-4510 > URL: https://issues.jboss.org/browse/TEIID-4510 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.6.6_3 > Reporter: Jan Stastny > Assignee: Van Halbert > Priority: Blocker > > When using infinispan-cache-dsl translator to access JDG cache incorrect results are returned for joins between the parent and child table. > POJO proto schema: > {code:plain} > package org.jboss.qe.jdg.remote.protobuf.complex; > /* @Indexed */ > message Person { > > /* @IndexedField(index=true, store=false) */ > required int32 id = 1; > /* @IndexedField */ > required string name = 2; > > /* @IndexedField */ > optional string email = 3; > > /* @IndexedField(index=true, store=false) */ > repeated PhoneNumber phones = 4; > /* @Indexed */ > message Address { > /* @IndexedField */ > required string Address = 1; > > /* @IndexedField(index=true, store=false) */ > required string City = 2; > > /* @IndexedField(index=true, store=false) */ > required string State = 3; > } > /* @IndexedField(index=true, store=false) */ > optional Address address = 5; > } > /* @Indexed */ > message PhoneNumber { > /* @IndexedField */ > required string number = 1; > } > {code} > Source metadata: > {code:sql} > CREATE FOREIGN TABLE Address ( > Address string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'address.Address', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > City string NOT NULL OPTIONS (NAMEINSOURCE 'address.City', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > State string NOT NULL OPTIONS (NAMEINSOURCE 'address.State', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE TRUE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'address') > ) OPTIONS (UPDATABLE TRUE); > CREATE FOREIGN TABLE Person ( > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > name string NOT NULL OPTIONS (NAMEINSOURCE 'name', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > email string OPTIONS (NAMEINSOURCE 'email', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > CONSTRAINT PK_ID PRIMARY KEY(id) > ) OPTIONS (UPDATABLE TRUE); > CREATE FOREIGN TABLE PhoneNumber ( > number string NOT NULL PRIMARY KEY OPTIONS (NAMEINSOURCE 'phones.number', SEARCHABLE 'Searchable', NATIVE_TYPE 'java.lang.String'), > id integer NOT NULL OPTIONS (NAMEINSOURCE 'id', SELECTABLE TRUE, SEARCHABLE 'Searchable', NATIVE_TYPE 'int'), > CONSTRAINT FK_PERSON FOREIGN KEY(id) REFERENCES Person (id) OPTIONS (NAMEINSOURCE 'phones') > ) OPTIONS (UPDATABLE TRUE); > {code} > Tested scenario: > {code:sql} > SELECT COUNT(*) FROM PhoneNumber WHERE id=1 > {code} > returns 2. > {code:sql} > SELECT COUNT(*) FROM Person p, PhoneNumber pn WHERE p.id=pn.id AND p.id=1 > {code} > or > {code:sql} > SELECT COUNT(*) FROM Person p INNER JOIN PhoneNumber pn ON p.id=pn.id WHERE p.id=1 > {code} > both return only 1. > NOTE: issue appears also when using only nested descriptors in the proto schema. -- 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