April 2017 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2865) JDBC importer imports MSSQL Server datatype numeric(9, [0-9]) as bigdecimal with zero precision

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2865?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2865. ------------------------------------ Resolution: Done 11.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/63e7cdef53c052810... > JDBC importer imports MSSQL Server datatype numeric(9,[0-9]) as bigdecimal with zero precision > ---------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2865 > URL: https://issues.jboss.org/browse/TEIIDDES-2865 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 10.0, 9.0.5, 9.0.6, 9.0.7 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: 11.0.2 > > > JDBC importer imports MSSQL Server datatype numeric(9,[0-9]) as bigdecimal with zero precision and should be 9. I believe this https://issues.jboss.org/browse/TEIIDDES-2746 may have changed the behavior, in version 9.0.3 it imports correctly. > You can use jdbc:sqlserver://ENGNTDBS14.mw.lab.eng.bos.redhat.com:1433;databaseName=mss_eds > user - mss_eds > password - mss_eds > table - debtest2, both columns are numeric(9,2) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3069) odata4 fails to return data on top of mongoDB view model

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3069?page=com.atlassian.jira.plu... ] Steven Hawkins reassigned TEIIDDES-3069: ---------------------------------------- Assignee: Barry LaFond (was: Steven Hawkins) Moving to Designer for further investigation / work. On the Teiid side at least with upstream I don't see the server providing a 0 length in the metadata. > odata4 fails to return data on top of mongoDB view model > --------------------------------------------------------- > > Key: TEIIDDES-3069 > URL: https://issues.jboss.org/browse/TEIIDDES-3069 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Environment: Noticed in JDV 6.3.4 > Reporter: Michael Echevarria > Assignee: Barry LaFond > Priority: Critical > Attachments: Screenshot from 2017-03-28 15-38-25.png, Screenshot from 2017-03-28 15-38-32.png, Screenshot from 2017-03-28 15-38-46.png, Screenshot from 2017-03-28 15-38-56.png, designer-length-added.png, mongo-view-error.png, odata2-works.png, odata4-error.png, odata4-with-length-changed.png > > > Description of problem: > Accessing either an exclusive view model or combined view model for a mongoDB datasource via odata4 results in an error. > The data returns via odata2, jdbc and preview in the designer > Version-Release number of selected component (if applicable): > JDV 6.3.4 > Actual results: > Property mapping error > Expected results: > Model data -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3069) odata4 fails to return data on top of mongoDB view model

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3069?page=com.atlassian.jira.plu... ] Steven Hawkins moved TEIID-4829 to TEIIDDES-3069: ------------------------------------------------- Project: Teiid Designer (was: Teiid) Key: TEIIDDES-3069 (was: TEIID-4829) Component/s: Teiid Integration (was: Misc. Connectors) Affects Version/s: (was: 8.12.9.6_3) > odata4 fails to return data on top of mongoDB view model > --------------------------------------------------------- > > Key: TEIIDDES-3069 > URL: https://issues.jboss.org/browse/TEIIDDES-3069 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Environment: Noticed in JDV 6.3.4 > Reporter: Michael Echevarria > Assignee: Steven Hawkins > Priority: Critical > Attachments: Screenshot from 2017-03-28 15-38-25.png, Screenshot from 2017-03-28 15-38-32.png, Screenshot from 2017-03-28 15-38-46.png, Screenshot from 2017-03-28 15-38-56.png, designer-length-added.png, mongo-view-error.png, odata2-works.png, odata4-error.png, odata4-with-length-changed.png > > > Description of problem: > Accessing either an exclusive view model or combined view model for a mongoDB datasource via odata4 results in an error. > The data returns via odata2, jdbc and preview in the designer > Version-Release number of selected component (if applicable): > JDV 6.3.4 > Actual results: > Property mapping error > Expected results: > Model data -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

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

