November 2017 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2683) Importing Excel file using Teiid Connection does not import extension properties

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2683?page=com.atlassian.jira.plu... ] Barry LaFond reopened TEIIDDES-2683: ------------------------------------ > Importing Excel file using Teiid Connection does not import extension properties > -------------------------------------------------------------------------------- > > Key: TEIIDDES-2683 > URL: https://issues.jboss.org/browse/TEIIDDES-2683 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 9.0.4 > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Fix For: 11.1, 11.1.1 > > Attachments: excel-import-problem.mkv > > > When importing an excel file using Teiid Connection, the extension properties are silently discarded. This results in invalid model, which, when deployed and queried, causes the following error in the server log: > bq. Connector worker process failed for atomic-request=AVU37BnZoOUS.0.0.0: org.teiid.translator.TranslatorException: TEIID23007 OPTIONS property CELL_NUMBER is required and it not defined on column ROW_ID > The DDL obtained from the server is > {code:sql} > SET NAMESPACE 'http://www.teiid.org/translator/excel/2014' AS teiid_excel; > CREATE FOREIGN TABLE Sheet1 ( > ROW_ID integer OPTIONS (SEARCHABLE 'All_Except_Like', "teiid_excel:CELL_NUMBER" 'ROW_ID'), > StringNum string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '1'), > CharValue string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '2'), > DoubleNum double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '3'), > BigIntegerValue double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '4'), > ShortValue double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '5'), > FloatNum double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '6'), > ObjectValue string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '7'), > IntNum double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '8'), > BigDecimalValue double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '9'), > LongNum double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '10'), > BooleanValue boolean OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '11'), > TimestampValue double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '12'), > ByteNum double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '13'), > IntKey double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '14'), > StringKey string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '15'), > TimeValue double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '16'), > DateValue double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '17'), > CONSTRAINT PK0 PRIMARY KEY(ROW_ID) > ) OPTIONS ("teiid_excel:FILE" 'smalla.xlsx', "teiid_excel:FIRST_DATA_ROW_NUMBER" '2'); > {code} > When trying to import the same DDL using the DDL import wizard, a warning dialog is shown stating that the extension properties could not be processed and the Model Extension Definition should be registered -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2683) Importing Excel file using Teiid Connection does not import extension properties

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2683?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2683: ----------------------------------- Fix Version/s: 11.1.1 > Importing Excel file using Teiid Connection does not import extension properties > -------------------------------------------------------------------------------- > > Key: TEIIDDES-2683 > URL: https://issues.jboss.org/browse/TEIIDDES-2683 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 9.0.4 > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Fix For: 11.1, 11.1.1 > > Attachments: excel-import-problem.mkv > > > When importing an excel file using Teiid Connection, the extension properties are silently discarded. This results in invalid model, which, when deployed and queried, causes the following error in the server log: > bq. Connector worker process failed for atomic-request=AVU37BnZoOUS.0.0.0: org.teiid.translator.TranslatorException: TEIID23007 OPTIONS property CELL_NUMBER is required and it not defined on column ROW_ID > The DDL obtained from the server is > {code:sql} > SET NAMESPACE 'http://www.teiid.org/translator/excel/2014' AS teiid_excel; > CREATE FOREIGN TABLE Sheet1 ( > ROW_ID integer OPTIONS (SEARCHABLE 'All_Except_Like', "teiid_excel:CELL_NUMBER" 'ROW_ID'), > StringNum string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '1'), > CharValue string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '2'), > DoubleNum double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '3'), > BigIntegerValue double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '4'), > ShortValue double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '5'), > FloatNum double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '6'), > ObjectValue string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '7'), > IntNum double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '8'), > BigDecimalValue double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '9'), > LongNum double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '10'), > BooleanValue boolean OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '11'), > TimestampValue double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '12'), > ByteNum double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '13'), > IntKey double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '14'), > StringKey string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '15'), > TimeValue double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '16'), > DateValue double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '17'), > CONSTRAINT PK0 PRIMARY KEY(ROW_ID) > ) OPTIONS ("teiid_excel:FILE" 'smalla.xlsx', "teiid_excel:FIRST_DATA_ROW_NUMBER" '2'); > {code} > When trying to import the same DDL using the DDL import wizard, a warning dialog is shown stating that the extension properties could not be processed and the Model Extension Definition should be registered -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3037) Allow VDB user defined properties to have underscore(_) or period in the name

by Mario Majernik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3037?page=com.atlassian.jira.plu... ] Mario Majernik closed TEIIDDES-3037. ------------------------------------ > Allow VDB user defined properties to have underscore(_) or period in the name > ----------------------------------------------------------------------------- > > Key: TEIIDDES-3037 > URL: https://issues.jboss.org/browse/TEIIDDES-3037 > Project: Teiid Designer > Issue Type: Bug > Reporter: Chandra Akkinepalli > Assignee: Barry LaFond > Labels: release_notes > Fix For: 11.1 > > > VDB's userdefined properties doesn't allow Names containing underscore in them. > Our naming standards are defined to have _ in them. This is preventing us from doing a update via designer. As a work around we are udpating vdb.xml file within .vdb in an offline manner. > It would would be great if this restriction can be removed -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3055) non-integer VDB version missing validation warning

