October 2015 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2692) Operation editor still show that SQL is invalid but it is valid.

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2692?page=com.atlassian.jira.plu... ] Matej Kralik updated TEIIDDES-2692: ----------------------------------- Steps to Reproduce: # import the project from attachment # open Products_WSResponses model and rename incorrectName to badResultsDocument # save all # click to "Save/Validate SQL" in the deleteProductsInfo operation # nothing happened, operations are still invalid # delete anything letters from SQL and writings it there again # click to "Save/Validate SQL" # even now, it is valid was: # import the project from attachment # open Products_WSResponses model and rename incorrectName to badResultsDocument # save all # click to "Save/Validate SQL" in the deleteProductsInfo operation # nothing happened, operations are still invalid # delete anythink letters from SQL and writings it there again # click to "Save/Validate SQL" # even now, it is valid > Operation editor still show that SQL is invalid but it is valid. > ---------------------------------------------------------------- > > Key: TEIIDDES-2692 > URL: https://issues.jboss.org/browse/TEIIDDES-2692 > Project: Teiid Designer > Issue Type: Bug > Components: Editors, Validation > Affects Versions: 9.0.4 > Environment: Fedora 22 > Reporter: Matej Kralik > Priority: Minor > Attachments: ProductsProject.zip, Snímka obrazovky z 2015-10-15 15-50-28.png > > > I rename incorrect name in xml document to correct. When I try validate SQL in the web operation, nothing happend. As soon as I freely adjusted SQL in the operation, validate is correct. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2692) Operation editor still show that SQL is invalid but it is valid.

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2692?page=com.atlassian.jira.plu... ] Matej Kralik updated TEIIDDES-2692: ----------------------------------- Attachment: Snímka obrazovky z 2015-10-15 15-50-28.png > Operation editor still show that SQL is invalid but it is valid. > ---------------------------------------------------------------- > > Key: TEIIDDES-2692 > URL: https://issues.jboss.org/browse/TEIIDDES-2692 > Project: Teiid Designer > Issue Type: Bug > Components: Editors, Validation > Affects Versions: 9.0.4 > Environment: Fedora 22 > Reporter: Matej Kralik > Priority: Minor > Attachments: ProductsProject.zip, Snímka obrazovky z 2015-10-15 15-50-28.png > > > I rename incorrect name in xml document to correct. When I try validate SQL in the web operation, nothing happend. As soon as I freely adjusted SQL in the operation, validate is correct. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2692) Operation editor still show that SQL is invalid but it is valid.

by Matej Kralik (JIRA)

Matej Kralik created TEIIDDES-2692: -------------------------------------- Summary: Operation editor still show that SQL is invalid but it is valid. Key: TEIIDDES-2692 URL: https://issues.jboss.org/browse/TEIIDDES-2692 Project: Teiid Designer Issue Type: Bug Components: Editors, Validation Affects Versions: 9.0.4 Environment: Fedora 22 Reporter: Matej Kralik Priority: Minor Attachments: ProductsProject.zip I rename incorrect name in xml document to correct. When I try validate SQL in the web operation, nothing happend. As soon as I freely adjusted SQL in the operation, validate is correct. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2458) Wrong "name-in-source" property value for imported tables in Source model (JDBC importer, Sybase 15 Database)

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2458?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-2458: -------------------------------------- Assignee: Andrej Šmigala > Wrong "name-in-source" property value for imported tables in Source model (JDBC importer, Sybase 15 Database) > ------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2458 > URL: https://issues.jboss.org/browse/TEIIDDES-2458 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 9.0.1 > Environment: JBDS: 8.0.2GA > TD: 9.0.1.Final > OS: Fedora 20 > java: oracle 1.7 > JDBC driver: jconn4-26502 - jConnect (TM) for JDBC(TM)/7.00(Build 26502) > Sybase DB: ASE 15.0.3/EBF > Reporter: Juraj Duráni > Assignee: Andrej Šmigala > Fix For: 9.2 > > Attachments: parts_sql_catalog_in_name_in_source.png, parts_sql_include_catalog_in_name.png, parts_sql_schema_tree.png, pic1.png, pic2.png, pic3.png, sybase_bqt2_datatools_tree.png > > > I am trying to import a Source model from Sybase database. But imported tables have wrong "name-in-source" property values. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2458) Wrong "name-in-source" property value for imported tables in Source model (JDBC importer, Sybase 15 Database)

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2458?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2458: ----------------------------------- Fix Version/s: 9.2 > Wrong "name-in-source" property value for imported tables in Source model (JDBC importer, Sybase 15 Database) > ------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2458 > URL: https://issues.jboss.org/browse/TEIIDDES-2458 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 9.0.1 > Environment: JBDS: 8.0.2GA > TD: 9.0.1.Final > OS: Fedora 20 > java: oracle 1.7 > JDBC driver: jconn4-26502 - jConnect (TM) for JDBC(TM)/7.00(Build 26502) > Sybase DB: ASE 15.0.3/EBF > Reporter: Juraj Duráni > Fix For: 9.2 > > Attachments: parts_sql_catalog_in_name_in_source.png, parts_sql_include_catalog_in_name.png, parts_sql_schema_tree.png, pic1.png, pic2.png, pic3.png, sybase_bqt2_datatools_tree.png > > > I am trying to import a Source model from Sybase database. But imported tables have wrong "name-in-source" property values. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2670) Copying XML Schema Model problem

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2670?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2670: ---------------------------------------- The copy XSD operation appears to be failing on the definition of a *PhoneType* attribute on the *EmployeeType* complex type. {code:xml} <xs:attribute name="PhoneType" use="required"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="office"/> <xs:enumeration value="fax"/> <xs:enumeration value="cell"/> <xs:enumeration value="home"/> <xs:enumeration value="pager"/> </xs:restriction> </xs:simpleType> </xs:attribute> {code} If this attribute is converted to an <element> and moved within the <sequence> the copy model works OK. > Copying XML Schema Model problem > -------------------------------- > > Key: TEIIDDES-2670 > URL: https://issues.jboss.org/browse/TEIIDDES-2670 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 9.0.3 > Reporter: stanislav kaleta > Priority: Optional > Attachments: TestedProject.zip > > > When creating new XML Schema (XSD) Model by copying from existing model (see steps to reproduce), action fails with error (and new empty schema) for some schemas (e.g. schemas in attachement). > Error message: > Error attempting to load a Model Editor Page plugin > ID = org.teiid.designer.xsd.ui.editor.XsdSimpleDatatypesEditorPage@611ddac3 > Exception Stack Trace: > ... > Caused by: org.xml.sax.SAXParseException ... ... lineNumber: 1; columnNumber: 1; Premature end of file. > I assume it might be something with line endings of Windows text files, because it happened only for files originally created in Windows for me (However some schemas created in Windows works properly). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2458) Wrong "name-in-source" property value for imported tables in Source model (JDBC importer, Sybase 15 Database)

