January 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1575) Create new importer based on DDL recieved via Teiid Admin API through a temporary dynamic VDB containing Data Source info only

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1575?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-1575: -------------------------------------- Assignee: Mark Drilling > Create new importer based on DDL recieved via Teiid Admin API through a temporary dynamic VDB containing Data Source info only > ------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1575 > URL: https://issues.jboss.org/browse/TEIIDDES-1575 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export, Teiid Integration > Affects Versions: 8.1 > Reporter: Barry LaFond > Assignee: Mark Drilling > Priority: Critical > Fix For: 8.1 > > > Newer data sources supported by Teiid cannot be imported into Designer because of special metadata structure or NON-JDBC compliance. Since Teiid supports these new data sources, they can expose a common Teiid DDL through the Admin API if a dynamic VDB and the data source is created and deployed on a server. > We need to create an Import option that works with connection profiles AND generic dynamic VDB data source properties so users can import the DDL and end up constructing relational models just like our JDBC importer. > Potential DBs include: > * Hive - TEIIDDES-1193 > * Mondrian - TEIIDDES-930 > * Intersystems Cache - TEIIDDES-904 > * Ingres - TEIIDDES-883 > * LDAP - TEIIDDES-305 -- 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

11 years, 10 months

1
0
0 / 0

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

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1216?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-1216: -------------------------------------- Assignee: Barry LaFond (was: Mark Drilling) > 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: 8.1 > > 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 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1575) Create new importer based on DDL recieved via Teiid Admin API through a temporary dynamic VDB containing Data Source info only

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1575: -------------------------------------- Summary: Create new importer based on DDL recieved via Teiid Admin API through a temporary dynamic VDB containing Data Source info only Key: TEIIDDES-1575 URL: https://issues.jboss.org/browse/TEIIDDES-1575 Project: Teiid Designer Issue Type: Feature Request Components: Import/Export, Teiid Integration Affects Versions: 8.1 Reporter: Barry LaFond Priority: Critical Fix For: 8.1 Newer data sources supported by Teiid cannot be imported into Designer because of special metadata structure or NON-JDBC compliance. Since Teiid supports these new data sources, they can expose a common Teiid DDL through the Admin API if a dynamic VDB and the data source is created and deployed on a server. We need to create an Import option that works with connection profiles AND generic dynamic VDB data source properties so users can import the DDL and end up constructing relational models just like our JDBC importer. Potential DBs include: * Hive - TEIIDDES-1193 * Mondrian - TEIIDDES-930 * Intersystems Cache - TEIIDDES-904 * Ingres - TEIIDDES-883 * LDAP - TEIIDDES-305 -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1574) Table Filter Properties has no effect on import

by Tom Johnston (JIRA)

Tom Johnston created TEIIDDES-1574: -------------------------------------- Summary: Table Filter Properties has no effect on import Key: TEIIDDES-1574 URL: https://issues.jboss.org/browse/TEIIDDES-1574 Project: Teiid Designer Issue Type: Bug Components: Import/Export Reporter: Tom Johnston -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1573) Create Komodo Build Job

by Dan Florian (JIRA)

