May 2013 - teiid-designer-issues - Jboss List Archives

[JBoss JIRA] (TEIIDDES-1578) Extension Properties category keeps collapsing in Property View

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1578?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-1578: -------------------------------------- Assignee: Mark Drilling (was: Dan Florian) Add steps to reproduce > Extension Properties category keeps collapsing in Property View > --------------------------------------------------------------- > > Key: TEIIDDES-1578 > URL: https://issues.jboss.org/browse/TEIIDDES-1578 > Project: Teiid Designer > Issue Type: Bug > Components: Extension Framework > Affects Versions: 8.0 > Reporter: Mark Drilling > Assignee: Mark Drilling > Fix For: 8.2 > > > The 'Extension' Category in the property view collapses whenever you edit one of the extension properties. This is very annoying when you want to edit several of the extension properties. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1211) Exporting DDL for Postgres produces invalid CREATE INDEX statement because duplicate object names in database

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1211?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1211: ----------------------------------- Assignee: Barry LaFond (was: Dan Florian) > Exporting DDL for Postgres produces invalid CREATE INDEX statement because duplicate object names in database > ------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1211 > URL: https://issues.jboss.org/browse/TEIIDDES-1211 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.4.2 > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 8.2 > > Attachments: tpc_postgres.ddl > > > Trying to execute DDL on postgres database produces this error: > Error: ERROR: relation "orders" already exists > SQLState: 42P07 > ErrorCode: 0 > Error occured in: > CREATE INDEX ORDERS ON ORDERS (O_CUSTKEY) > ---- > The problem was resolved if I changed ORDERS index name: > > CREATE INDEX ORDERS_IDX ON ORDERS (O_CUSTKEY); > ---- > Here's a statement I found on the Postgres Naming rules: > The names of all objects must be unique within some scope. Every database must have a unique name; the name of a schema must be unique within the scope of a single database, the name of a table must be unique within the scope of a single schema, and column names must be unique within a table. The name of an index must be unique within a database. > I would like to suggest that all index names that are created are appended with "idx" or something similar. Right now, the first looks to be the name of the table, and subsequent names have 1,2, etc. appended. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1705) Model imported from DDL is missing relational model extension MED

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1705?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1705: ---------------------------------------- At first glance, the primary problem is the the difference and merge processing is ignoring Model Descriptions or anything inside a model's *AnnotationsContainer* root object. We had this problem a few years ago in the *StructuralCopyModelFeaturePopulator*. We added an instanceof *AnnotationContainer* check if "Copy all descriptions" option is checked. > Model imported from DDL is missing relational model extension MED > ----------------------------------------------------------------- > > Key: TEIIDDES-1705 > URL: https://issues.jboss.org/browse/TEIIDDES-1705 > Project: Teiid Designer > Issue Type: Bug > Components: Extension Framework > Affects Versions: 8.1 > Reporter: Barry LaFond > Assignee: Dan Florian > Priority: Critical > Fix For: 8.2 > > > While working on TEIIDDES-1660 noticed that if I re-imported to same model an NPE showed up because the relational MED was not saved in the model. > RelationalPlugin is responding to a New Model event and applying the MED, but later in the importer, the model contents is copied and it loses the MED. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1722) Flat File Importer - selection of directory with pdfs causes designer to freeze.

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1722?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1722. ------------------------------------ Resolution: Done Moved loadHeader() call to when it's really needed after the source page. Added a warning message to the source page if a non TXT/CSV file is selected for processing. > Flat File Importer - selection of directory with pdfs causes designer to freeze. > -------------------------------------------------------------------------------- > > Key: TEIIDDES-1722 > URL: https://issues.jboss.org/browse/TEIIDDES-1722 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.1 > Reporter: Mark Drilling > Assignee: Barry LaFond > Fix For: 8.2 > > > In the Flat File Import Wizard, if a user selects a directory with mixed file types - this can cause Designer to freeze. > I created a connection profile with a directory containing about 60 files of various types. On the source selection page of the wizard, I selected the profile - then Designer hung. > The problem seems to be in TeiidMetadataFileInfo - the loadHeader method. The assumption is that the files being read are all text files - we need to detect and skip files of incompatible type. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1722) Flat File Importer - selection of directory with pdfs causes designer to freeze.

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1722?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-1722: -------------------------------------- Assignee: Barry LaFond (was: Mark Drilling) > Flat File Importer - selection of directory with pdfs causes designer to freeze. > -------------------------------------------------------------------------------- > > Key: TEIIDDES-1722 > URL: https://issues.jboss.org/browse/TEIIDDES-1722 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.1 > Reporter: Mark Drilling > Assignee: Barry LaFond > Fix For: 8.2 > > > In the Flat File Import Wizard, if a user selects a directory with mixed file types - this can cause Designer to freeze. > I created a connection profile with a directory containing about 60 files of various types. On the source selection page of the wizard, I selected the profile - then Designer hung. > The problem seems to be in TeiidMetadataFileInfo - the loadHeader method. The assumption is that the files being read are all text files - we need to detect and skip files of incompatible type. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1736) Provide the ability to define the MetadataRepository implementation (jboss as module) to use

