January 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1557) Add Greenplum importer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1557?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1557: ----------------------------------- Fix Version/s: Future (was: 8.1) > Add Greenplum importer > ---------------------- > > Key: TEIIDDES-1557 > URL: https://issues.jboss.org/browse/TEIIDDES-1557 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 8.0 > Reporter: Van Halbert > Fix For: Future > > > Add support for importing from a Greenplum data source. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-95) Allow Drag and Drop models into the VDB Editor

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-95?page=com.atlassian.jira.plugi... ] Mark Drilling resolved TEIIDDES-95. ----------------------------------- Fix Version/s: No Future (was: 8.1) Resolution: Won't Fix Discussed with Barry... In light of changes to VDBEditor regarding scoping to project and etc we decided not to address this issue. > Allow Drag and Drop models into the VDB Editor > ---------------------------------------------- > > Key: TEIIDDES-95 > URL: https://issues.jboss.org/browse/TEIIDDES-95 > Project: Teiid Designer > Issue Type: Feature Request > Components: Editors > Affects Versions: 6.0.0 > Reporter: Mark Drilling > Assignee: Mark Drilling > Priority: Minor > Fix For: No Future > > > Allow user to more easily add files from their workspace via button or drag n drop. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1288) Enable the viewing of a query plan by importing from a file / clipboard

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1288?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-1288. ------------------------------------- Resolution: Done Added toolbar action to import a plan from a file. pull request: https://github.com/Teiid-Designer/teiid-designer/pull/72 > Enable the viewing of a query plan by importing from a file / clipboard > ----------------------------------------------------------------------- > > Key: TEIIDDES-1288 > URL: https://issues.jboss.org/browse/TEIIDDES-1288 > Project: Teiid Designer > Issue Type: Enhancement > Components: Diagrams, Import/Export > Reporter: Van Halbert > Assignee: Mark Drilling > Fix For: 8.1 > > > It would be a good enhancement to the viewing of the query plan, if the person could import a query plan. Because the person who wants to view a query plan in designer, may not be the one who created it. I thought of that today when I wanted to view a plan someone attached to a jira. This plan was pretty big and hard to view just using a text editor. If I could have used designer to view the plan in a graphical manner, it would make the viewing easier. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1557) Add Greenplum importer

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1557?page=com.atlassian.jira.plu... ] Steven Hawkins commented on TEIIDDES-1557: ------------------------------------------ A specific importer for greenplum is not yet needed. > Add Greenplum importer > ---------------------- > > Key: TEIIDDES-1557 > URL: https://issues.jboss.org/browse/TEIIDDES-1557 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 8.0 > Reporter: Van Halbert > Fix For: 8.1 > > > Add support for importing from a Greenplum data source. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1557) Add Greenplum importer

by Van Halbert (JIRA)