by Steve Tran (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3065?page=com.atlassian.jira.plu... ] Steve Tran commented on TEIIDDES-3065: -------------------------------------- Same thing happens when you try to deploy one of these dynamic VDB xml files. Is the action item to look into Teiid Designer and why it's not generating the dynamic VDBs with default values properly? It might just be double-quoting within the single quotes when constructing the default value portion of the DDL. > 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)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2872) Add GEOMETRY datatype to MxdConstants as a new choice for extending column & parameter types

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2872?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2872. ------------------------------------ Resolution: Done 11.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/a80add0628e91dc55... > Add GEOMETRY datatype to MxdConstants as a new choice for extending column & parameter types > -------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2872 > URL: https://issues.jboss.org/browse/TEIIDDES-2872 > Project: Teiid Designer > Issue Type: Enhancement > Components: Extension Framework, Modeling > Affects Versions: 10.0.1 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 11.0.2 > > > the geometry datatype was added in Teiid 10.x as a built-in/runtime type. Need to add that type to the list of types that will be validated against in the translator framework. > See MxdConstants.java -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 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 resolved TEIIDDES-2683. ------------------------------------ Resolution: Done tested both the DDL importer and an example name.xlsx file and resource adapter. Both workflows ended up with proper extension property values assuming that a running server was connected and insure that the EXCEL MED was imported from the server and registered as a MED. > 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.0.2 > > > 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.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3067) Test connection is OK but cannot be created datasource (MongoDB)

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3067?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-3067: ----------------------------------- Priority: Major (was: Minor) > Test connection is OK but cannot be created datasource (MongoDB) > ---------------------------------------------------------------- > > Key: TEIIDDES-3067 > URL: https://issues.jboss.org/browse/TEIIDDES-3067 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 11.0.1 > Reporter: Mario Majernik > Attachments: screen_mongo.png, screen_mongo2.png > > > I create connection profile and test connection. Result is OK (screen_mongo2.png). > Then I tried to create datasource from this connection profile and relust is this error(screen_mongo.png) > [Values for MongoDB:| https://mojo.redhat.com/docs/DOC-943544] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3067) Test connection is OK but cannot be created datasource (MongoDB)

by Mario Majernik (JIRA)

Mario Majernik created TEIIDDES-3067: ---------------------------------------- Summary: Test connection is OK but cannot be created datasource (MongoDB) Key: TEIIDDES-3067 URL: https://issues.jboss.org/browse/TEIIDDES-3067 Project: Teiid Designer Issue Type: Bug Affects Versions: 11.0.1 Reporter: Mario Majernik Priority: Minor Attachments: screen_mongo.png, screen_mongo2.png I create connection profile and test connection. Result is OK (screen_mongo2.png). Then I tried to create datasource from this connection profile and relust is this error(screen_mongo.png) Values for MongoDB:[link title| https://mojo.redhat.com/docs/DOC-943544] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3067) Test connection is OK but cannot be created datasource (MongoDB)

by Mario Majernik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3067?page=com.atlassian.jira.plu... ] Mario Majernik updated TEIIDDES-3067: ------------------------------------- Description: I create connection profile and test connection. Result is OK (screen_mongo2.png). Then I tried to create datasource from this connection profile and relust is this error(screen_mongo.png) [Values for MongoDB:| https://mojo.redhat.com/docs/DOC-943544] was: I create connection profile and test connection. Result is OK (screen_mongo2.png). Then I tried to create datasource from this connection profile and relust is this error(screen_mongo.png) Values for MongoDB:[link title| https://mojo.redhat.com/docs/DOC-943544] > Test connection is OK but cannot be created datasource (MongoDB) > ---------------------------------------------------------------- > > Key: TEIIDDES-3067 > URL: https://issues.jboss.org/browse/TEIIDDES-3067 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 11.0.1 > Reporter: Mario Majernik > Priority: Minor > Attachments: screen_mongo.png, screen_mongo2.png > > > I create connection profile and test connection. Result is OK (screen_mongo2.png). > Then I tried to create datasource from this connection profile and relust is this error(screen_mongo.png) > [Values for MongoDB:| https://mojo.redhat.com/docs/DOC-943544] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3050) Non working checkboxes in Index after Export/Import

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3050?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-3050. ------------------------------------ Resolution: Won't Fix The Index object in Designer contains a few properties that are not transferrable to Teiid DDL, so they are not exported nor imported with the Index as *OPTIONS(....)* > Non working checkboxes in Index after Export/Import > ---------------------------------------------------- > > Key: TEIIDDES-3050 > URL: https://issues.jboss.org/browse/TEIIDDES-3050 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 11.0.1 > Reporter: Mario Majernik > Assignee: Barry LaFond > Fix For: 11.0.2 > > Attachments: IndexCheckboxes.zip > > > Checkboxes "Unique" , "Nullable" and "Auto Update" is false. All should be true. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues April 2017