by Van Halbert (JIRA)

Van Halbert created TEIIDDES-1736: ------------------------------------- Summary: Provide the ability to define the MetadataRepository implementation (jboss as module) to use Key: TEIIDDES-1736 URL: https://issues.jboss.org/browse/TEIIDDES-1736 Project: Teiid Designer Issue Type: Feature Request Components: Modeling Affects Versions: 8.2 Reporter: Van Halbert Teiid provides the ability to specify your own MetadataRepository implementation, by specifying the jboss as module (type) in the dynamic vdb. Example: <metadata type="org.jboss.teiid.costing.example"></metadata> Can designer provide the ability to do the same from the tooling? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1735) Importing DDL Tables containing FK with no column references to table reference does not set unique key

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1735?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1735. ------------------------------------ Resolution: Done Done > Importing DDL Tables containing FK with no column references to table reference does not set unique key > ------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1735 > URL: https://issues.jboss.org/browse/TEIIDDES-1735 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.2 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 8.2 > > > DDL allows creating an in-line FK constraint with an abbreviated Table reference which assumes the PK or UC on the table references same # columns as the FK. The example below results in the FK's Unique Key reference NOT getting set (NULL) > {code} > // testOptionalFK > CREATE FOREIGN TABLE T12 ( > g1e1 integer, > g1e2 varchar, > PRIMARY KEY(g1e1, g1e2) > ); > CREATE FOREIGN TABLE T13 ( > g2e1 integer, > g2e2 varchar, > PRIMARY KEY(g2e1, g2e2), > FOREIGN KEY (g2e1, g2e2) REFERENCES T12 > ); > {code} > Need to allow for this. > Error is in the DdlImporter.createTeiidConstraint() method -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1515) Cannot set ROW_NUMBER() on Transformation Editor

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1515?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-1515. ------------------------------------- Resolution: Done Added WindowFunction handling to DisplayNodeFactory. Also fixed issue getting the projected symbol type in TransformationSqlHelper (the attribute type was not being resolved correctly). pull request - https://github.com/Teiid-Designer/teiid-designer/pull/164 > Cannot set ROW_NUMBER() on Transformation Editor > ------------------------------------------------ > > Key: TEIIDDES-1515 > URL: https://issues.jboss.org/browse/TEIIDDES-1515 > Project: Teiid Designer > Issue Type: Bug > Components: Editors > Affects Versions: 7.7.1, 7.8 > Environment: JBDS 5.0.1 > Reporter: Eiichi Nagai > Assignee: Mark Drilling > Fix For: 8.2 > > > ROW_NUMBER is supported by Teiid[1]. However, it cannot set the ROW_NUMBER function using the Transformation Editor. > [1] http://docs.jboss.org/teiid/7.7.0.Final/reference/en-US/html/sql_support.... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1735) Importing DDL Tables containing FK with no column references to table reference does not set unique key

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1735: -------------------------------------- Summary: Importing DDL Tables containing FK with no column references to table reference does not set unique key Key: TEIIDDES-1735 URL: https://issues.jboss.org/browse/TEIIDDES-1735 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 8.2 Reporter: Barry LaFond Assignee: Barry LaFond Fix For: 8.2 DDL allows creating an in-line FK constraint with an abbreviated Table reference which assumes the PK or UC on the table references same # columns as the FK. The example below results in the FK's Unique Key reference NOT getting set (NULL) {code} // testOptionalFK CREATE FOREIGN TABLE T12 ( g1e1 integer, g1e2 varchar, PRIMARY KEY(g1e1, g1e2) ); CREATE FOREIGN TABLE T13 ( g2e1 integer, g2e2 varchar, PRIMARY KEY(g2e1, g2e2), FOREIGN KEY (g2e1, g2e2) REFERENCES T12 ); {code} Need to allow for this. Error is in the DdlImporter.createTeiidConstraint() method -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1287) Web Service to Source Importer Warns of No Input Columns for Web Services with No Inputs

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1287?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1287: ----------------------------------- Assignee: (was: Barry LaFond) > Web Service to Source Importer Warns of No Input Columns for Web Services with No Inputs > ---------------------------------------------------------------------------------------- > > Key: TEIIDDES-1287 > URL: https://issues.jboss.org/browse/TEIIDDES-1287 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.7 > Reporter: Ted Jones > Attachments: org.teiid.designer.modelgenerator.wsdl.ui.patch > > > For a web service with no input parameters, we show a warning that no elements are selected. We should figure out that there are no inputs for the web service and not show a warning. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues May 2013