March 2014 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2090) Connection profile wizard dialog for Ingres database has labels on right side

by Lucie Fabrikova (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2090?page=com.atlassian.jira.plu... ] Lucie Fabrikova updated TEIIDDES-2090: -------------------------------------- Attachment: ingresDB.png > Connection profile wizard dialog for Ingres database has labels on right side > ----------------------------------------------------------------------------- > > Key: TEIIDDES-2090 > URL: https://issues.jboss.org/browse/TEIIDDES-2090 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 8.3.2 > Environment: Windows, Macos, Linux > Reporter: Lucie Fabrikova > Priority: Minor > Attachments: ingresDB.png > > -- 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

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2089) Teiid connection import throws "java.lang.IllegalArgumentException: The supplied model folder refers to an existing non-model project" on Windows

by Lucie Fabrikova (JIRA)

Lucie Fabrikova created TEIIDDES-2089: ----------------------------------------- Summary: Teiid connection import throws "java.lang.IllegalArgumentException: The supplied model folder refers to an existing non-model project" on Windows Key: TEIIDDES-2089 URL: https://issues.jboss.org/browse/TEIIDDES-2089 Project: Teiid Designer Issue Type: Bug Affects Versions: 8.3.2 Reporter: Lucie Fabrikova Import-> Teiid designer -> Teiid connection >> source model: Next button doesn't move to next page of wizard on Windows (both 7, XP), but throws following exception in error log: java.lang.IllegalArgumentException: The supplied model folder refers to an existing non-model project. at org.teiid.designer.ddl.importer.DdlImporter.setModelFolder(DdlImporter.java:344) at org.teiid.designer.teiidimporter.ui.wizard.TeiidImportManager.setTargetModelLocation(TeiidImportManager.java:433) at org.teiid.designer.teiidimporter.ui.wizard.TeiidImportWizard.init(TeiidImportWizard.java:134) at org.eclipse.ui.internal.dialogs.WorkbenchWizardNode.getWizard(WorkbenchWizardNode.java:185) at org.eclipse.jface.wizard.WizardSelectionPage.getNextPage(WizardSelectionPage.java:104) at org.eclipse.ui.internal.dialogs.WorkbenchWizardSelectionPage.getNextPage(WorkbenchWizardSel ... -- 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

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2088) Data preview throws No teiid instance found on Windows

by Lucie Fabrikova (JIRA)

Lucie Fabrikova created TEIIDDES-2088: ----------------------------------------- Summary: Data preview throws No teiid instance found on Windows Key: TEIIDDES-2088 URL: https://issues.jboss.org/browse/TEIIDDES-2088 Project: Teiid Designer Issue Type: Bug Affects Versions: 8.3.2 Environment: Windows 7 Reporter: Lucie Fabrikova Data preview fails with following exception: java.lang.Exception: No Teiid Instance found (server not started) at org.teiid.designer.runtime.TeiidServer.connect(TeiidServer.java:182) at org.teiid.designer.runtime.TeiidServer.dataSourceExists(TeiidServer.java:540) at org.teiid.designer.runtime.preview.PreviewManager.ensureConnectionInfoIsValid(PreviewManager.java:519) at org.teiid.designer.runtime.preview.PreviewManager.previewSetup(PreviewManager.java:1286) at org.teiid.designer.runtime.ui.preview.PreviewDataWorker$1.run(PreviewDataWorker.java:232) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) -- 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

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2087) Teiid Connection Importer - problem with google source 'refresh key' property

by Mark Drilling (JIRA)

Mark Drilling created TEIIDDES-2087: --------------------------------------- Summary: Teiid Connection Importer - problem with google source 'refresh key' property Key: TEIIDDES-2087 URL: https://issues.jboss.org/browse/TEIIDDES-2087 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 8.4 Reporter: Mark Drilling Assignee: Mark Drilling Fix For: 8.5 In teiid connection importer, select to create a new 'google' source. 'refresh key' is shown as a required property and user is forced to enter a value. But, refresh key is not required for 'ClientLogin' auth, just 'OAAuth'. The user should not be required to enter for ClientLogin auth -- 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

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2086) Need ConnectionProfile for Google Spreadsheet sources

by Mark Drilling (JIRA)

