July 2015 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2248) Teiid Connection import fails to parse DDL when table contains VARCHAR column with DEFAULT value

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2248?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2248: --------------------------------------------------- Barry LaFond <blafond(a)redhat.com> changed the Status of [bug 1120073|https://bugzilla.redhat.com/show_bug.cgi?id=1120073] from NEW to MODIFIED > Teiid Connection import fails to parse DDL when table contains VARCHAR column with DEFAULT value > ------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-2248 > URL: https://issues.jboss.org/browse/TEIIDDES-2248 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Teiid Integration > Affects Versions: 8.3.3 > Environment: Teiid Designer 8.3.3 > Teiid 8.4.1-redhat-7 > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Fix For: 9.2, 9.0.3 > > Attachments: screen-1.png > > > Create a table with > {code:sql} > CREATE TABLE t1 ( c1 VARCHAR(10) DEFAULT 'c1' ) > {code} > When trying to import it through Teiid Connection Importer, the importer DDL is shown as > {code:sql} > CREATE FOREIGN TABLE "dballo00.dbo.t1" ( > c1 string(10) DEFAULT '(''c1'')' OPTIONS (NAMEINSOURCE '"c1"', NATIVE_TYPE 'varchar') > ) OPTIONS (NAMEINSOURCE '"dballo00"."dbo"."t1"', UPDATABLE TRUE, CARDINALITY 0); > {code} > but on the next page, the following error is shown (see screenshot): > The DDL failed to parse with message: "Unparsable table body". -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2248) Teiid Connection import fails to parse DDL when table contains VARCHAR column with DEFAULT value

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2248?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2248: ----------------------------------- Fix Version/s: 9.0.3 > Teiid Connection import fails to parse DDL when table contains VARCHAR column with DEFAULT value > ------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-2248 > URL: https://issues.jboss.org/browse/TEIIDDES-2248 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Teiid Integration > Affects Versions: 8.3.3 > Environment: Teiid Designer 8.3.3 > Teiid 8.4.1-redhat-7 > Reporter: Andrej Šmigala > Assignee: Dan Florian > Fix For: 9.2, 9.0.3 > > Attachments: screen-1.png > > > Create a table with > {code:sql} > CREATE TABLE t1 ( c1 VARCHAR(10) DEFAULT 'c1' ) > {code} > When trying to import it through Teiid Connection Importer, the importer DDL is shown as > {code:sql} > CREATE FOREIGN TABLE "dballo00.dbo.t1" ( > c1 string(10) DEFAULT '(''c1'')' OPTIONS (NAMEINSOURCE '"c1"', NATIVE_TYPE 'varchar') > ) OPTIONS (NAMEINSOURCE '"dballo00"."dbo"."t1"', UPDATABLE TRUE, CARDINALITY 0); > {code} > but on the next page, the following error is shown (see screenshot): > The DDL failed to parse with message: "Unparsable table body". -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-303) Materialization can fail when MMX passes back data that exceeds the maximum length, as defined in the materialized model.

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-303?page=com.atlassian.jira.plug... ] Barry LaFond closed TEIIDDES-303. --------------------------------- Assignee: Barry LaFond (was: Van Halbert) > Materialization can fail when MMX passes back data that exceeds the maximum length, as defined in the materialized model. > ------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-303 > URL: https://issues.jboss.org/browse/TEIIDDES-303 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.1 > Environment: Windows 2003 Server, 5.5 + patch 62 > Reporter: Michael Walker > Assignee: Barry LaFond > Labels: materialization > Fix For: 9.0.3 > > > When querying data from a source model, MMX allows data to exceed the model's length restrictions. For example, a SalesForce model might have a column called "biography:string(200)". Querying data from this column can sometimes result in a string that exceeds 200 characters, and MMX does not truncate the data. > This causes problems when you attempt to materialize the model. Since the create table scripts are based on the model definition, the mat view table will not accommodate data that exceeds the length restrictions. Following the previous example, this means that the biography data will raise a "inserted length too large for column" error, causing the rest of the materialization to fail. > The new materialization process will need to account for this issue, or perhaps MMX should truncate data that exceeds the defined length found within the model. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-303) Materialization can fail when MMX passes back data that exceeds the maximum length, as defined in the materialized model.

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-303?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-303. ----------------------------------- Resolution: Out of Date > Materialization can fail when MMX passes back data that exceeds the maximum length, as defined in the materialized model. > ------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-303 > URL: https://issues.jboss.org/browse/TEIIDDES-303 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.1 > Environment: Windows 2003 Server, 5.5 + patch 62 > Reporter: Michael Walker > Assignee: Van Halbert > Labels: materialization > Fix For: 9.0.3 > > > When querying data from a source model, MMX allows data to exceed the model's length restrictions. For example, a SalesForce model might have a column called "biography:string(200)". Querying data from this column can sometimes result in a string that exceeds 200 characters, and MMX does not truncate the data. > This causes problems when you attempt to materialize the model. Since the create table scripts are based on the model definition, the mat view table will not accommodate data that exceeds the length restrictions. Following the previous example, this means that the biography data will raise a "inserted length too large for column" error, causing the rest of the materialization to fail. > The new materialization process will need to account for this issue, or perhaps MMX should truncate data that exceeds the defined length found within the model. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2217) TEIID30183 Message:TEIID30183 Text parse error: Non-whitespace character found between the qualifier and the delimiter in text line 16, 161 in Unknown. SQLState: TEIID30183

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2217?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2217: ----------------------------------- Fix Version/s: 9.3 (was: 9.2) (was: 9.0.3) > TEIID30183 Message:TEIID30183 Text parse error: Non-whitespace character found between the qualifier and the delimiter in text line 16,161 in Unknown. SQLState: TEIID30183 > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2217 > URL: https://issues.jboss.org/browse/TEIIDDES-2217 > Project: Teiid Designer > Issue Type: Quality Risk > Reporter: luca gioppo > Priority: Minor > Fix For: 9.3 > > > On the same use case of TEIID30181 I now got the error in object: > TEIID30183 Message:TEIID30183 Text parse error: Non-whitespace character found between the qualifier and the delimiter in text line 16,161 in Unknown. > SQLState: TEIID30183 > the row should be: > istsc_pgee021002 Direzione Didattica Statale "Franco Rasetti" Castiglione del Lago ANTONIETTA MANNUCCI 06061 PG Umbria www.dirclago.it Via Carducci, 25 Dirigente Scolastico Istituti di Istruzione Statale di Ogni Ordine e Grado Pubbliche Amministrazioni S 80005650546 pgee021002(a)pec.istruzione.it pec pgee021002(a)istruzione.it altro null null null null null null 0 > the only difference I find between the previous rows that passed without problems is that a field has double quote in its content. > The delimiter is tabulation so there should not be any problem. > Could it be this the problem and how to solve it? > Thanks -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2525) Reproducing 'Import Data from REST Services' from documentation not working

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2525?page=com.atlassian.jira.plu... ] Ted Jones commented on TEIIDDES-2525: ------------------------------------- The project docs are up to date. See http://docs.jboss.org/teiid/designer/9.1/user-guide/en-US/html_single/#re... The product docs should be updated accordingly. > Reproducing 'Import Data from REST Services' from documentation not working > --------------------------------------------------------------------------- > > Key: TEIIDDES-2525 > URL: https://issues.jboss.org/browse/TEIIDDES-2525 > Project: Teiid Designer > Issue Type: Bug > Components: Documentation > Affects Versions: 9.0.1, 9.0.2 Beta2 > Environment: Windows 7, JBoss Developer Studio 8.1 > Reporter: Daan Creemers > Assignee: David Le Sage > Fix For: 9.0.3 > > > Reproducing the steps of the documentation 'Import Data from REST Services' (https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Data_Virtuali...) does not work. The documentation is saying you should select 'REST Web Services URL' when choosing a Connection Profile Type for a new Connection Profile, but this type is not available. Only 'XML File URL Source' is available. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2525) Reproducing 'Import Data from REST Services' from documentation not working

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2525?page=com.atlassian.jira.plu... ] Ted Jones reassigned TEIIDDES-2525: ----------------------------------- Assignee: David Le Sage (was: Ted Jones) > Reproducing 'Import Data from REST Services' from documentation not working > --------------------------------------------------------------------------- > > Key: TEIIDDES-2525 > URL: https://issues.jboss.org/browse/TEIIDDES-2525 > Project: Teiid Designer > Issue Type: Bug > Components: Documentation > Affects Versions: 9.0.1, 9.0.2 Beta2 > Environment: Windows 7, JBoss Developer Studio 8.1 > Reporter: Daan Creemers > Assignee: David Le Sage > Fix For: 9.0.3 > > > Reproducing the steps of the documentation 'Import Data from REST Services' (https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Data_Virtuali...) does not work. The documentation is saying you should select 'REST Web Services URL' when choosing a Connection Profile Type for a new Connection Profile, but this type is not available. Only 'XML File URL Source' is available. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2447) Failed to import SalesForce Metadata

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2447?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2447. ------------------------------------ Fix Version/s: (was: 9.2) Resolution: Done > Failed to import SalesForce Metadata > ------------------------------------ > > Key: TEIIDDES-2447 > URL: https://issues.jboss.org/browse/TEIIDDES-2447 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Priority: Blocker > Fix For: 9.0.3 > > Attachments: sfddl (1).ddl > > > Using the Teiid Connection import, the attached DDL has been retrived from salesforce instance. However Designer fails to import it, and gives NO clue as to what is wrong. > 1) The DDL should be successfully imported > 2) When there is something wrong that Designer does not understand it needs to give a meaningful error, as per the location of the file and context -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2447) Failed to import SalesForce Metadata

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2447?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2447: ---------------------------------------- Upgraded jars via TEIIDDES-2580. Tested Import Teiid DDL file with the following content and the pick-list values seemed to be in order. {code} CREATE FOREIGN TABLE FlintStones ( RejectionReason__c string(255) OPTIONS (NATIVE_TYPE 'picklist', "teiid_sf:calculated" 'false', "teiid_sf:Custom" 'true', "teiid_sf:Defaulted on Create" 'false', "teiid_sf:Picklist Values" '0.00 Amount not approved,Backdate Subsc Start-date,Billing/Shipping Info Missing,Billing Account Number Invalid,Billing Acct/Info Incorrect/Missing,Billing Address Incorrect,Billing Address Missing,Contract Incorrect/Missing/Unsigned,Contract Missing/Not Signed,Contract Numbers Incorrect,Contract Numbers Missing,Co-Terms Info Incorrect/Missing,Credit Card Declined,Credit Related/Payment Terms Issues,Credit Status/Payment Terms Issues,Customer Hold or Delivery Delay,Cut-Off Time Exceeded,Description Missing,Discount Not Approved,Duplicate Order,EU Login Incorrect/Missing,Finance Approval Required,Handwritten Change Not Acceptable,Incorrect Account Classification,Incorrect SKUs,Invalid RH Entitlement Login,Legal/BD Review & Approval,Legal Agreement not attached / Missing,Legal Approval,Legal Approval Required,Legal Entity Not Correct,Login/Acct # Invalid/Missing,Missing Pages,Missing Reference to Existing Agreement,Missing Signatures,Missing SKUs,New Party / Account Request,No PO Letter needs Approval,No PO Letter Required,Other,Payment Terms Missing,Payment Terms Not Approved,PO/Credit Card Info Incorrect/Missing,PO Missing,PO not attached / missing,Pricing Incorrect,Product/Discount Approval Required,Qty/Price/Products Not Equal,Renewal Dates are Incorrect/Missing,Renewal Info/Start Date Needed,Renewal Information Incorrect/Missing,Sales Mgmt or PM Approval Required,Shipping Address Incorrect,Shipping Address Missing,Shipping Info Incorrect/Missing,SKU/Qty/Currency/Price Incorrect,SKU Qty/Price/Desc Issue,Start/End Date Missing,Start Date Over 14 Days Old,Subsc Dates/Term Issue,Tax Info Missing/Incorrect,Unclear - Auto entitlement Vs Keys,VAT # Missing/Incorrect,VAT number missing/incorrect,Waiting Saba # or CM# or Others'' Info,Wrong Billing Acct#,Wrong Currency'), OMComments__c string(255) OPTIONS (SEARCHABLE 'Unsearchable', NATIVE_TYPE 'textarea', "teiid_sf:calculated" 'false', "teiid_sf:Custom" 'true', "teiid_sf:Defaulted on Create" 'false') ); {code} > Failed to import SalesForce Metadata > ------------------------------------ > > Key: TEIIDDES-2447 > URL: https://issues.jboss.org/browse/TEIIDDES-2447 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Priority: Blocker > Fix For: 9.0.3 > > Attachments: sfddl (1).ddl > > > Using the Teiid Connection import, the attached DDL has been retrived from salesforce instance. However Designer fails to import it, and gives NO clue as to what is wrong. > 1) The DDL should be successfully imported > 2) When there is something wrong that Designer does not understand it needs to give a meaningful error, as per the location of the file and context -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2525) Reproducing 'Import Data from REST Services' from documentation not working

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2525?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-2525: -------------------------------------- Assignee: Ted Jones (was: David Le Sage) > Reproducing 'Import Data from REST Services' from documentation not working > --------------------------------------------------------------------------- > > Key: TEIIDDES-2525 > URL: https://issues.jboss.org/browse/TEIIDDES-2525 > Project: Teiid Designer > Issue Type: Bug > Components: Documentation > Affects Versions: 9.0.1, 9.0.2 Beta2 > Environment: Windows 7, JBoss Developer Studio 8.1 > Reporter: Daan Creemers > Assignee: Ted Jones > Fix For: 9.0.3 > > > Reproducing the steps of the documentation 'Import Data from REST Services' (https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Data_Virtuali...) does not work. The documentation is saying you should select 'REST Web Services URL' when choosing a Connection Profile Type for a new Connection Profile, but this type is not available. Only 'XML File URL Source' is available. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues July 2015