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

[JBoss JIRA] (TEIIDDES-1719) UDF jar path required for SalesForce Function Model created from SalesForce source model

by Lucie Fabrikova (JIRA)

Lucie Fabrikova created TEIIDDES-1719: ----------------------------------------- Summary: UDF jar path required for SalesForce Function Model created from SalesForce source model Key: TEIIDDES-1719 URL: https://issues.jboss.org/browse/TEIIDDES-1719 Project: Teiid Designer Issue Type: Feature Request Affects Versions: 8.1 Environment: JBDS 6.0.GA, Teiid Designer 8.1.Beta Reporter: Lucie Fabrikova Attachments: sf.xmi I created new source model by importing data from metamatrix demo SalesForce test account. On last page of importer, I checked the "Create a procedure for the GetUpdated operation." and "Create a procedure for the GetUpdated operation." Then I tried to generate a function model by following steps; the functional model is invalid. Steps to reproduce: 1. right-click the sf.xmi: Modelling > Create SalesForce Function Model 2. Error log: missing UDF jar path -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1667) Ability to define UDF with vararg to be used in a static VDB

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1667?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1667: ----------------------------------- Attachment: MyMathFunctions.jar > Ability to define UDF with vararg to be used in a static VDB > ------------------------------------------------------------ > > Key: TEIIDDES-1667 > URL: https://issues.jboss.org/browse/TEIIDDES-1667 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 8.0 > Environment: JBoss AS 7.1.1 > Teiid 8.3.0 > Teiid Designer 8.0.0 > Reporter: Shakir Shaik > Assignee: Mark Drilling > Fix For: 8.2 > > Attachments: FunctionMethodDescriptor.patch, FunctionPlugin.patch, MyMathFunctions.jar, MyMathFunctions.java, RelationalPlugin.patch, UdfManager.patch > > > I am not able to use a UDF with vararg and deploy the same in a static VDB. > Please see the details in the following thread of Teiid Designer User forum discussions: > https://community.jboss.org/thread/223823?tstart=0 -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1667) Ability to define UDF with vararg to be used in a static VDB

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1667?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1667: ----------------------------------- Attachment: MyMathFunctions.java > Ability to define UDF with vararg to be used in a static VDB > ------------------------------------------------------------ > > Key: TEIIDDES-1667 > URL: https://issues.jboss.org/browse/TEIIDDES-1667 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 8.0 > Environment: JBoss AS 7.1.1 > Teiid 8.3.0 > Teiid Designer 8.0.0 > Reporter: Shakir Shaik > Assignee: Mark Drilling > Fix For: 8.2 > > Attachments: FunctionMethodDescriptor.patch, FunctionPlugin.patch, MyMathFunctions.jar, MyMathFunctions.java, RelationalPlugin.patch, UdfManager.patch > > > I am not able to use a UDF with vararg and deploy the same in a static VDB. > Please see the details in the following thread of Teiid Designer User forum discussions: > https://community.jboss.org/thread/223823?tstart=0 -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1667) Ability to define UDF with vararg to be used in a static VDB

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1667?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1667: ----------------------------------- Attachment: UdfManager.patch > Ability to define UDF with vararg to be used in a static VDB > ------------------------------------------------------------ > > Key: TEIIDDES-1667 > URL: https://issues.jboss.org/browse/TEIIDDES-1667 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 8.0 > Environment: JBoss AS 7.1.1 > Teiid 8.3.0 > Teiid Designer 8.0.0 > Reporter: Shakir Shaik > Assignee: Mark Drilling > Fix For: 8.2 > > Attachments: FunctionMethodDescriptor.patch, FunctionPlugin.patch, RelationalPlugin.patch, UdfManager.patch > > > I am not able to use a UDF with vararg and deploy the same in a static VDB. > Please see the details in the following thread of Teiid Designer User forum discussions: > https://community.jboss.org/thread/223823?tstart=0 -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1667) Ability to define UDF with vararg to be used in a static VDB

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1667?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1667: ----------------------------------- Attachment: (was: UdfManager.patch) > Ability to define UDF with vararg to be used in a static VDB > ------------------------------------------------------------ > > Key: TEIIDDES-1667 > URL: https://issues.jboss.org/browse/TEIIDDES-1667 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 8.0 > Environment: JBoss AS 7.1.1 > Teiid 8.3.0 > Teiid Designer 8.0.0 > Reporter: Shakir Shaik > Assignee: Mark Drilling > Fix For: 8.2 > > Attachments: FunctionMethodDescriptor.patch, FunctionPlugin.patch, RelationalPlugin.patch, UdfManager.patch > > > I am not able to use a UDF with vararg and deploy the same in a static VDB. > Please see the details in the following thread of Teiid Designer User forum discussions: > https://community.jboss.org/thread/223823?tstart=0 -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1718) New Child/Sibling actions for view model launch the source model actions

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1718?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1718. ------------------------------------ Resolution: Done fixed > New Child/Sibling actions for view model launch the source model actions > ------------------------------------------------------------------------ > > Key: TEIIDDES-1718 > URL: https://issues.jboss.org/browse/TEIIDDES-1718 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 8.1 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 8.2 > > > The transformation.ui plugin's EditRelationalObjectDialog is using the RelationalObjectEditorFactory from the source model plugin. So the dialogs come up as new source object dialogs. > Result is that tables and procedures are missing the Transformation SQL tab and have a irrelevant Native SQL tab -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1718) New Child/Sibling actions for view model launch the source model actions

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1718: -------------------------------------- Summary: New Child/Sibling actions for view model launch the source model actions Key: TEIIDDES-1718 URL: https://issues.jboss.org/browse/TEIIDDES-1718 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 8.1 Reporter: Barry LaFond Assignee: Barry LaFond Fix For: 8.2 The transformation.ui plugin's EditRelationalObjectDialog is using the RelationalObjectEditorFactory from the source model plugin. So the dialogs come up as new source object dialogs. Result is that tables and procedures are missing the Transformation SQL tab and have a irrelevant Native SQL tab -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1717) Flat File Importer should allow alternate file extensions

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1717?page=com.atlassian.jira.plu... ] Mark Drilling reassigned TEIIDDES-1717: --------------------------------------- Assignee: Mark Drilling > Flat File Importer should allow alternate file extensions > --------------------------------------------------------- > > Key: TEIIDDES-1717 > URL: https://issues.jboss.org/browse/TEIIDDES-1717 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Affects Versions: 8.1 > Reporter: Mark Drilling > Assignee: Mark Drilling > Fix For: 8.2 > > > In the Flat File Importer (on the TeiidMetadataImportSourcePage) the user selects a folder, then the 'available' files in the folder are shown for selection. > > Currently, files of form .txt, .csv and (no ext) are shown - and this is hard-coded. I would recommend adding a filter drop down (or ?) to show the assumed defaults, but then allow the user to change the filter to "*.*" so that all files are shown. > We should not force the user to name their data files a certain way. For example if they have .dat files, there is no way to see them currently. -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1717) Flat File Importer should allow alternate file extensions

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1717?page=com.atlassian.jira.plu... ] Mark Drilling updated TEIIDDES-1717: ------------------------------------ Description: In the Flat File Importer (on the TeiidMetadataImportSourcePage) the user selects a folder, then the 'available' files in the folder are shown for selection. Currently, files of form .txt, .csv and (no ext) are shown - and this is hard-coded. I would recommend adding a filter drop down (or ?) to show the assumed defaults, but then allow the user to change the filter to "*.*" so that all files are shown. We should not force the user to name their data files a certain way. For example if they have .dat files, there is no way to see them currently. was: In the Flat File Importer (on the TeiidMetadataImportSourcePage) the user selects a folder, then the 'available' files in the folder are shown for selection. Currently, files of form *.txt, *.csv and * (no ext) are shown - and this is hard-coded. I would recommend adding a filter drop down (or ?) to show the assumed defaults, but then allow the user to change the filter to *.* so that all files are shown. We should not force the user to name their data files a certain way. For example if they have *.dat files, there is no way to see them currently. > Flat File Importer should allow alternate file extensions > --------------------------------------------------------- > > Key: TEIIDDES-1717 > URL: https://issues.jboss.org/browse/TEIIDDES-1717 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Affects Versions: 8.1 > Reporter: Mark Drilling > Fix For: 8.2 > > > In the Flat File Importer (on the TeiidMetadataImportSourcePage) the user selects a folder, then the 'available' files in the folder are shown for selection. > > Currently, files of form .txt, .csv and (no ext) are shown - and this is hard-coded. I would recommend adding a filter drop down (or ?) to show the assumed defaults, but then allow the user to change the filter to "*.*" so that all files are shown. > We should not force the user to name their data files a certain way. For example if they have .dat files, there is no way to see them currently. -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1717) Flat File Importer should allow alternate file extensions

by Mark Drilling (JIRA)

Mark Drilling created TEIIDDES-1717: --------------------------------------- Summary: Flat File Importer should allow alternate file extensions Key: TEIIDDES-1717 URL: https://issues.jboss.org/browse/TEIIDDES-1717 Project: Teiid Designer Issue Type: Enhancement Components: Import/Export Affects Versions: 8.1 Reporter: Mark Drilling Fix For: 8.2 In the Flat File Importer (on the TeiidMetadataImportSourcePage) the user selects a folder, then the 'available' files in the folder are shown for selection. Currently, files of form *.txt, *.csv and * (no ext) are shown - and this is hard-coded. I would recommend adding a filter drop down (or ?) to show the assumed defaults, but then allow the user to change the filter to *.* so that all files are shown. We should not force the user to name their data files a certain way. For example if they have *.dat files, there is no way to see them currently. -- 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

12 years, 11 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 May 2013