Dan Florian created TEIIDDES-1573: ------------------------------------- Summary: Create Komodo Build Job Key: TEIIDDES-1573 URL: https://issues.jboss.org/browse/TEIIDDES-1573 Project: Teiid Designer Issue Type: Task Components: komodo-build Affects Versions: Komodo Reporter: Dan Florian Assignee: Dan Florian Create Jenkins Tycho build job that runs nightly and periodically during the day if there is new code committed. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1566) Create Web Service On procedure generates invalid sql

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1566?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1566. ------------------------------------ Resolution: Done Completed. In GenerateXsdHelper.generateSql() method added a object type check. If Result Set object, then delegate to the procedure's full name instead. {code} if( source instanceof ProcedureResult) { newSql.append(TransformationHelper.getSqlEObjectFullName(((ProcedureResult)source).getProcedure())); } else { newSql.append(TransformationHelper.getSqlEObjectFullName(source)); } {code} > Create Web Service On procedure generates invalid sql > ----------------------------------------------------- > > Key: TEIIDDES-1566 > URL: https://issues.jboss.org/browse/TEIIDDES-1566 > Project: Teiid Designer > Issue Type: Bug > Components: Web Services Support > Affects Versions: 7.4.2 > Environment: Windows 7 > Reporter: Michael Conner > Assignee: Barry LaFond > Priority: Minor > Fix For: 8.1 > > > # I select on a procedure, {{Rsw_CustomerUnitProc}}, whose result is {{Rsw_CustomerUnitResult}}. > # Choose Modeling > Create Web Service > # Enter in the appropriate info in the web service, including {{Rsw_CustomerUnit_Output}} for the Output Schema Model. > The generated code for the output Model Transformation Editor is: > {code} > SELECT > * > FROM > Procedures.Rsw_CustomerUnitProc.Rsw_CustomerUnitResult > {code} > And there is an error: > {{ERROR: Group does not exist: Procedures.Rsw_CustomerUnitProc.Rsw_CustomerUnitResult}} > Removing the Result seems to fix the problem: > {code} > SELECT > * > FROM > Procedures.Rsw_CustomerUnitProc > {code} -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1566) Create Web Service On procedure generates invalid sql

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1566?page=com.atlassian.jira.plu... ] Barry LaFond edited comment on TEIIDDES-1566 at 1/31/13 9:02 AM: ----------------------------------------------------------------- Completed. In GenerateXsdHelper.generateSql() method added a object type check. If Result Set object, then delegate to the procedure's full name instead. {code} if( source instanceof ProcedureResult) { newSql.append(TransformationHelper.getSqlEObjectFullName(((ProcedureResult)source).getProcedure())); } else { newSql.append(TransformationHelper.getSqlEObjectFullName(source)); } {code} Note the commit message incorrectly references JIRA 1572 instead of this one. was (Author: blafond): Completed. In GenerateXsdHelper.generateSql() method added a object type check. If Result Set object, then delegate to the procedure's full name instead. {code} if( source instanceof ProcedureResult) { newSql.append(TransformationHelper.getSqlEObjectFullName(((ProcedureResult)source).getProcedure())); } else { newSql.append(TransformationHelper.getSqlEObjectFullName(source)); } {code} > Create Web Service On procedure generates invalid sql > ----------------------------------------------------- > > Key: TEIIDDES-1566 > URL: https://issues.jboss.org/browse/TEIIDDES-1566 > Project: Teiid Designer > Issue Type: Bug > Components: Web Services Support > Affects Versions: 7.4.2 > Environment: Windows 7 > Reporter: Michael Conner > Assignee: Barry LaFond > Priority: Minor > Fix For: 8.1 > > > # I select on a procedure, {{Rsw_CustomerUnitProc}}, whose result is {{Rsw_CustomerUnitResult}}. > # Choose Modeling > Create Web Service > # Enter in the appropriate info in the web service, including {{Rsw_CustomerUnit_Output}} for the Output Schema Model. > The generated code for the output Model Transformation Editor is: > {code} > SELECT > * > FROM > Procedures.Rsw_CustomerUnitProc.Rsw_CustomerUnitResult > {code} > And there is an error: > {{ERROR: Group does not exist: Procedures.Rsw_CustomerUnitProc.Rsw_CustomerUnitResult}} > Removing the Result seems to fix the problem: > {code} > SELECT > * > FROM > Procedures.Rsw_CustomerUnitProc > {code} -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1566) Create Web Service On procedure generates invalid sql

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1566?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-1566: -------------------------------------- Assignee: Barry LaFond (was: Ted Jones) > Create Web Service On procedure generates invalid sql > ----------------------------------------------------- > > Key: TEIIDDES-1566 > URL: https://issues.jboss.org/browse/TEIIDDES-1566 > Project: Teiid Designer > Issue Type: Bug > Components: Web Services Support > Affects Versions: 7.4.2 > Environment: Windows 7 > Reporter: Michael Conner > Assignee: Barry LaFond > Priority: Minor > Fix For: 8.1 > > > # I select on a procedure, {{Rsw_CustomerUnitProc}}, whose result is {{Rsw_CustomerUnitResult}}. > # Choose Modeling > Create Web Service > # Enter in the appropriate info in the web service, including {{Rsw_CustomerUnit_Output}} for the Output Schema Model. > The generated code for the output Model Transformation Editor is: > {code} > SELECT > * > FROM > Procedures.Rsw_CustomerUnitProc.Rsw_CustomerUnitResult > {code} > And there is an error: > {{ERROR: Group does not exist: Procedures.Rsw_CustomerUnitProc.Rsw_CustomerUnitResult}} > Removing the Result seems to fix the problem: > {code} > SELECT > * > FROM > Procedures.Rsw_CustomerUnitProc > {code} -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-662) Allow export DDL to clipboard or SQL Workbook to facilitate devs using DTP to instantiate the schema on a particular DB

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-662?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-662: ---------------------------------- Fix Version/s: 8.1 (was: Future) > Allow export DDL to clipboard or SQL Workbook to facilitate devs using DTP to instantiate the schema on a particular DB > ----------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-662 > URL: https://issues.jboss.org/browse/TEIIDDES-662 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 7.1 > Environment: JBDS 4 Beta 1, RHEL 6 > Reporter: Ken Johnson > Assignee: Paul Richardson > Priority: Minor > Fix For: 8.1 > > > When exporting DDL, it would be nice to have the option to export to the cilpboard or SQL Workbook in addition to exporting to files. This will assist the Eclipse developer using DTP and instantiating schema in a DB to support materialized view staging. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-662) Allow export DDL to clipboard or SQL Workbook to facilitate devs using DTP to instantiate the schema on a particular DB

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-662?page=com.atlassian.jira.plug... ] Paul Richardson resolved TEIIDDES-662. -------------------------------------- Resolution: Done > Allow export DDL to clipboard or SQL Workbook to facilitate devs using DTP to instantiate the schema on a particular DB > ----------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-662 > URL: https://issues.jboss.org/browse/TEIIDDES-662 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 7.1 > Environment: JBDS 4 Beta 1, RHEL 6 > Reporter: Ken Johnson > Assignee: Paul Richardson > Priority: Minor > Fix For: Future > > > When exporting DDL, it would be nice to have the option to export to the cilpboard or SQL Workbook in addition to exporting to files. This will assist the Eclipse developer using DTP and instantiating schema in a DB to support materialized view staging. -- 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

11 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 January 2013