Mark Drilling created TEIIDDES-2086: --------------------------------------- Summary: Need ConnectionProfile for Google Spreadsheet sources Key: TEIIDDES-2086 URL: https://issues.jboss.org/browse/TEIIDDES-2086 Project: Teiid Designer Issue Type: Enhancement Affects Versions: 8.4 Reporter: Mark Drilling Currently there is no connection profile in Designer for creating a google spreadsheet source. The only way to create the datasource in Designer (that I know of) is to launch Teiid Connection Importer and create it on the first page of the wizard. However even that is not working currently (see linked jira). -- 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

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2085) Creation of Google DataSource in Teiid Connection Importer fails - cant proceed

by Mark Drilling (JIRA)

Mark Drilling created TEIIDDES-2085: --------------------------------------- Summary: Creation of Google DataSource in Teiid Connection Importer fails - cant proceed Key: TEIIDDES-2085 URL: https://issues.jboss.org/browse/TEIIDDES-2085 Project: Teiid Designer Issue Type: Bug Affects Versions: 8.4 Reporter: Mark Drilling Assignee: Mark Drilling Fix For: 8.5 In the Teiid Connection Importer, select and create a google DataSource. When it gets created, there is no 'driver' associated with it. You cant proceed to the next page. -- 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

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1846) Top Down modeling, when importing to create views, allow for default syntax to applied

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1846?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1846: ---------------------------------------- Setting the default SQL will be easy. Hard part is identifying all the use-cases and places where an empty virtual table/procedure would be created. 1) New Child/Sibling > Table... or Procedure... wizards? 2) ??? There is a TransformationNewModelObjectHelper class that is called each time a new Transformation root is created so it set's up all the root's child/nested roots etc... We could maybe piggy back on to this? > Top Down modeling, when importing to create views, allow for default syntax to applied > -------------------------------------------------------------------------------------- > > Key: TEIIDDES-1846 > URL: https://issues.jboss.org/browse/TEIIDDES-1846 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 8.5 > > > When a user is starting from a top-down approach (building the views) to design their data layers, and will be performing an import to create the view layer, it would speed up the iterative development of build / deploy / test (not preview) if when the view is built (on import), it can contain valid syntax so that the model will validate. Example of syntax could be, "Select '1'" or "Select 'view not defined'" or throw an exception. This would enable the modeler to implement the views at their pace and have it deployable, rather than having to go thru every view and add syntax before its valid. This is akin to JAVA and NOOP'ing the methods. -- 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

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2084) Upgrade to Teiid 8.7 source code

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-2084: -------------------------------------- Summary: Upgrade to Teiid 8.7 source code Key: TEIIDDES-2084 URL: https://issues.jboss.org/browse/TEIIDDES-2084 Project: Teiid Designer Issue Type: Task Components: Build, Teiid Integration Affects Versions: 8.5 Reporter: Barry LaFond Assignee: Paul Richardson Priority: Blocker Fix For: 8.5 Release 8.5 will upgrade to using Teiid 8.7 Final source when it's released. -- 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

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2050) Full Temp Table support in Designer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2050?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2050: ---------------------------------------- Need a clearer definition of some of these terms. * Currently *session/block* is not a Design-time term * What does *not a schema entry* mean? * Would all temp tables be *virtual* tables? * Looks very similar to our Materialized Views feature where the view table references a source/materialized table > Full Temp Table support in Designer > ----------------------------------- > > Key: TEIIDDES-2050 > URL: https://issues.jboss.org/browse/TEIIDDES-2050 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 8.5 > > > Per TEIIDDES-1794 there are more areas Designer needs to add support for temporary tables: > ... the full array of temp table stuff we currently support is: > * Teiid global temporary table (a virtual entry - which from an engine perspective can be on any model type) > * Teiid temporary table (not a schema entry in the design time metadata, scoped to a session/block) > * Teiid temporary table backed by a physical table (not a schema entry in the design time metadata, scoped to a session/block - the physical table could be a temporary one) > Eventually we would also like to have an ease of use path to simply create a teiid temporary table and have the backing table created on a source automatically - similar to the data shipment join temporary table creation. -- 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

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1732) Stream line steps to implement all the steps around materialization

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1732?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1732: ---------------------------------------- Currently in Designer you can 1) Right-click on a virtual table and select *Modeling > Create Materialized Views" 2) Select/create new Source Model (materialized landing location) 3) click Finish/OK and it'll create the corresponding source table and reference that table in the original virtual 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 > Assignee: Barry LaFond > Fix For: 8.5 > > > 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

12 years

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 March 2014