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

[JBoss JIRA] (TEIIDDES-1723) Refactor>Rename/Move do not enable in ModelExplorer

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1723?page=com.atlassian.jira.plu... ] Mark Drilling reassigned TEIIDDES-1723: --------------------------------------- Assignee: Mark Drilling > Refactor>Rename/Move do not enable in ModelExplorer > --------------------------------------------------- > > Key: TEIIDDES-1723 > URL: https://issues.jboss.org/browse/TEIIDDES-1723 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 8.2 > Reporter: Mark Drilling > Assignee: Mark Drilling > Fix For: 8.2 > > > 'Refactor > Rename' and 'Refactor > Move' dont enable in ModelExplorer -- 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-1669) Column Datatype Missing Generating Virtual Table From SELECT Clause Containing A Function And Alias

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1669?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-1669. ------------------------------------- Resolution: Done isolated problem to TransformationSqlHelper.getElementSymbolType. Was not getting the type for other possibilities. Retested ok. https://github.com/Teiid-Designer/teiid-designer/pull/163 > Column Datatype Missing Generating Virtual Table From SELECT Clause Containing A Function And Alias > --------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1669 > URL: https://issues.jboss.org/browse/TEIIDDES-1669 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 8.1 > Environment: JBDS 6.0.1.GA, Teiid 8.2, OSX 10.8.3 > Reporter: Dan Florian > Assignee: Mark Drilling > Fix For: 8.2 > > > Create a source model (SourceModel) with one table (SourceTable) that has one column (sourceColumn) of type int. Created a virtual model (VirtualModel) with one table (ViewTable). Opened the transformation editor and entered: > SELECT SUM(SourceModel.SourceTable.sourceColumn) AS viewColumn FROM SourceModel.SourceTable > The "viewColumn" column was generated without a data type. Because we know the return type of the function, and the datatype resolver knows how to resolve, the data type should've been determined. -- 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-1669) Column Datatype Missing Generating Virtual Table From SELECT Clause Containing A Function And Alias

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1669?page=com.atlassian.jira.plu... ] Mark Drilling reassigned TEIIDDES-1669: --------------------------------------- Assignee: Mark Drilling > Column Datatype Missing Generating Virtual Table From SELECT Clause Containing A Function And Alias > --------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1669 > URL: https://issues.jboss.org/browse/TEIIDDES-1669 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 8.1 > Environment: JBDS 6.0.1.GA, Teiid 8.2, OSX 10.8.3 > Reporter: Dan Florian > Assignee: Mark Drilling > Fix For: 8.2 > > > Create a source model (SourceModel) with one table (SourceTable) that has one column (sourceColumn) of type int. Created a virtual model (VirtualModel) with one table (ViewTable). Opened the transformation editor and entered: > SELECT SUM(SourceModel.SourceTable.sourceColumn) AS viewColumn FROM SourceModel.SourceTable > The "viewColumn" column was generated without a data type. Because we know the return type of the function, and the datatype resolver knows how to resolve, the data type should've been determined. -- 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-257) enhancement to provide better visibility to Request parameters from within the Response document

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-257?page=com.atlassian.jira.plug... ] Mark Drilling updated TEIIDDES-257: ----------------------------------- > enhancement to provide better visibility to Request parameters from within the Response document > ------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-257 > URL: https://issues.jboss.org/browse/TEIIDDES-257 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Affects Versions: 7.0 > Reporter: Debbie Steigner > Assignee: Mark Drilling > Fix For: Future > > Attachments: POC.vdb > > > Need a way to pass WS request inputs to an XML response doc that doesn't include them in the response. Requesting an enhancement to provide better visibility to Request parameters from within the Response document. One logical way to do that is to expose them in the Input Set of each mapping class in the Response. -- 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-257) enhancement to provide better visibility to Request parameters from within the Response document

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-257?page=com.atlassian.jira.plug... ] Mark Drilling updated TEIIDDES-257: ----------------------------------- Attachment: POC.vdb > enhancement to provide better visibility to Request parameters from within the Response document > ------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-257 > URL: https://issues.jboss.org/browse/TEIIDDES-257 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Affects Versions: 7.0 > Reporter: Debbie Steigner > Assignee: Mark Drilling > Fix For: Future > > Attachments: POC.vdb > > > Need a way to pass WS request inputs to an XML response doc that doesn't include them in the response. Requesting an enhancement to provide better visibility to Request parameters from within the Response document. One logical way to do that is to expose them in the Input Set of each mapping class in the Response. -- 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-1727) Servers View - Translators folder is alway empty

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1727?page=com.atlassian.jira.plu... ] Paul Richardson resolved TEIIDDES-1727. --------------------------------------- Resolution: Done [Pull Request|https://github.com/Teiid-Designer/teiid-designer/pull/161] > Servers View - Translators folder is alway empty > ------------------------------------------------ > > Key: TEIIDDES-1727 > URL: https://issues.jboss.org/browse/TEIIDDES-1727 > Project: Teiid Designer > Issue Type: Bug > Components: Views > Affects Versions: 8.2 > Reporter: Mark Drilling > Assignee: Paul Richardson > Fix For: 8.2 > > > On the servers view, the Teiid Configuration has 'Data Sources', 'Translators' and 'VDBs' folders. The 'Data Sources' and 'VDBs' folders show the corresponding items, but the 'Translators' folder is always empty. -- 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-1733) IllegalArgumentException right-clicking with 2 or more projects selected

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1733?page=com.atlassian.jira.plu... ] Paul Richardson resolved TEIIDDES-1733. --------------------------------------- Resolution: Done See pull [request|https://github.com/Teiid-Designer/teiid-designer/pull/160] > IllegalArgumentException right-clicking with 2 or more projects selected > ------------------------------------------------------------------------ > > Key: TEIIDDES-1733 > URL: https://issues.jboss.org/browse/TEIIDDES-1733 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 8.2 > Reporter: Barry LaFond > Assignee: Paul Richardson > Priority: Critical > Fix For: 8.2 > > > java.lang.IllegalArgumentException: can't find ID "properties" > at org.eclipse.jface.action.ContributionManager.insertAfter(ContributionManager.java:334) > at org.teiid.designer.ui.common.actions.ExtendedMenuManager.insertAfter(ExtendedMenuManager.java:147) > at org.eclipse.jface.action.ContributionManager.insertAfter(ContributionManager.java:325) > at org.teiid.designer.ui.common.actions.ExtendedMenuManager.insertAfter(ExtendedMenuManager.java:129) > at org.teiid.designer.ui.explorer.ModelExplorerResourceNavigator.overrideAction(ModelExplorerResourceNavigator.java:959) > at org.teiid.designer.ui.explorer.ModelExplorerResourceNavigator.fillContextMenu(ModelExplorerResourceNavigator.java:1122) > at org.teiid.designer.ui.explorer.ModelExplorerResourceNavigator$13.menuAboutToShow(ModelExplorerResourceNavigator.java:935) > at org.eclipse.jface.action.MenuManager.fireAboutToShow(MenuManager.java:343) -- 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-1733) IllegalArgumentException right-clicking with 2 or more projects selected

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1733: -------------------------------------- Summary: IllegalArgumentException right-clicking with 2 or more projects selected Key: TEIIDDES-1733 URL: https://issues.jboss.org/browse/TEIIDDES-1733 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 8.2 Reporter: Barry LaFond Assignee: Paul Richardson Priority: Critical Fix For: 8.2 java.lang.IllegalArgumentException: can't find ID "properties" at org.eclipse.jface.action.ContributionManager.insertAfter(ContributionManager.java:334) at org.teiid.designer.ui.common.actions.ExtendedMenuManager.insertAfter(ExtendedMenuManager.java:147) at org.eclipse.jface.action.ContributionManager.insertAfter(ContributionManager.java:325) at org.teiid.designer.ui.common.actions.ExtendedMenuManager.insertAfter(ExtendedMenuManager.java:129) at org.teiid.designer.ui.explorer.ModelExplorerResourceNavigator.overrideAction(ModelExplorerResourceNavigator.java:959) at org.teiid.designer.ui.explorer.ModelExplorerResourceNavigator.fillContextMenu(ModelExplorerResourceNavigator.java:1122) at org.teiid.designer.ui.explorer.ModelExplorerResourceNavigator$13.menuAboutToShow(ModelExplorerResourceNavigator.java:935) at org.eclipse.jface.action.MenuManager.fireAboutToShow(MenuManager.java:343) -- 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-1661) "Create expression" doesn't bind virtual column to function

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1661?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-1661. ------------------------------------- Resolution: Done The root cause of the issue was that that return type was not set for Functions. Now when the Function object is returned from the ExpressionBuilder, it is checked and sync is done against the FunctionLibrary to ensure that the return type and FunctionDescriptor are set. Retested ok. Pull request - https://github.com/Teiid-Designer/teiid-designer/pull/159 > "Create expression" doesn't bind virtual column to function > ----------------------------------------------------------- > > Key: TEIIDDES-1661 > URL: https://issues.jboss.org/browse/TEIIDDES-1661 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 8.1 > Environment: Eclipse Juno sr2 > Teiid designer alpha 8.1alpha2 > Reporter: Lucie Fabrikova > Assignee: Mark Drilling > Fix For: 8.2 > > Attachments: create-expression.png > > > In relational view model, if I create new virtual column and try to bind a function to it via Reconciler and Create expression button, they are not binded. -- 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-1732) Stream line steps to implement all the steps around materialization

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1732?page=com.atlassian.jira.plu... ] Van Halbert updated TEIIDDES-1732: ---------------------------------- Description: Would like to stream line the steps to putting materialization to work. Example: - Right mouse click on view, select materialization - present wizard to walk thru the following options: - create physical table based on selected view/table (export/import of ddl is supported, but would like the table automatically created) - put name of mat table into the selected table/view to be materialized - [optional] export DDL (file system or clipboard) - [optional] create procedure that has the "select into" for refreshing Having the procedure provides the immediate ability to call to refresh, without having to remember what tables. Also, with the feature of native queries, could add the truncate call to clear the table. Once thru this wizard, (I think) everything is in place to do materialization for the specified table. was: Would like to stream line the steps to putting materialization to work. Example: - Right mouse click on view, select materialization - present wizard to walk thru the following options: - create physical table based on selected view/table (export/import of ddl is supported, but would like the table automatically created) - put name of name into the selected table/view to be materialized - [optional] export DDL (file system or clipboard) - [optional] create procedure that has the "select into" for refreshing Having the procedure provides the immediate ability to call to refresh, without having to remember what tables. Also, with the feature of native queries, could add the truncate call to clear the table. Once thru this wizard, (I think) everything is in place to do materialization for the specified table. > Stream line steps to implement all the steps around materialization > -------------------------------------------------------------------- > > Key: TEIIDDES-1732 > URL: https://issues.jboss.org/browse/TEIIDDES-1732 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Affects Versions: 8.2 > Reporter: Van Halbert > > Would like to stream line the steps to putting materialization to work. Example: > - Right mouse click on view, select materialization > - present wizard to walk thru the following options: > - create physical table based on selected view/table (export/import of ddl is supported, but would like the table automatically created) > - put name of mat table into the selected table/view to be materialized > - [optional] export DDL (file system or clipboard) > - [optional] create procedure that has the "select into" for refreshing > Having the procedure provides the immediate ability to call to refresh, without having to remember what tables. Also, with the feature of native queries, could add the truncate call to clear the table. > Once thru this wizard, (I think) everything is in place to do materialization for the specified table. -- 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