by Mario Majernik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3055?page=com.atlassian.jira.plu... ] Mario Majernik closed TEIIDDES-3055. ------------------------------------ > non-integer VDB version missing validation warning > -------------------------------------------------- > > Key: TEIIDDES-3055 > URL: https://issues.jboss.org/browse/TEIIDDES-3055 > Project: Teiid Designer > Issue Type: Bug > Components: Validation, VDB & Execution > Affects Versions: 11.0.1 > Reporter: Barry LaFond > Assignee: Barry LaFond > Labels: release_notes > Fix For: 11.1 > > > The VDB validation logic is missing the logic to catch a number format exception when validating the VDB version string. Need to wrap the logic in a try/catch block in VdbUtil.validateVdbModelsInWorkspace() > Here's an example of a message: *The PartsSupplier VDB's version number 1.0.1 is not an integer and will not deploy to a Teiid runtime version less than 9.0. Your current default Teiid server version is: 8.12.5* -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3099) Data sources cannot be created

by Mario Majernik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3099?page=com.atlassian.jira.plu... ] Mario Majernik closed TEIIDDES-3099. ------------------------------------ > Data sources cannot be created > ------------------------------ > > Key: TEIIDDES-3099 > URL: https://issues.jboss.org/browse/TEIIDDES-3099 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 11.1 > Reporter: Mario Majernik > Assignee: Barry LaFond > Priority: Blocker > Labels: release_notes > Fix For: 11.1 > > Attachments: screen1.png > > > Data Source cannot be created because in new version of designer are changed properties of data sources. > For example: (screen1.png --> right window) I chose salesforce as example. There are the same 3 important parameters in Data Source Properties for all drivers (why?) : > * connection-url > * user-name > * password > and for salesforce we have these parameters in connection profile : (screen2.png) > So how should I create data source when I do not have a "connection-url" (or how I can create a connection-url). The same problem is with more data sources. For example google spreadsheet (screen2.png) there are 4 properties. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3099) Data sources cannot be created

by Mario Majernik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3099?page=com.atlassian.jira.plu... ] Mario Majernik updated TEIIDDES-3099: ------------------------------------- Attachment: (was: screen2.png) > Data sources cannot be created > ------------------------------ > > Key: TEIIDDES-3099 > URL: https://issues.jboss.org/browse/TEIIDDES-3099 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 11.1 > Reporter: Mario Majernik > Assignee: Barry LaFond > Priority: Blocker > Fix For: 11.1 > > Attachments: screen1.png > > > Data Source cannot be created because in new version of designer are changed properties of data sources. > For example: (screen1.png --> right window) I chose salesforce as example. There are the same 3 important parameters in Data Source Properties for all drivers (why?) : > * connection-url > * user-name > * password > and for salesforce we have these parameters in connection profile : (screen2.png) > So how should I create data source when I do not have a "connection-url" (or how I can create a connection-url). The same problem is with more data sources. For example google spreadsheet (screen2.png) there are 4 properties. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

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

by Mario Majernik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3105?page=com.atlassian.jira.plu... ] Mario Majernik commented on TEIIDDES-3105: ------------------------------------------ There is still problem with saleforce-34 (still jdbc-ansi as default value instead of saleforce-34). File translator works fine. > 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.5.0#75005)

8 years, 4 months

1
0
0 / 0

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

by Mario Majernik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3105?page=com.atlassian.jira.plu... ] Mario Majernik reopened TEIIDDES-3105: -------------------------------------- > 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.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2985) Missing Procedure settings in dynamic VDB

by Mario Majernik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2985?page=com.atlassian.jira.plu... ] Mario Majernik closed TEIIDDES-2985. ------------------------------------ > Missing Procedure settings in dynamic VDB > ----------------------------------------- > > Key: TEIIDDES-2985 > URL: https://issues.jboss.org/browse/TEIIDDES-2985 > Project: Teiid Designer > Issue Type: Bug > Components: Dynamic VDBs, Import/Export > Affects Versions: 10.0.2 > Reporter: Mario Majernik > Labels: release_notes > Fix For: 11.1 > > Attachments: DynamicVDBtesting.zip > > > Some setting in source model miss after generate source model from dynamic vdb: > * Value of Function is false for "Function"(should be true) > * Value of Update Count is always AUTO(should be ONE for procedure) > * Name is Source for parameters missing > * Value of Name was newParameter_2 for second parameter in Procedure. After generating from dynamic vdb name is result. I think that is caused direction for this parameter which was set on RETURN. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2990) Strange behaviour with multi-sources in dynamic VDB

by Mario Majernik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2990?page=com.atlassian.jira.plu... ] Mario Majernik closed TEIIDDES-2990. ------------------------------------ > Strange behaviour with multi-sources in dynamic VDB > --------------------------------------------------- > > Key: TEIIDDES-2990 > URL: https://issues.jboss.org/browse/TEIIDDES-2990 > Project: Teiid Designer > Issue Type: Bug > Components: Dynamic VDBs, Import/Export > Affects Versions: 10.0.2 > Reporter: Mario Majernik > Assignee: Barry LaFond > Labels: release_notes > Fix For: 11.1 > > Attachments: ModelSourceVDB-vdb.xml > > > Line 9 and 10 in dynamic VDB describe two sources. > When you generate static VDB and check Source binding tab there is just one source model. > He has Source name from line 9 but translator name and JNDI name from line 10. > Also "Add Column" checkbox is not check. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 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 November 2017