August 2015 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2614) Add option to remove redundant Unique Constraint in DDL importing if column ID's match a PK

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2614?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2614: ----------------------------------- Fix Version/s: 9.0.4 > Add option to remove redundant Unique Constraint in DDL importing if column ID's match a PK > ------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2614 > URL: https://issues.jboss.org/browse/TEIIDDES-2614 > Project: Teiid Designer > Issue Type: Enhancement > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 9.2, 9.0.4 > > Attachments: TeiidDdlImporter.patch > > > Teiid Connection importer will return all PK/UC definitions exposed by the DB. Some DB's auto-create a unique constraint for an defined PK, which is really redundant. > Teiid Designer has a validation check that looks for PK/UC who share common column ID's and generates an error. This prevents a lot of DDL to end up being imported with errors. > Suggest looking for this use-case in the Teiid DDL Importer logic and removing the redundant UC prior to generating the XMI model -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2612) Cannot delete a model project with a read-only model in it.

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2612?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2612: ----------------------------------- Fix Version/s: 9.0.4 > Cannot delete a model project with a read-only model in it. > ----------------------------------------------------------- > > Key: TEIIDDES-2612 > URL: https://issues.jboss.org/browse/TEIIDDES-2612 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 9.0, 9.1 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 9.2, 9.0.4 > > Attachments: 0001-TEIIDES-2612-Refactor-deleting-response-to-related-r.patch, AbstractRefactorAction.patch, DeleteResourceRefactoring.patch, ModelExplorerResourceNavigator.patch > > > I set up a 2 projects with a single model in it. Project 1 has a read-only -model, Project 2 has a writeable model. > I can delete Project 2, but Project 1 sends up a error message dialog that it can't delete because the project has a read-only file in it. > Looking at DeleteResourcesRefactoring.checkResource(), it starts with checking if the resource is in the selected list. If not selected, it'll be an ERROR if a child resources is READ-ONLY, rather than a WARNING. > Further down the method it checks for read-only state of the resource and will set the message. > Problem is the Selected/Top-level Project should determine the severity of the read-only check. At most, the message should be an OK/Warning dialog to ask the user "Read-only resources found... do you still wish to delete?" > adding a method to check that *allProjectsSelected()* and switching the ERROR read-only status to WARNING at the start of the method seems to work. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1995) Add templates for OBJECTTABLE, TEXTABLE, etc

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1995?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1995: ---------------------------------------- OBJECTTABLE: master: https://github.com/Teiid-Designer/teiid-designer/commit/868e97ac9b1af1407... > Add templates for OBJECTTABLE, TEXTABLE, etc > -------------------------------------------- > > Key: TEIIDDES-1995 > URL: https://issues.jboss.org/browse/TEIIDDES-1995 > Project: Teiid Designer > Issue Type: Enhancement > Components: Transformations > Affects Versions: 8.4 > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 9.2, 9.0.4 > > Attachments: select-object-table-sql-template.png > > > Add templates for using OBJECTTABLE, TEXTTABLE, etc. to the the list of templates to apply to the transformation. Example: > SELECT > o.{colname}, o.{colname} > FROM > {ObjectTableName} as T, > OBJECTTABLE('x' PASSING T.{ObjectColumnName}Object as x COLUMNS > {colname} type 'teiid_row.{colname}', ….) as o -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1995) Add templates for OBJECTTABLE, TEXTABLE, etc

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1995?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1995: ----------------------------------- Attachment: select-object-table-sql-template.png > Add templates for OBJECTTABLE, TEXTABLE, etc > -------------------------------------------- > > Key: TEIIDDES-1995 > URL: https://issues.jboss.org/browse/TEIIDDES-1995 > Project: Teiid Designer > Issue Type: Enhancement > Components: Transformations > Affects Versions: 8.4 > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 9.2, 9.0.4 > > Attachments: select-object-table-sql-template.png > > > Add templates for using OBJECTTABLE, TEXTTABLE, etc. to the the list of templates to apply to the transformation. Example: > SELECT > o.{colname}, o.{colname} > FROM > {ObjectTableName} as T, > OBJECTTABLE('x' PASSING T.{ObjectColumnName}Object as x COLUMNS > {colname} type 'teiid_row.{colname}', ….) as o -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2460) JDBC Importer changes integer type to biginteger type when importing schema (reusing) from VDB

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2460?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2460: ---------------------------------------- [~asmigala] yes. Let's close this and create a new BZ to handle this via the new JIRA. > JDBC Importer changes integer type to biginteger type when importing schema (reusing) from VDB > ----------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2460 > URL: https://issues.jboss.org/browse/TEIIDDES-2460 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Reporter: Barry LaFond > Assignee: Mark Drilling > Fix For: 9.0.3, 9.2 > > Attachments: ErrorDialog.png, TEIIDDES2460.zip > > > When the JDBC importer is used to import a schema from an existing VDB integer types will be converted into biginterger types. This error is similar to Bug 1026892 except no exception is raised > Version-Release number of selected component (if applicable): > Actual results: > Imported schema has changed integer data type to biginteger data type. > Expected results: > Imported schema will be identical to original schema. > Additional info: > Imported schema is so long as the JPA entity reflects the biginteger type. This is problematic because now two separate JPA entities are needed, one for the original schema and another for the imported schema. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2460) JDBC Importer changes integer type to biginteger type when importing schema (reusing) from VDB

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2460?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-2460: -------------------------------------- Assignee: Barry LaFond (was: Mark Drilling) > JDBC Importer changes integer type to biginteger type when importing schema (reusing) from VDB > ----------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2460 > URL: https://issues.jboss.org/browse/TEIIDDES-2460 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 9.0.3, 9.2 > > Attachments: ErrorDialog.png, TEIIDDES2460.zip > > > When the JDBC importer is used to import a schema from an existing VDB integer types will be converted into biginterger types. This error is similar to Bug 1026892 except no exception is raised > Version-Release number of selected component (if applicable): > Actual results: > Imported schema has changed integer data type to biginteger data type. > Expected results: > Imported schema will be identical to original schema. > Additional info: > Imported schema is so long as the JPA entity reflects the biginteger type. This is problematic because now two separate JPA entities are needed, one for the original schema and another for the imported schema. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2616) Additional performance improvements in admin factory

