October 2017 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-3113) When creating VDB where new infinispan-hotrod translator, missing native metadata tag

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3113?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-3113: ----------------------------------- Fix Version/s: 11.1.1 > When creating VDB where new infinispan-hotrod translator, missing native metadata tag > ------------------------------------------------------------------------------------- > > Key: TEIIDDES-3113 > URL: https://issues.jboss.org/browse/TEIIDDES-3113 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 11.1.1 > Reporter: Van Halbert > Assignee: Barry LaFond > Priority: Blocker > Fix For: 11.1.1 > > > When a VDB is being created that contains a model that uses the new infinispan-hotrod translator, the created VDB is missing the following native tag: > <metadata type = "NATIVE"/> > The source model should contain 2 metadata entries, the following is an example: > {code} > <model name="People"> > <source connection-jndi-name="java:/infinispanPerson" name="infinispan" translator-name="infinispan-hotrod"/> > <metadata type = "DDL"><![CDATA[ > CREATE FOREIGN TABLE Person (id integer PRIMARY KEY, name varchar(100), salary double) OPTIONS(UPDATABLE true, "teiid_ispn:cache" 'personCache'); > ]]> > </metadata> > <metadata type = "NATIVE"/> > </model> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3113) When creating VDB where new infinispan-hotrod translator, missing native metadata tag

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3113?page=com.atlassian.jira.plu... ] Van Halbert commented on TEIIDDES-3113: --------------------------------------- The only work around that i can find is to export the VDB in xml format. Then manually edit the file and deploy that. > When creating VDB where new infinispan-hotrod translator, missing native metadata tag > ------------------------------------------------------------------------------------- > > Key: TEIIDDES-3113 > URL: https://issues.jboss.org/browse/TEIIDDES-3113 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 11.1.1 > Reporter: Van Halbert > Assignee: Barry LaFond > Priority: Blocker > > When a VDB is being created that contains a model that uses the new infinispan-hotrod translator, the created VDB is missing the following native tag: > <metadata type = "NATIVE"/> > The source model should contain 2 metadata entries, the following is an example: > {code} > <model name="People"> > <source connection-jndi-name="java:/infinispanPerson" name="infinispan" translator-name="infinispan-hotrod"/> > <metadata type = "DDL"><![CDATA[ > CREATE FOREIGN TABLE Person (id integer PRIMARY KEY, name varchar(100), salary double) OPTIONS(UPDATABLE true, "teiid_ispn:cache" 'personCache'); > ]]> > </metadata> > <metadata type = "NATIVE"/> > </model> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3062) Add support for Teiid DDL export to include dependent objects

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3062?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-3062: ---------------------------------------- This seems like a valid path to copy source DDL from one model (per project) into another > Add support for Teiid DDL export to include dependent objects > ------------------------------------------------------------- > > Key: TEIIDDES-3062 > URL: https://issues.jboss.org/browse/TEIIDDES-3062 > Project: Teiid Designer > Issue Type: Enhancement > Reporter: Tom Johnston > Fix For: Future > > Attachments: TeiidDES3062.jpg > > > It would be helpful that if when performing an Export at model level there would be an option on the following screen to include all supporting objects. > !image-2017-03-14-11-33-38-504.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3065) VDB Export to Import problem

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3065?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-3065: ---------------------------------------- [~sqtran] I'm pretty sure it's the quoting issue. Our DDL/VDB importer relies on Modeshape DDL Sequencing which is very specific on what and how it parses. > VDB Export to Import problem > ---------------------------- > > Key: TEIIDDES-3065 > URL: https://issues.jboss.org/browse/TEIIDDES-3065 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 10.1 > Environment: Windows 7 > JBoss Developer Studio 10.3.0.GA > Teiid Designer 10.1.0.GA > Reporter: Steve Tran > Attachments: Screenshot from 2017-03-21 13-29-38.png > > > I exported my VDB as a dynamic VDB file, then I attempted to re-import it but got an error message. > {code} > The message says "Unparsable table body". > !ENTRY org.teiid.designer.vdb 4 4 2017-03-21 13:28:40.629 > !MESSAGE An exception occurred while performing a VDB operation > !SUBENTRY 1 org.teiid.designer.vdb 4 0 2017-03-21 13:28:40.629 > !MESSAGE * Error Message: Unparsable table body > Error Line Number: 323 > Error Column Number: 42 > Error Index: 29455 > !ENTRY org.teiid.designer.vdb 4 4 2017-03-21 13:28:48.784 > !MESSAGE An exception occurred while performing a VDB operation > !SUBENTRY 1 org.teiid.designer.vdb 4 0 2017-03-21 13:28:48.784 > !MESSAGE * Error Message: Unparsable table body > Error Line Number: 323 > Error Column Number: 42 > Error Index: 29455 > !ENTRY org.teiid.designer.vdb 4 4 2017-03-21 13:35:15.660 > !MESSAGE An exception occurred while performing a VDB operation > !SUBENTRY 1 org.teiid.designer.vdb 4 0 2017-03-21 13:35:15.660 > !MESSAGE * Error Message: Unparsable table body > Error Line Number: 323 > Error Column Number: 42 > Error Index: 29455 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3070) Neon NPE in database explorer connect

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3070?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-3070: ---------------------------------------- [~don.krapohl] This issue needs more info. The eclipse log file would help indicate where the NPE occurred. I'd need more info in order to replicate the scenario/steps to replicate the error. > Neon NPE in database explorer connect > ------------------------------------- > > Key: TEIIDDES-3070 > URL: https://issues.jboss.org/browse/TEIIDDES-3070 > Project: Teiid Designer > Issue Type: Bug > Components: Eclipse Integration > Affects Versions: 11.0 > Environment: Version: Neon.3 Release (4.6.3) > Build id: 20170314-1500 > Windows > Reporter: Don Krapohl > Attachments: teiiddes-npe.png > > > In teiiddes, database development perspective, data source explorer frame, opening a connection by double-clicking or using the left-click "connect" context menu results in NPE. The connection is successful but an error occurs and the data source explorer frame does not show the subelements in the treeview under the connection. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3075) teiid designer fails to import excel file

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3075?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-3075. ------------------------------------ Assignee: Barry LaFond Resolution: Out of Date > teiid designer fails to import excel file > ----------------------------------------- > > Key: TEIIDDES-3075 > URL: https://issues.jboss.org/browse/TEIIDDES-3075 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 11.0.1 > Environment: JBoss Developer Studio 10.3.0 with teiid designer 11.0.1 on Linux > Reporter: Michael Echevarria > Assignee: Barry LaFond > Attachments: colors.xlsx > > > After importing an excel file, attempting to preview the data results in the following error: > Connector worker process failed for atomic-request=9241FCRcB/yA.0.0.1: org.teiid.translator.TranslatorException: TEIID23007 OPTIONS property CELL_NUMBER is required and it not defined on column ROW_ID -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3086) Issue when importing Flat files

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3086?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-3086. ------------------------------------ Assignee: Barry LaFond Resolution: Won't Do > Issue when importing Flat files > ------------------------------- > > Key: TEIIDDES-3086 > URL: https://issues.jboss.org/browse/TEIIDDES-3086 > Project: Teiid Designer > Issue Type: Bug > Components: Editors > Affects Versions: 11.0.1 > Environment: Teiid Version 8.12.10 > Reporter: Madou Coulibaly > Assignee: Barry LaFond > Attachments: editor1.png, editor2.png, execution.png, wizard.png > > > Several issues when importing CSV file using Teiid Designer > # Double quotes are added on the first fields of the file. (wizard.png) > # When we remove these double quotes from the Transformation Editor, we got a mapping error. (editor1.png) > # We are not able anymore to add double quotes (because of SQL validation and Auto-Syntax), we have to click on "Reconcile Transformation SQL with Target Columns" button and bind the missing field. This will have an alias with double quotes and add "ROW DELIMITER ';'" information. (editor2.png) > # After removing the "ROW DELIMITER ';'" information, we execute the query and we got another error "org.teiid.runtime.client.TeiidClientException: java.lang.RuntimeException: Remote org.teiid.core.TeiidProcessingException: TEIID30181 HEADER entry missing for column name airlinePartner in file:xxxx" > # We have to replace "HEADER" to "SKIP 1" to get a result (execution.png) but we still need to keep the alias with double quotes for the first field in the projection area. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3085) Importer is not setting Name In Source for salesforce relationship name

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3085?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-3085. ------------------------------------ Resolution: Won't Fix > Importer is not setting Name In Source for salesforce relationship name > ----------------------------------------------------------------------- > > Key: TEIIDDES-3085 > URL: https://issues.jboss.org/browse/TEIIDDES-3085 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 11.0.1 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: 11.0.3 > > > Salesforce importer doesn't set Name in Source for relationship name. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3105) Salesforce and file bad translators

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3105?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-3105: -------------------------------------- Assignee: Barry LaFond > Salesforce and file bad translators > ----------------------------------- > > Key: TEIIDDES-3105 > URL: https://issues.jboss.org/browse/TEIIDDES-3105 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 11.1 > Reporter: Mario Majernik > Assignee: Barry LaFond > Fix For: 11.1.1 > > Attachments: SFscreen.png > > > There is bad translator when I tried import using Teiid connection from salesforce. Should be there (SFscreen.png) salesforce-34 translator instead jdbc-ansi. > EDIT : // The same problem is with "file". Should be translator "file" but there is jdbc-ansi. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3105) Salesforce and file bad translators

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3105?page=com.atlassian.jira.plu... ] Barry LaFond edited comment on TEIIDDES-3105 at 10/4/17 2:39 PM: ----------------------------------------------------------------- master: https://github.com/Teiid-Designer/teiid-designer/commit/7655e3bf6af32404a... master: https://github.com/Teiid-Designer/teiid-designer/commit/d7b54f72d53169a19... (added infinispan-hotrod string check for driver match) was (Author: blafond): master: https://github.com/Teiid-Designer/teiid-designer/commit/7655e3bf6af32404a... > Salesforce and file bad translators > ----------------------------------- > > Key: TEIIDDES-3105 > URL: https://issues.jboss.org/browse/TEIIDDES-3105 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 11.1 > Reporter: Mario Majernik > Fix For: 11.1.1 > > Attachments: SFscreen.png > > > There is bad translator when I tried import using Teiid connection from salesforce. Should be there (SFscreen.png) salesforce-34 translator instead jdbc-ansi. > EDIT : // The same problem is with "file". Should be translator "file" but there is jdbc-ansi. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues October 2017