Van Halbert created TEIIDDES-1557: ------------------------------------- Summary: Add Greenplum importer Key: TEIIDDES-1557 URL: https://issues.jboss.org/browse/TEIIDDES-1557 Project: Teiid Designer Issue Type: Feature Request Components: Import/Export Affects Versions: 8.0 Reporter: Van Halbert Fix For: 8.1 Add support for importing from a Greenplum data source. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1555) Errors with Web Service model operation validation

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1555?page=com.atlassian.jira.plu... ] Paul Richardson commented on TEIIDDES-1555: ------------------------------------------- Fix pushed to address this at http://github.com/Teiid-Designer/teiid-designer/commit/c7c0b429a80e4162e2... Under review and testing. > Errors with Web Service model operation validation > -------------------------------------------------- > > Key: TEIIDDES-1555 > URL: https://issues.jboss.org/browse/TEIIDDES-1555 > Project: Teiid Designer > Issue Type: Feature Request > Components: Transformations > Affects Versions: 8.1 > Reporter: Barry LaFond > Assignee: Paul Richardson > Fix For: 8.1 > > > Created WS model from simple relational model. > Validation results in the following T-editor message: > _ERROR: TEIID30387 Could not load UDF "+", since its invocation class "org.teiid.query.function.FunctionMethods" could not be found._ > And a ClassCastException > java.lang.ClassCastException: org.teiid82.sql.impl.xml.MappingNodeImpl cannot be cast to org.teiid.designer.xml.IMappingElement > at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.createMapping(MappingDocumentFormatter.java:787) > at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.processChildren(MappingDocumentFormatter.java:1116) > at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.processNamespaces(MappingDocumentFormatter.java:1196) > at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.createDocumentNode(MappingDocumentFormatter.java:702) > at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.createMapping(MappingDocumentFormatter.java:748) > at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.createMappingString(MappingDocumentFormatter.java:821) > at org.teiid.designer.transformation.aspects.sql.TreeMappingRootSqlAspect.getTransformation(TreeMappingRootSqlAspect.java:285) > at org.teiid.designer.transformation.aspects.sql.TreeMappingRootSqlAspect.getTransformationInfo(TreeMappingRootSqlAspect.java:333) > at org.teiid.designer.core.metadata.runtime.RuntimeAdapter.addTransformationWords(RuntimeAdapter.java:412) > at org.teiid.designer.core.metadata.runtime.RuntimeAdapter.addIndexWord(RuntimeAdapter.java:172) > at org.teiid.designer.core.index.ModelIndexer.addIndexWord(ModelIndexer.java:311) > at org.teiid.designer.core.index.ModelIndexer.index(ModelIndexer.java:164) > at org.teiid.designer.core.index.Index.add(Index.java:127) > at org.teiid.designer.core.index.ModelIndexer.indexResource(ModelIndexer.java:240) > at org.teiid.designer.core.builder.ModelBuildUtil.indexResource(ModelBuildUtil.java:308) > at org.teiid.designer.core.builder.ModelBuildUtil.indexResources(ModelBuildUtil.java:333) > at org.teiid.designer.core.builder.ModelBuildUtil.indexResources(ModelBuildUtil.java:324) > at org.teiid.designer.core.builder.ModelBuildUtil.buildResources(ModelBuildUtil.java:123) > at org.teiid.designer.core.builder.ModelBuilder$1.run(ModelBuilder.java:138) -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1111) Create a model(s) (view/source) based on the schema and type of data source provided

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1111?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1111: ---------------------------------------- The current WSDL > SOAP importer eventually gets to the point of using the Schema for the defined WSDL. The Schema is then "tailored" based on if the user is working on the Request or Response document. The class "org.teiid.designer.modelgenerator.wsdl.ui.wizards.soap.ImportWsdlSchemaHandler" would be the starting point, maybe.... > Create a model(s) (view/source) based on the schema and type of data source provided > ------------------------------------------------------------------------------------ > > Key: TEIIDDES-1111 > URL: https://issues.jboss.org/browse/TEIIDDES-1111 > Project: Teiid Designer > Issue Type: Sub-task > Components: Import/Export > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Labels: importers, teiid, xml > Fix For: 8.1 > > > There have been many requests from users in the recent past to auto-generate source and view models that can consume the XML coming in the specified in a schema file. The current XML document model, take in a XSD and maps the relational data into XML data. This request is exact opposite of it in the consuming side. The data is coming in as XML, need to expose them as relational. > I strongly believe that this needs to be done as part of TEIIDDES-1078, not create separate importers to minimize the user experience with modelling any XML data. > The data sources can File, SOAP service or Rest service currently, but may not be restricted to those. -- 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

13 years, 3 months

1
0
0 / 0

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

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1388?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1388: ----------------------------------- Fix Version/s: Future (was: 8.1) > 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 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1273) XML File Importer Enhancements

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1273?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1273. ------------------------------------ Resolution: Done Added duplicate column name validation. Finish won't enable unless duplicate name error is corrected. Also added auto-gen of xxxx_Source and xxxx_View model names. > XML File Importer Enhancements > ------------------------------ > > Key: TEIIDDES-1273 > URL: https://issues.jboss.org/browse/TEIIDDES-1273 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Affects Versions: 7.7 > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Fix For: 8.1 > > > There couple of suggestion I have to make XML/WSDL importers little more user friedly > - let the user double click on the element/attribute in the XML tree to add as column. Currently user need to right click and select to add. > - When a element/attribute is added have it decorated with some different graphic such that user knows that particular element/attribute is already added. (Elements can be added twice, there is no restrictions) > - Currently root element where the XPATH expressions for the columns are rooted from need to be selected by right clicking on the element. However the default shows empty. This should be by default set to "/", or have some mechanism to force this selection. Note also that if the user changes this after the column definitions, the original XPATH expressions need to be re-calculated to new root, or make the root read-only after the first selection. Another good guess for this is where the user first selected element from, set to that. > - may be a little text above the XML tree saying double click to select the columns would be helpful, I found right click by goofing around. > - I also believe "add" buttons not that useful, especially if they just adding a empty column and already have a "add selection as new column" button. Actually it is confusing. Keep up/down. "delete" is useful. You could also enable "delete" key on selection > - when same column is added, a different aliased name should be selected, as e1 as e1_1, e1_2 currently I see same name is given. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1556) In 8.0, the function metamodel has been deprecated, can the new model wizard drop down indicate as such

by Van Halbert (JIRA)

Van Halbert created TEIIDDES-1556: ------------------------------------- Summary: In 8.0, the function metamodel has been deprecated, can the new model wizard drop down indicate as such Key: TEIIDDES-1556 URL: https://issues.jboss.org/browse/TEIIDDES-1556 Project: Teiid Designer Issue Type: Enhancement Components: Dialogs, Usability Affects Versions: 8.0 Reporter: Van Halbert When selecting New Model Wizard, the Model Class drop down should indicate the Function Model is "Deprecated". -- 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

13 years, 3 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 January 2013