September 2016 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2097) JDBC Importer fails when importing Access 2013 metadata via JDBC ODBC bridge

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2097?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-2097. ---------------------------------- The issue is marked as "Out of date". Closing the issue - TD JIRA Clean up > JDBC Importer fails when importing Access 2013 metadata via JDBC ODBC bridge > ---------------------------------------------------------------------------- > > Key: TEIIDDES-2097 > URL: https://issues.jboss.org/browse/TEIIDDES-2097 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Reporter: Filip Nguyen > Attachments: DSN.png, ODBCTesting.mdb > > > Probably related to TEIID-2912 > Environment: > * MS Access 2013 > * MS Windows Server 2012 > Steps to reproduce: > * Created a JDBC ODBC bridge connection profile (class: sun.jdbc.odbc.JdbcOdbcDriver) > * Trying to import using JDBC importer, no tables are shown -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2083) VDB datasource creation enhancements

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2083?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-2083. ---------------------------------- > VDB datasource creation enhancements > ------------------------------------ > > Key: TEIIDDES-2083 > URL: https://issues.jboss.org/browse/TEIIDDES-2083 > Project: Teiid Designer > Issue Type: Enhancement > Components: Teiid Integration > Reporter: Ramesh Reddy > Assignee: Barry LaFond > > 1) When a VDB is deployed, "Create VDB DataSource" dialog pops up, it asks the user whether to create a data source for VDB, but does not provide a "cancel" button to opt out. There should be a "cancel" to opt out. > * BML - There is a Cancel button on the dialog > 2) If you are re-deploying the same VDB, the same dialog pops up again asking the same question, it should be changed to honor the previous answer. > 3) Say if the user did create a data source, then in re-deploy case the data source either needs to be deleted and re-created or flush the connections in the old data source, so that the connections point to valid VDB rather than stale connections. > 4) It would be even nice, "Remember My Decision" kind of preference, that could always create or not create data source, rather than keep asking the user. > BTW, this feature is only useful for the Web Service scenarios, so I would start off with OFF position. May be turn it on only ask when web service model in the work space if you want to be fancy. Also detect the name of data source in the web-service war creation scenarios, or let them create with a button right next to it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2059) Preview VDB should contain only models needed for the preview

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2059?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-2059. ---------------------------------- > Preview VDB should contain only models needed for the preview > ------------------------------------------------------------- > > Key: TEIIDDES-2059 > URL: https://issues.jboss.org/browse/TEIIDDES-2059 > Project: Teiid Designer > Issue Type: Feature Request > Components: Data Preview > Affects Versions: 8.3 > Reporter: Debbie Steigner > > When doing a view data on a table, designer unnecessarily deploys a vdb for ALL models in the project instead of evaluating what is necessary for a particular table in a view model (where I've chosen to preview data) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1635) Designer is not showing the same error in the server log

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1635?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-1635. ---------------------------------- The issue has resolution "Out of date" I am closing the issue. (TD JIRA Clean up) > Designer is not showing the same error in the server log > -------------------------------------------------------- > > Key: TEIIDDES-1635 > URL: https://issues.jboss.org/browse/TEIIDDES-1635 > Project: Teiid Designer > Issue Type: Feature Request > Components: Usability > Affects Versions: 7.4 > Reporter: Van Halbert > Assignee: Barry LaFond > > JBoss developer studio is not returning complete error stack trace. For example, running a query throws error in the designer which is different from error in server log and we would like to get the error whatever is there in the server.log to troubleshoot and fix the issues. > It's really difficult for developers to understand and fix the issues with the way error is shown in the designer compared to more useful error shown in the server.log. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1634) For Komodo, remove UUID from the persisted models, will help with ability to merge models

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1634?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-1634. ---------------------------------- This will be addressed in new tooling. The issue has resolution "Out of date". Closing the issue - TD JIRA Clean up > For Komodo, remove UUID from the persisted models, will help with ability to merge models > ----------------------------------------------------------------------------------------- > > Key: TEIIDDES-1634 > URL: https://issues.jboss.org/browse/TEIIDDES-1634 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: Komodo > > > When saving a model file, don't persist the UUID's in the file. This would make the file smaller and help with the user's ability to manage their models in a SCM and merge the changes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1491) Please investigate the pssibility of adding support for adding wrapper procedures for RPC-encoded procedures

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1491?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-1491. ---------------------------------- Issue was resolved as "Won't fix" TD JIRA Clean up - Closing the issue > Please investigate the pssibility of adding support for adding wrapper procedures for RPC-encoded procedures > ------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1491 > URL: https://issues.jboss.org/browse/TEIIDDES-1491 > Project: Teiid Designer > Issue Type: Enhancement > Components: Modeling > Reporter: Paul Nittel > Priority: Minor > > I was trying to use the NWS Web service (imported as a source) we employ for our quickstart, but when I tried to query it, I received: > select t.* from (call weathersource.invoke(action=>'GET', endpoint=>querystring('', '38.99,-77.02 39.70,-104.80 47.6,-122.30' as listLatLon, 'time-series' as product, '2004-01-01T00:00:00' as "begin", '2013-04-20T00:00:00' as "end", 'maxt' as maxt, 'mint' as mint) )) w, XMLTABLE('/dwml/data/location' passing w.result columns "location-key" string, lat string path 'point/@latitude', "long" string path 'point/@longitude') t > Remote org.teiid.core.TeiidProcessingException: WeatherSource: No namespace on "dwml" element. > The connection URL is: http://graphical.weather.gov/xml/SOAP_server/ndfdXMLserver.php?wsdl > This Jira was requested by a developer as a tickler for future research. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1388) Improve Flat File importer

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1388?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-1388. ---------------------------------- > Improve Flat File importer > -------------------------- > > Key: TEIIDDES-1388 > URL: https://issues.jboss.org/browse/TEIIDDES-1388 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Affects Versions: 7.7, 7.7.1 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: Future > > > The Flat File importer still lacks simplicity. Need to spend another cycle improving usability > PAUL NITTEL wrote: > I'm tinkering with this thing and have a few suggestions. (The problem with coming up with cool wizardly things is they spark other synapses thereby creating an endless flow of work.) > The Create Teiid Flat File Connection action seems to be a mixture of building the data source connection and laying the groundwork for the transformation (like where are the column name and types). Moving this to the Create Source Model wizard might make it easier and flow better for the user. > Rather than checkboxes that presume much about how flat file data may be constructed, how about allowing the user to tell you which lines are contain heading and type info (if any, of course)? In the case of my weird data file, there a comment in line 1, line 2 is blank, line 3 have column names and line 4 has types. Data starts in line 5. > I realize my case is atypical, but might be worth consideration. ;-) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1216) New View Table Wizard

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1216?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-1216. ---------------------------------- > New View Table Wizard > --------------------- > > Key: TEIIDDES-1216 > URL: https://issues.jboss.org/browse/TEIIDDES-1216 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling, Transformations > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: Komodo > > Attachments: Create View Table Wizard.bmml, Create View Table Wizard.png, CreateViewTableWizard.png, View Easy Edit Mockup.bmml, View Easy Edit Mockup.bmml, View Easy Edit Mockup.png > > > In our push to improve usability, a new "Create View Table" wizard could provide a new means to create views using the Join or Union concept. > Result of the wizard would be a complete, valid SQL transformation that is reconciled, use "functions" in Symbol definition and include Criteria -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1149) Managing multiple versions of models

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1149?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-1149. ---------------------------------- > Managing multiple versions of models > ------------------------------------ > > Key: TEIIDDES-1149 > URL: https://issues.jboss.org/browse/TEIIDDES-1149 > Project: Teiid Designer > Issue Type: Feature Request > Components: Eclipse Integration, Modeling > Affects Versions: 7.1.1, 7.4.2 > Reporter: Tom Fonteyne > Fix For: Komodo > > > We have a big requirement to more effectively manage multiple versions of models. In the future, we will have to maintain multiple versions of models and VDBs in order to guarantee compability for some clients while possibly providing new functionality for other clients using the same models. > We will also have "core models" (again possibly multiple releases) of business concepts which will be included in VDBs for specific clients and systems, then changes will need to be merged in from this one core set to many models/VDBs in the future. I posted a question to the SME list about this a few months ago ("Effectively version controlling models"). Ramesh provided some helpful ideas, such as stacking of VDBs, which we would prefer not to do because of foreseen management and performance (query planning) problems, and also how we can deploy multiple versions of the same VDB. > The problem remains however, that the only way we have at present to work with models is interactively through Teiid designer, and the only way to merge selectively (rather than replacing models) is manually. This process would potentially have to be repeated multiple times for each changeset. The customer is concerned that this approach will become unmanageable in the future. > Being able to merge through the designer would be great, but also non-interactively and automatable in some way too. Ideally, we would like to see a greater seperation of model management from the designer (in the same that it was done in a set of reusable classes which the designer makes use of also) so we have the option of using automatable tools (ie. maven) or building or own tools to do this merging. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1119) Need for global workspace location

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1119?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-1119. ---------------------------------- > Need for global workspace location > ---------------------------------- > > Key: TEIIDDES-1119 > URL: https://issues.jboss.org/browse/TEIIDDES-1119 > Project: Teiid Designer > Issue Type: Feature Request > Components: Eclipse Integration > Reporter: Barry LaFond > Assignee: Paul Richardson > Fix For: Komodo > > > With 7.6 Teiid Designer will be managing a new Model Extension framework which allows users to define Model Extension Definitions (MEDs) to inject additional properties into relational, web services, XML document and function models. > Initial design is to maintain a registry or both built-in and user-defined MED's within the user's workspace/.metadata/org.teiid.designer.extension folder. > Designer is also maintaining a similar Teiid Server registry in workspace/.metadata/org.teiid.designer.dqp > The "Import VDB" feature will probably need a place to store a registry of "Translator Overrides" so user can re-use these across VDB's rather than re-inputing these properties manually each time in their VDB editors. > The Data Tools Connection profile registry is also stored in a workspace/.metadata/org.eclipse.datatools.connectivity folder. Data Tool provides input/export features for persisting portions or all of the profile registry across workspace, but requires user to import/export each time. > Eclipse's ".metadata" folder concept is good from a single workspace standpoint, but these registries are: > 1) at risk of being deleted if workspace is cleared > 2) registry data (i.e. files) are not available/exposed for proper version control > So a solution might be to create the concept of a Global Workspace Location. This location would be set by the user if they choose. This location would contain folders for Teiid Server, Model Extension, Translator Overrides, Connection Profiles such that if a user changes workspaces they wouldn't necessarily have to re-import all of this data. > Maybe provide a "Global Workspace Explorer" view that would have some features/actions to do some appropriate management of the artifacts. > This would be a Usability -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues September 2016