May 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2961) TEIID60016 Duplicate Column with h2 database

by Kenichi Takemura (JIRA)

[ https://issues.jboss.org/browse/TEIID-2961?page=com.atlassian.jira.plugin... ] Kenichi Takemura commented on TEIID-2961: ----------------------------------------- Hi I see sessions from both INFORMATION_SCHEMA and PUBLIC are list. 1: INFORMATION_SCHEMA SESSIONS (1) 2: INFORMATION_SCHEMA SESSIONS (2) 3: INFORMATION_SCHEMA SESSIONS (3) 4: INFORMATION_SCHEMA SESSIONS (4) 5: INFORMATION_SCHEMA SESSIONS (5) 6: INFORMATION_SCHEMA SESSIONS (6) 7: PUBLIC SESSIONS (1) 8: PUBLIC SESSIONS (2) 9: PUBLIC SESSIONS (3) 10: PUBLIC SESSIONS (4) 11: PUBLIC SESSIONS (5) 12: PUBLIC SESSIONS (6) 13: PUBLIC SESSIONS (7) 14: PUBLIC SESSIONS (8) 15: PUBLIC SESSIONS (9) 16: PUBLIC SESSIONS (10) 17: PUBLIC SESSIONS (11) > TEIID60016 Duplicate Column with h2 database > -------------------------------------------- > > Key: TEIID-2961 > URL: https://issues.jboss.org/browse/TEIID-2961 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7 > Reporter: Kenichi Takemura > Assignee: Steven Hawkins > > I am trying to deploy a vdb.xml that has a physical datasouce with h2 translator. Teiid fails to deploy it with error 'TEIID60016 Duplicate Column'. > Source database has a table that is 'sessions'. It seems getMetadata() from h2 database returns more columns for sessions table(user database + metadata for h2 itself?). > It getting Duplicated 'ID' columns. > On production we use mysql but on our test we want to use h2. > Is this a bug in Teiid? > Is there any workaround? -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2961) TEIID60016 Duplicate Column with h2 database

by Kenichi Takemura (JIRA)

[ https://issues.jboss.org/browse/TEIID-2961?page=com.atlassian.jira.plugin... ] Kenichi Takemura updated TEIID-2961: ------------------------------------ Description: I am trying to deploy a vdb.xml that has a physical datasouce with h2 translator. Teiid fails to deploy it with error 'TEIID60016 Duplicate Column'. Source database has a table that is 'sessions'. It seems getMetadata() from h2 database returns more columns for sessions table(user database + metadata for h2 itself?). It getting Duplicated 'ID' columns. On production we use mysql but on our test we want to use h2. Is this a bug in Teiid? Is there any workaround? was: I am trying to deploy a vdb.xml that has a physical datasouce with h2 translator. Teiid fails to deploy it with error 'TEIID60016 Duplicate Column with h2 database' (Cannot import) Source database has a table that is 'sessions'. It seems getMetadata() from h2 database returns more columns for sessions table(user database + metadata for h2 itself?). It getting Duplicated 'ID' columns. On production we use mysql but on our test we want to use h2. Is this a bug in Teiid? Is there any workaround? > TEIID60016 Duplicate Column with h2 database > -------------------------------------------- > > Key: TEIID-2961 > URL: https://issues.jboss.org/browse/TEIID-2961 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7 > Reporter: Kenichi Takemura > Assignee: Steven Hawkins > > I am trying to deploy a vdb.xml that has a physical datasouce with h2 translator. Teiid fails to deploy it with error 'TEIID60016 Duplicate Column'. > Source database has a table that is 'sessions'. It seems getMetadata() from h2 database returns more columns for sessions table(user database + metadata for h2 itself?). > It getting Duplicated 'ID' columns. > On production we use mysql but on our test we want to use h2. > Is this a bug in Teiid? > Is there any workaround? -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2961) TEIID60016 Duplicate Column with h2 database

by Kenichi Takemura (JIRA)

Kenichi Takemura created TEIID-2961: --------------------------------------- Summary: TEIID60016 Duplicate Column with h2 database Key: TEIID-2961 URL: https://issues.jboss.org/browse/TEIID-2961 Project: Teiid Issue Type: Bug Affects Versions: 8.7 Reporter: Kenichi Takemura Assignee: Steven Hawkins I am trying to deploy a vdb.xml that has a physical datasouce with h2 translator. Teiid fails to deploy it with error 'TEIID60016 Duplicate Column with h2 database' (Cannot import) Source database has a table that is 'sessions'. It seems getMetadata() from h2 database returns more columns for sessions table(user database + metadata for h2 itself?). It getting Duplicated 'ID' columns. On production we use mysql but on our test we want to use h2. Is this a bug in Teiid? Is there any workaround? -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2954) support older designer metadata for ws translator invoke

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2954?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2954. ----------------------------------- Resolution: Done Changed the logic to also support the version that uses an out instead of a return parameter. > support older designer metadata for ws translator invoke > -------------------------------------------------------- > > Key: TEIID-2954 > URL: https://issues.jboss.org/browse/TEIID-2954 > Project: Teiid > Issue Type: Quality Risk > Components: Misc. Connectors > Affects Versions: 8.2 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.8 > > > Desinger modeled the invoke procedure with the result as an out parameter rather than a return, which was not accounted for with TEIID-2268 > The workaround is to modify the invoke procedure metadata so that the result is a return parameter. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2960) Class cast exception with source batched update command

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2960?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2960. ----------------------------------- Resolution: Done Corrected the check to use the command parameter. > Class cast exception with source batched update command > ------------------------------------------------------- > > Key: TEIID-2960 > URL: https://issues.jboss.org/browse/TEIID-2960 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.8 > > > A source batched update command will cause: > Caused by: java.lang.ClassCastException: org.teiid.query.sql.lang.BatchedUpdateCommand cannot be cast to org.teiid.query.sql.lang.ProcedureContainer > at org.teiid.dqp.internal.process.DataTierTupleSource.checkForUpdates(DataTierTupleSource.java:223) > at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:148 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2960) Class cast exception with source batched update command

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2960: ------------------------------------- Summary: Class cast exception with source batched update command Key: TEIID-2960 URL: https://issues.jboss.org/browse/TEIID-2960 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.7 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.7.1, 8.8 A source batched update command will cause: Caused by: java.lang.ClassCastException: org.teiid.query.sql.lang.BatchedUpdateCommand cannot be cast to org.teiid.query.sql.lang.ProcedureContainer at org.teiid.dqp.internal.process.DataTierTupleSource.checkForUpdates(DataTierTupleSource.java:223) at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:148 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2959) Revert Salesforce DDL Option keys

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2959?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-2959: -------------------------------- Fix Version/s: 8.7.1 8.8 > Revert Salesforce DDL Option keys > --------------------------------- > > Key: TEIID-2959 > URL: https://issues.jboss.org/browse/TEIID-2959 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.7 > Reporter: Mark Drilling > Assignee: Ramesh Reddy > Fix For: 8.7.1, 8.8 > > > The OPTION keys for Salesforce DDL changed going from 8.6 to 8.7. Example below. > ================= > 8.6 version > CONSTRAINT Id_PK PRIMARY KEY(Id), > CONSTRAINT FK_ApexPage_ScontrolId FOREIGN KEY(ScontrolId) REFERENCES ApexPage > ) OPTIONS (UPDATABLE TRUE, Custom 'false', "Supports Create" 'true', "Supports Delete" 'true', "Supports Merge" 'false', "Supports Query" 'true', "Supports Replicate" 'true', "Supports Retrieve" 'true', "Supports Search" 'false'); > ================= > 8.7 version > CONSTRAINT Id_PK PRIMARY KEY(Id), > CONSTRAINT FK_ApexPage_ScontrolId FOREIGN KEY(ScontrolId) REFERENCES importVDBSrcModel.ApexPage (Id) > ) OPTIONS (UPDATABLE TRUE, custom 'false', supportsCreate 'true', supportsDelete 'true', supportsMerge 'false', supportsQuery 'true', supportsReplicate 'true', supportsRetrieve 'true', supportsSearch 'false'); > ================= -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2959) Revert Salesforce DDL Option keys

by Mark Drilling (JIRA)

Mark Drilling created TEIID-2959: ------------------------------------ Summary: Revert Salesforce DDL Option keys Key: TEIID-2959 URL: https://issues.jboss.org/browse/TEIID-2959 Project: Teiid Issue Type: Bug Components: AdminApi Affects Versions: 8.7 Reporter: Mark Drilling Assignee: Ramesh Reddy The OPTION keys for Salesforce DDL changed going from 8.6 to 8.7. Example below. ================= 8.6 version CONSTRAINT Id_PK PRIMARY KEY(Id), CONSTRAINT FK_ApexPage_ScontrolId FOREIGN KEY(ScontrolId) REFERENCES ApexPage ) OPTIONS (UPDATABLE TRUE, Custom 'false', "Supports Create" 'true', "Supports Delete" 'true', "Supports Merge" 'false', "Supports Query" 'true', "Supports Replicate" 'true', "Supports Retrieve" 'true', "Supports Search" 'false'); ================= 8.7 version CONSTRAINT Id_PK PRIMARY KEY(Id), CONSTRAINT FK_ApexPage_ScontrolId FOREIGN KEY(ScontrolId) REFERENCES importVDBSrcModel.ApexPage (Id) ) OPTIONS (UPDATABLE TRUE, custom 'false', supportsCreate 'true', supportsDelete 'true', supportsMerge 'false', supportsQuery 'true', supportsReplicate 'true', supportsRetrieve 'true', supportsSearch 'false'); ================= -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2958) MongoDB: Put nested JSON documents in one single table

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2958?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-2958: ----------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) > MongoDB: Put nested JSON documents in one single table > ------------------------------------------------------- > > Key: TEIID-2958 > URL: https://issues.jboss.org/browse/TEIID-2958 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.7 > Environment: MongoDB with Teiid > Reporter: Ivan Chan > Assignee: Ramesh Reddy > Labels: teiid > > Currently, it seems like ID needs to be appear in parent and child for nested documents. But it is unlikely a case for MongoDB customers. It would be nice if Teiid can flatten out data in one single table. Therefore, users would not need to insert parent id in the child document in order for Teiid to work. > I am thinking the following case. For example I have a JSON object like this: > > Customer > { > _id: 1374932, > FirstName: "John", > LastName: "Doe", > Address: > { > _id: 43839430, > Street: "123 Lane", > City: "New York", > State: "NY", > Zipcode: "12345" > } > } > > In this case, customer._id doesn't exist inside Address. There is no way to do join in regular SQL fashion. But it would be nice if teiid can put the column from parent and child into a single table. Maybe something similar to the following schema: > CREATE FOREIGN TABLE Customer ( > CustomerId integer PRIMARY KEY, > FirstName varchar(25), > LastName varchar(25), > address__id integer, > address_Street varchar(50), > address_City varchar(25), > address_State varchar(25), > address_Zipcode varchar(6), > ) OPTIONS(UPDATABLE 'TRUE'); -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2958) MongoDB: Put nested JSON documents in one single table

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2958?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2958: ------------------------------------- The enhancement I asked to log is to remove the need to add customer id in the address nested document. The above in only issue when dealing with the importing metadata from existing documents in the mongodb. However, the prior issue needs to be solved before this can be considered > MongoDB: Put nested JSON documents in one single table > ------------------------------------------------------- > > Key: TEIID-2958 > URL: https://issues.jboss.org/browse/TEIID-2958 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.7 > Environment: MongoDB with Teiid > Reporter: Ivan Chan > Assignee: Steven Hawkins > Labels: teiid > > Currently, it seems like ID needs to be appear in parent and child for nested documents. But it is unlikely a case for MongoDB customers. It would be nice if Teiid can flatten out data in one single table. Therefore, users would not need to insert parent id in the child document in order for Teiid to work. > I am thinking the following case. For example I have a JSON object like this: > > Customer > { > _id: 1374932, > FirstName: "John", > LastName: "Doe", > Address: > { > _id: 43839430, > Street: "123 Lane", > City: "New York", > State: "NY", > Zipcode: "12345" > } > } > > In this case, customer._id doesn't exist inside Address. There is no way to do join in regular SQL fashion. But it would be nice if teiid can put the column from parent and child into a single table. Maybe something similar to the following schema: > CREATE FOREIGN TABLE Customer ( > CustomerId integer PRIMARY KEY, > FirstName varchar(25), > LastName varchar(25), > address__id integer, > address_Street varchar(50), > address_City varchar(25), > address_State varchar(25), > address_Zipcode varchar(6), > ) OPTIONS(UPDATABLE 'TRUE'); -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2014