June 2016 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2864) NPE's when trying to perform JDBC import from a postgres database

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2864?page=com.atlassian.jira.plu... ] Van Halbert reassigned TEIIDDES-2864: ------------------------------------- Assignee: Van Halbert > NPE's when trying to perform JDBC import from a postgres database > ----------------------------------------------------------------- > > Key: TEIIDDES-2864 > URL: https://issues.jboss.org/browse/TEIIDDES-2864 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 10.0 > Reporter: Van Halbert > Assignee: Van Halbert > > Seeing 2 NPE's, the first one is seen a lot: > java.lang.NullPointerException > at org.teiid.designer.jdbc.ui.wizards.JdbcImportOptionsPage.createModelDefinitionPanel(JdbcImportOptionsPage.java:444) > at org.teiid.designer.jdbc.ui.wizards.JdbcImportOptionsPage.createModelDefinitionTab(JdbcImportOptionsPage.java:245) > at org.teiid.designer.jdbc.ui.wizards.JdbcImportOptionsPage.createControl(JdbcImportOptionsPage.java:228) > at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1216) > at org.eclipse.jface.wizard.WizardDialog.access$4(WizardDialog.java:1208) > at org.eclipse.jface.wizard.WizardDialog$8.run(WizardDialog.java:1197) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1194) > java.lang.NullPointerException > at org.teiid.designer.jdbc.ui.wizards.JdbcImportObjectsPage.refresh(JdbcImportObjectsPage.java:539) > at org.teiid.designer.jdbc.ui.wizards.JdbcImportObjectsPage.setVisible(JdbcImportObjectsPage.java:454) > at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1229) > at org.eclipse.jface.wizard.WizardDialog.access$4(WizardDialog.java:1208) > at org.eclipse.jface.wizard.WizardDialog$8.run(WizardDialog.java:1197) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1194) > at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:885) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2861) Import DDL option is confusing

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2861?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2861: ----------------------------------- Affects Version/s: 10.0.1 (was: 10.0.2) > Import DDL option is confusing > ------------------------------ > > Key: TEIIDDES-2861 > URL: https://issues.jboss.org/browse/TEIIDDES-2861 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 10.0.1 > Reporter: Van Halbert > Attachments: jdg-remote-cache-mat-vdb.xml, portfolio-vdb.xml > > > Have the following comments when trying to use the DDL importer to import a dynamic vdb: > - It refers to everything as DDL, when dynamic vdb is not > - the file chooser defaults to DDL, when maybe it should have an option for .xml > - on the importer, there's a Mode type. When importing dynamic VDB's, this shouldn't apply, because the dynamic vdb can have both virtual and source models. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2450) All role and other vdb editing actions to be undo-able

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2450?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2450: ---------------------------------------- this is just too big of framework to tackle any time soon. May be better suited for next-gen UI (Komodo-based) > All role and other vdb editing actions to be undo-able > ------------------------------------------------------ > > Key: TEIIDDES-2450 > URL: https://issues.jboss.org/browse/TEIIDDES-2450 > Project: Teiid Designer > Issue Type: Quality Risk > Components: VDB & Execution > Reporter: Steven Hawkins > Fix For: Future > > > From using the DV 6.1 Designer it appeared that most vdb editing actions were not undo-able - for example checking or unchecking a resource in the role editor. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2450) All role and other vdb editing actions to be undo-able

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2450?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2450: ----------------------------------- Fix Version/s: Future (was: 10.0.2) > All role and other vdb editing actions to be undo-able > ------------------------------------------------------ > > Key: TEIIDDES-2450 > URL: https://issues.jboss.org/browse/TEIIDDES-2450 > Project: Teiid Designer > Issue Type: Quality Risk > Components: VDB & Execution > Reporter: Steven Hawkins > Fix For: Future > > > From using the DV 6.1 Designer it appeared that most vdb editing actions were not undo-able - for example checking or unchecking a resource in the role editor. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2467) Query Results Table Hides Query Results

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2467?page=com.atlassian.jira.plu... ] Barry LaFond closed TEIIDDES-2467. ---------------------------------- Resolution: Won't Fix > Query Results Table Hides Query Results > --------------------------------------- > > Key: TEIIDDES-2467 > URL: https://issues.jboss.org/browse/TEIIDDES-2467 > Project: Teiid Designer > Issue Type: Bug > Components: Data Preview > Affects Versions: 9.0 > Reporter: Debbie Steigner > Fix For: 10.0.2 > > > The query results table hides results for queries that have a number of rows that would fit inside of the window. After a query was updated, the Result hides the first row, and the user can not scroll up to see that row. > This appears to occur on tables where the number of rows will all fit within the view without scrolling. In these situations the results are available only by clicking on the result tab content and scrolling up with the keyboard. Scrolling with the mouse does not work to show these hidden rows. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2860) Deleting a source model should not delete dependent models and vdbs by default

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2860?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2860: ----------------------------------- Issue Type: Enhancement (was: Bug) Description: For the JDG generate/materialize view use-case, users may want to regenerate their pojo/source table and will want to delete the source model first. (was: When deleting MATVIEW it also wants to delete the view model from where it came. You should be able to delete the MATVIEW table and rerun the MATVIEW creation.) Summary: Deleting a source model should not delete dependent models and vdbs by default (was: deleting MATVIEW deletes the upper view model) Priority: Major (was: Blocker) > Deleting a source model should not delete dependent models and vdbs by default > ------------------------------------------------------------------------------ > > Key: TEIIDDES-2860 > URL: https://issues.jboss.org/browse/TEIIDDES-2860 > Project: Teiid Designer > Issue Type: Enhancement > Components: Modeling > Affects Versions: 10.0.1 > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 10.0.2 > > > For the JDG generate/materialize view use-case, users may want to regenerate their pojo/source table and will want to delete the source model first. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1912) Allow non-managed extension properties

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1912?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1912: ---------------------------------------- implementing this feature would require a whole editing layer to handle decorating the *custom extended* object (table, column, model, etc....), else the user could never find it again to edit. Current model property extensions are handled and editable in the properties panel, but required property definitions (type, format, cell editor) in order to enable editing. > Allow non-managed extension properties > -------------------------------------- > > Key: TEIIDDES-1912 > URL: https://issues.jboss.org/browse/TEIIDDES-1912 > Project: Teiid Designer > Issue Type: Enhancement > Components: ModeShape Integration, Teiid Integration > Reporter: Steven Hawkins > Fix For: No Future > > > Requiring managed extension properties puts additional management burden on users and in the case of missing built-in properties does not allow for an easy way to add the properties. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1912) Allow non-managed extension properties

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1912?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1912: ----------------------------------- Fix Version/s: No Future (was: 10.0.2) > Allow non-managed extension properties > -------------------------------------- > > Key: TEIIDDES-1912 > URL: https://issues.jboss.org/browse/TEIIDDES-1912 > Project: Teiid Designer > Issue Type: Enhancement > Components: ModeShape Integration, Teiid Integration > Reporter: Steven Hawkins > Fix For: No Future > > > Requiring managed extension properties puts additional management burden on users and in the case of missing built-in properties does not allow for an easy way to add the properties. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1898) Connection Profile requires a password for preview

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1898?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1898: ----------------------------------- Fix Version/s: No Future (was: 10.0.2) > Connection Profile requires a password for preview > -------------------------------------------------- > > Key: TEIIDDES-1898 > URL: https://issues.jboss.org/browse/TEIIDDES-1898 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.2 > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Fix For: No Future > > > Some data sources can work without user name and/or password for connecting to the source. So, those properties are not mandatory and requiring them for preview is unnecessary if they are not defined. > In this example, Hive Connection profile was created with username but with out password, when the Teiid Connection importer used and them a connection profile is set on it to use the preview, it failed until a dummy password is provided -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2860) deleting MATVIEW deletes the upper view model

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2860?page=com.atlassian.jira.plu... ] Van Halbert commented on TEIIDDES-2860: --------------------------------------- " when deleting a materialized source table (generated from pojo wizard), the view model does not get deleted." I'm confused in those statement (1st seems to contradict the second). When trying to delete a materialized source table, a wizard pops up and shows that the VDB and View (from which it was created from) are to be deleted. There's no option to not delete the view and VDB. This is the issue. Also, I would have thought if the tables are deleted, that the VDB just be flagged as needs regenerating, not totally deleting the vdb. > deleting MATVIEW deletes the upper view model > --------------------------------------------- > > Key: TEIIDDES-2860 > URL: https://issues.jboss.org/browse/TEIIDDES-2860 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 10.0.1 > Reporter: Van Halbert > Assignee: Barry LaFond > Priority: Blocker > Fix For: 10.0.2 > > > When deleting MATVIEW it also wants to delete the view model from where it came. You should be able to delete the MATVIEW table and rerun the MATVIEW creation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues June 2016