December 2017 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1128) Implement The Model Registry View's Find Reference Action

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1128?page=com.atlassian.jira.plu... ] Barry LaFond closed TEIIDDES-1128. ---------------------------------- Resolution: Won't Do > Implement The Model Registry View's Find Reference Action > --------------------------------------------------------- > > Key: TEIIDDES-1128 > URL: https://issues.jboss.org/browse/TEIIDDES-1128 > Project: Teiid Designer > Issue Type: Task > Components: Views > Affects Versions: 7.6 > Reporter: Dan Florian > Assignee: Barry LaFond > Fix For: Future > > > The "Find References" action will find all models that have applied the selected model extension definition. The results of the action should be displayed in Eclipse's search results view. Double-click in the results should open the model. The design of the search results should patterned after the Java->References results. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1001) Merge the "Transformations - Import/Export SQL " actions with the Import Text Files > Relational Virtual Tables feature

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1001?page=com.atlassian.jira.plu... ] Barry LaFond closed TEIIDDES-1001. ---------------------------------- Resolution: Won't Do > Merge the "Transformations - Import/Export SQL " actions with the Import Text Files > Relational Virtual Tables feature > ----------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1001 > URL: https://issues.jboss.org/browse/TEIIDDES-1001 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export, Transformations > Affects Versions: 7.5 > Reporter: Barry LaFond > Fix For: Future > > > The Text file importer contains a "Relational Virtual Tables" option. There is also a "Transformations - Import SQL" action which performs basically the same function but has a different format. > We'd like to merge these concepts into one and make it clearer to the user what's going on and be more flexible about format -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-956) In Designer, when there is an error, provide context in project explorer view mouseover or table view mouseover

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-956?page=com.atlassian.jira.plug... ] Barry LaFond closed TEIIDDES-956. --------------------------------- Resolution: Won't Do > In Designer, when there is an error, provide context in project explorer view mouseover or table view mouseover > --------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-956 > URL: https://issues.jboss.org/browse/TEIIDDES-956 > Project: Teiid Designer > Issue Type: Enhancement > Components: Modeling > Affects Versions: 7.3 > Environment: JBDS 4.0.0 GA > Reporter: Joel Tosi > Fix For: Komodo > > > When doing some modeling in Designer, create an error state - for example create a foreign key relationship with one side missing. You will get the error in the Message Log stating the error, but also a visual on the table in the model as well as the model in project view (red Xs). > Please support a mouseover affect - i.e. if I mouseover the table (where the red X is) I would see the error. Same thing for the project explorer view. This would be more consistant with development in Eclipse -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-924) Error creating virtual model with multi_byte characters - Lexical error: Lexical error at line 1, column 30. Encountered: "\u00e5" (229), after : ""

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-924?page=com.atlassian.jira.plug... ] Barry LaFond closed TEIIDDES-924. --------------------------------- Resolution: Out of Date > Error creating virtual model with multi_byte characters - Lexical error: Lexical error at line 1, column 30. Encountered: "\u00e5" (229), after : "" > ----------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-924 > URL: https://issues.jboss.org/browse/TEIIDDES-924 > Project: Teiid Designer > Issue Type: Bug > Components: Transformations > Reporter: Warren Gibson > Attachments: ScreenShot001.bmp, multi_byte.zip > > > The objective of this test was to test multi_byte handling from a Postgres DB through the > modeling process and ultimately querying a VDB. This includes > multi byte (Chinese characters) in the table name, column names, and > the data base data. I used a Postgres DB for the test. I was able to > connect and successfully query the DB with a direct connection using > pgAdmin III, SqlWorkbench, and Squirrel receiving the correct > Chinese characters back. > However, I have encountered a problem when attempting to model > using the DB. I created a project in Designer and imported the DB > table. The imported model appear to be correct in Designer (at least > the Table and columns show up with Chinese characters and no errors > are visible. See ScreenShot001.bmp However when I create a virtual > view model by transforming it from the imported model I get the > following error: > Lexical error: Lexical error at line 1, column 30. Encountered: > "\u00e5" (229), after : "" multi_byte_virtual.xmi /multi_byte åƒ_å__ > I can provide the Postgres DB url if you need it. The project is attached: multi_byte.zip -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-984) Create or update existing Test Scripts with artifacts

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-984?page=com.atlassian.jira.plug... ] Barry LaFond closed TEIIDDES-984. --------------------------------- Resolution: Won't Do > Create or update existing Test Scripts with artifacts > ----------------------------------------------------- > > Key: TEIIDDES-984 > URL: https://issues.jboss.org/browse/TEIIDDES-984 > Project: Teiid Designer > Issue Type: Task > Components: Documentation > Affects Versions: 7.5 > Reporter: Barry LaFond > Assignee: Barry LaFond > Priority: Critical > Fix For: Future > > > Several of the E2E and integration test scripts are outdated and need to be improved and/or cleaned up. > In addition, these scripts are used by QE to create SWT Bot tests. > This jira is parent task to spend some time in 7.5 release to provide up-to-date or new scripts along with compatible artifacts (XMI models, VDB's, XML Schema files, *.txt files) that can be used to create automated SWT Bot tests and to assist in better milestone and release testing. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-898) reconsiler issues with secondary set query branches

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-898?page=com.atlassian.jira.plug... ] Barry LaFond closed TEIIDDES-898. --------------------------------- Resolution: Out of Date > reconsiler issues with secondary set query branches > --------------------------------------------------- > > Key: TEIIDDES-898 > URL: https://issues.jboss.org/browse/TEIIDDES-898 > Project: Teiid Designer > Issue Type: Bug > Components: Transformations > Affects Versions: 7.4 > Reporter: Steven Hawkins > Priority: Minor > > The reconsiler doesn't work well with union branches that don't have derived column names matching the view e.g. select 1 as x, 2 as y union all select 3, 4 > The second branch will initially not be matched with output symbols. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-812) DDL Export XSLT files need to be upgraded/improved

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-812?page=com.atlassian.jira.plug... ] Barry LaFond closed TEIIDDES-812. --------------------------------- Resolution: Won't Do Support for DDL export for non-Teiid JDBC DBs has been limited and not intended to be improved or updated. Not related to any Teiid runtime features. > DDL Export XSLT files need to be upgraded/improved > -------------------------------------------------- > > Key: TEIIDDES-812 > URL: https://issues.jboss.org/browse/TEIIDDES-812 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.1.1, 7.2, 7.3 > Reporter: Barry LaFond > Priority: Critical > Fix For: Future > > > After working import issue TEIIDDES-215, it's become apparent that our XSLT's for various DB's need to be revisited. > For instance, there is no logic in PostgreSQL version to check for integer types that have AUTOINCREMENT == TRUE. These should be exported as SERIAL datatypes. Same for BIGSERIAL. > There is other missing logic. > We need to: > 1) Create a doc or series of docs describing what datatype conversions should be done on IMPORT JDBC and EXPORT DDL > 2) Create sub-tasks for implementing these docs for all DB's > 3) Possibly create extension point(s) to handle "new" DB types more effeciently -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-696) Clicking "Restore Default" in Editor Prefs deletes entries from list of tables

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-696?page=com.atlassian.jira.plug... ] Barry LaFond closed TEIIDDES-696. --------------------------------- Resolution: Won't Do > Clicking "Restore Default" in Editor Prefs deletes entries from list of tables > ------------------------------------------------------------------------------ > > Key: TEIIDDES-696 > URL: https://issues.jboss.org/browse/TEIIDDES-696 > Project: Teiid Designer > Issue Type: Feature Request > Components: Dialogs > Affects Versions: 7.1.1 > Environment: Windows, JBDS 4.0 Beta 1 > Reporter: Paul Nittel > Assignee: Barry LaFond > Priority: Minor > Fix For: Future > > Attachments: EvenMoreMissing.jpg, TablesWithSomeMissing.jpg > > > I was testing the Windows > Preferences > Teiid Designer > Editor - Table Tab and went to restore the default values, after reordering columns in the Columns table. When I did so, the entry for the Columns table vanished! Tried it again on a couple of other table entries and they, too, were removed from the list. I clicked OK. Looked again and they were gone. Restarted the Designer and they were still gone. > Had I canceled, it would have been OK, but it shouldn't have happened anyway. > Happy Halloween? (Screenshots are attached. No exceptions were noted.) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-683) JDBC Importer cannot connect with DB unless the ConnectionProfile has username and password.

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-683?page=com.atlassian.jira.plug... ] Barry LaFond closed TEIIDDES-683. --------------------------------- Resolution: Out of Date > JDBC Importer cannot connect with DB unless the ConnectionProfile has username and password. > -------------------------------------------------------------------------------------------- > > Key: TEIIDDES-683 > URL: https://issues.jboss.org/browse/TEIIDDES-683 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.1 > Reporter: John Doyle > Fix For: Future > > > The UI in the JDBC importer allows a user to provide a password at import time, rather than keep it in the ConnectionProfile, for security purposes. In theory DTP supports this use and has a connect() method that allows a user to pass the username and password. In practice there is a defect in the ConnectionProfiles provided in the DTP enablement project. The username and password are not used. > This means that when a Teiid Designer user selects a ConnectionProfile w/o a password in the JDBC importer and supplies the password in our UI, the connection will fail. > Here's the eclipse bug. > https://bugs.eclipse.org/bugs/show_bug.cgi?id=328738 > Targeted to be fixed in DTP 1.9. > For our purposes the JDBC importer should validate that the profile has a password before attempting to connect, and inform the user that Teiid Designer can only use profiles with full credentials. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-438) XML large model mapping (Better handling of Large XML Files)

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-438?page=com.atlassian.jira.plug... ] Barry LaFond closed TEIIDDES-438. --------------------------------- Resolution: Won't Do XML Document Model Support is deprecated and future Teiid Web Service solutions use alternative methods. > XML large model mapping (Better handling of Large XML Files) > ------------------------------------------------------------ > > Key: TEIIDDES-438 > URL: https://issues.jboss.org/browse/TEIIDDES-438 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Marc Shirley > Fix For: Future > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 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 December 2017