by Andrej Šmigala (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2616?page=com.atlassian.jira.plu... ] Andrej Šmigala updated TEIIDDES-2616: ------------------------------------- Labels: commit-master (was: commit-master release_notes verified_jbdsis-8.0.3.CR2) > Additional performance improvements in admin factory > ----------------------------------------------------- > > Key: TEIIDDES-2616 > URL: https://issues.jboss.org/browse/TEIIDDES-2616 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 9.0.2, 9.0.3 > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Priority: Blocker > Labels: commit-master > Fix For: 9.2, 9.0.4 > > > There were a couple of issues that arose with testing the changes in TEIIDDES-2592 in Komodo Admin8Factory. There were some issues with certain connection factories that didn't have properties that ended up stopping loading of data source definitions. > So needed to catch intermediate exceptions and allow caching/loading of what data sources were on the server. This lead to caching DS names and XA-DS names separately, similar to resource names. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1995) Add templates for OBJECTTABLE, TEXTABLE, etc

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1995?page=com.atlassian.jira.plu... ] Barry LaFond edited comment on TEIIDDES-1995 at 8/21/15 5:04 PM: ----------------------------------------------------------------- Office discussions have led to more questions about this feature and how it should be implemented. The nature of SQL definition in Designer really begs for providing a more robust/full set of SQL fragments to handle the special Language objects supported by the Teiid runtime and query parser framework. * TEXTTABLE: https://docs.jboss.org/author/display/TEIID/TEXTTABLE * XMLTABLE: https://docs.jboss.org/author/display/TEIID/FROM+Clause#FROMClause-XMLTABLE * OBJECTTABLE: https://docs.jboss.org/author/display/TEIID/OBJECTTABLE * ARRAYTABLE: https://docs.jboss.org/author/display/TEIID/ARRAYTABLE We could provide a small set of templates for each of these with variables/placeholders for the user to replace. Ultimately this begs for enhancing the code-completion framework. So all the formatting/BNF rules for these objects would have to be captured and implemented.... and that's not a small effort. {code} TEXTTABLE(expression [SELECTOR string] COLUMNS <COLUMN>, ... [NO ROW DELIMITER] [DELIMITER char] [(QUOTE|ESCAPE) char] [HEADER [integer]] [SKIP integer]) AS name >> COLUMN := name (FOR ORDINALITY | datatype [WIDTH integer [NO TRIM]] [SELECTOR string integer]) >> see: https://docs.jboss.org/author/display/TEIID/FROM+Clause#FROMClause-TEXTTABLE OBJECTTABLE([LANGUAGE lang] rowScript [PASSING val AS name ...] COLUMNS colName colType colScript [DEFAULT defaultExpr] ...) AS id ARRAYTABLE(expression COLUMNS <COLUMN>, ...) AS name >> COLUMN := name datatype XMLTABLE([<NSP>,] xquery-expression [<PASSING>] [COLUMNS <COLUMN>, ... )] AS name >> COLUMN := name (FOR ORDINALITY | (datatype [DEFAULT expression] [PATH string])) {code} Pushing to 8.7 was (Author: blafond): Office discussions have led to more questions about this feature and how it should be implemented. The nature of SQL definition in Designer really begs for providing a more robust/full set of SQL fragments to handle the special Language objects supported by the Teiid runtime and query parser framework. TEXTTABLE, XMLTABLE, OBJECTTABLE, ARRAYTABLE would be a primary focus. We could provide a small set of templates for each of these with variables/placeholders for the user to replace. Ultimately this begs for enhancing the code-completion framework. So all the formatting/BNF rules for these objects would have to be captured and implemented.... and that's not a small effort. {code} TEXTTABLE(expression [SELECTOR string] COLUMNS <COLUMN>, ... [NO ROW DELIMITER] [DELIMITER char] [(QUOTE|ESCAPE) char] [HEADER [integer]] [SKIP integer]) AS name >> COLUMN := name (FOR ORDINALITY | datatype [WIDTH integer [NO TRIM]] [SELECTOR string integer]) >> see: https://docs.jboss.org/author/display/TEIID/FROM+Clause#FROMClause-TEXTTABLE OBJECTTABLE([LANGUAGE lang] rowScript [PASSING val AS name ...] COLUMNS colName colType colScript [DEFAULT defaultExpr] ...) AS id ARRAYTABLE(expression COLUMNS <COLUMN>, ...) AS name >> COLUMN := name datatype XMLTABLE([<NSP>,] xquery-expression [<PASSING>] [COLUMNS <COLUMN>, ... )] AS name >> COLUMN := name (FOR ORDINALITY | (datatype [DEFAULT expression] [PATH string])) {code} Pushing to 8.7 > Add templates for OBJECTTABLE, TEXTABLE, etc > -------------------------------------------- > > Key: TEIIDDES-1995 > URL: https://issues.jboss.org/browse/TEIIDDES-1995 > Project: Teiid Designer > Issue Type: Enhancement > Components: Transformations > Affects Versions: 8.4 > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 9.2, 9.0.4 > > > Add templates for using OBJECTTABLE, TEXTTABLE, etc. to the the list of templates to apply to the transformation. Example: > SELECT > o.{colname}, o.{colname} > FROM > {ObjectTableName} as T, > OBJECTTABLE('x' PASSING T.{ObjectColumnName}Object as x COLUMNS > {colname} type 'teiid_row.{colname}', ….) as o -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2616) Additional performance improvements in admin factory

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2616?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2616: ---------------------------------------- master: https://github.com/Teiid-Designer/teiid-designer/commit/47e5b43a8007f9f79... > Additional performance improvements in admin factory > ----------------------------------------------------- > > Key: TEIIDDES-2616 > URL: https://issues.jboss.org/browse/TEIIDDES-2616 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 9.0.2, 9.0.3 > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Priority: Blocker > Labels: commit-master, release_notes, verified_jbdsis-8.0.3.CR2 > Fix For: 9.2, 9.0.4 > > > There were a couple of issues that arose with testing the changes in TEIIDDES-2592 in Komodo Admin8Factory. There were some issues with certain connection factories that didn't have properties that ended up stopping loading of data source definitions. > So needed to catch intermediate exceptions and allow caching/loading of what data sources were on the server. This lead to caching DS names and XA-DS names separately, similar to resource names. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2616) Additional performance improvements in admin factory

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2616?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2616: ----------------------------------- Labels: commit-master release_notes verified_jbdsis-8.0.3.CR2 (was: release_notes verified_jbdsis-8.0.3.CR2) > Additional performance improvements in admin factory > ----------------------------------------------------- > > Key: TEIIDDES-2616 > URL: https://issues.jboss.org/browse/TEIIDDES-2616 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 9.0.2, 9.0.3 > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Priority: Blocker > Labels: commit-master, release_notes, verified_jbdsis-8.0.3.CR2 > Fix For: 9.2, 9.0.4 > > > There were a couple of issues that arose with testing the changes in TEIIDDES-2592 in Komodo Admin8Factory. There were some issues with certain connection factories that didn't have properties that ended up stopping loading of data source definitions. > So needed to catch intermediate exceptions and allow caching/loading of what data sources were on the server. This lead to caching DS names and XA-DS names separately, similar to resource names. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 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 August 2015