by Andrej Šmigala (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2458?page=com.atlassian.jira.plu... ] Andrej Šmigala commented on TEIIDDES-2458: ------------------------------------------ The comment above should be disregarded, I got the errors because I did not set {{SQLINITSTRING=set quoted_identifier on}} on the connection profile I submitted a PR here, but there's one issue with it that needs to be resolved: https://github.com/Teiid-Designer/teiid-designer/pull/516 > Wrong "name-in-source" property value for imported tables in Source model (JDBC importer, Sybase 15 Database) > ------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2458 > URL: https://issues.jboss.org/browse/TEIIDDES-2458 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 9.0.1 > Environment: JBDS: 8.0.2GA > TD: 9.0.1.Final > OS: Fedora 20 > java: oracle 1.7 > JDBC driver: jconn4-26502 - jConnect (TM) for JDBC(TM)/7.00(Build 26502) > Sybase DB: ASE 15.0.3/EBF > Reporter: Juraj Duráni > Attachments: parts_sql_catalog_in_name_in_source.png, parts_sql_include_catalog_in_name.png, parts_sql_schema_tree.png, pic1.png, pic2.png, pic3.png, sybase_bqt2_datatools_tree.png > > > I am trying to import a Source model from Sybase database. But imported tables have wrong "name-in-source" property values. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2682) Importing Teiid DDL and selecting wrong model type results in error

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2682?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2682: ---------------------------------------- For all but the Teiid dialect, the imported DDL will be targeted at *source* models. It's only the Teiid dialect that can defined source or view. But until the ddl file is specified and the DDL file is loaded, we can't detect what model type it is. There should be something we can do to clean this up. > Importing Teiid DDL and selecting wrong model type results in error > ------------------------------------------------------------------- > > Key: TEIIDDES-2682 > URL: https://issues.jboss.org/browse/TEIIDDES-2682 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 9.0.4 > Environment: MAC OS > Reporter: Matus Makovy > Attachments: Screen Shot 2015-10-12 at 13.32.49.png, view.ddl > > > When you import Teiid DDL that was created as export from VIEW MODEL and you select SOURCE MODEL during the import, this process results in error dialogue that is not really helpful for user. (see screenshot) > I think the error message should be more accurate -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 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 commented on TEIIDDES-2683: ---------------------------------------- I've verified that by importing the referenced DDL via Import > DDL File (Teiid dialect).... that the resulting model contains the appropriate Extension properties. > 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 > > 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 (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2684) SalesForce importer issue

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2684?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-2684: -------------------------------------- Assignee: Mark Drilling > SalesForce importer issue > ------------------------- > > Key: TEIIDDES-2684 > URL: https://issues.jboss.org/browse/TEIIDDES-2684 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 9.0.4 > Environment: MAC OS > Reporter: Matus Makovy > Assignee: Mark Drilling > Fix For: 9.3 > > > According to conversation in TEIID-3112 this is a Designer issue. If I understood correctly, it has been fixed in Teiid and now the changes have to be made in TD SF importer. > I have a VDB with Source model that is created via SalesForce importer and I am getting this error: > {quote} > Didn't understand relationship 'Opportunitys' in FROM part of query call. If you are attempting to use a custom relationship, be sure to append the '__r' after the custom relationship name. Please reference your WSDL or the describe call for the appropriate names > {quote} > when trying to submit this query: > {quote} > select distinct YEAR("Opportunity"."CloseDate") as "Opportunity_CloseDate1" from "SalesForceSource".Campaign AS "Campaign" LEFT OUTER JOIN "SalesForceSource".Opportunity AS "Opportunity" ON Campaign."Id" = Opportunity."CampaignId" order by YEAR("Opportunity"."CloseDate") ASC LIMIT 0 , 32 > {quote} > It works without problems with dynamic VDB. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 2015