April 2014 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-379) ERROR Previewing data for nested mapping class in XML Document model

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-379?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-379. ----------------------------------- Resolution: Won't Fix very old issue and previewing XML documents has not been a feature asked for by users. > ERROR Previewing data for nested mapping class in XML Document model > -------------------------------------------------------------------- > > Key: TEIIDDES-379 > URL: https://issues.jboss.org/browse/TEIIDDES-379 > Project: Teiid Designer > Issue Type: Bug > Reporter: Barry LaFond > Assignee: Barry LaFond > > During testing of Books XML tried to query nested mapping class. Received SQL Server error which was masking the real problem with unresolved/unindexed Input Set objects in criteria. > Suggest we disable previewing Mapping Classes (Staging tables would be OK) until we can find a solution, which may be treating a mapping class like an access pattern. Ramesh suggested we "Swipe" the SQL for a mapping class, present to user a list of "Input Set Parameters" (similar to procedures & access patterns), and inject the user-supplied values into the SQL. The actual SQL called will NOT be Select * FROM XXXXX, but the modified Mapping Class's SQL. > NOTE that the Preview data will be success for the "TOP" mapping class because it doesn't utilize an Input Set. -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-355) Designer - Add context sensitive help

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-355?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-355. ----------------------------------- Resolution: Won't Fix JBoss Tools practice is to not embed help into the kit, and hence no help to reference from Eclipse context framework > Designer - Add context sensitive help > -------------------------------------- > > Key: TEIIDDES-355 > URL: https://issues.jboss.org/browse/TEIIDDES-355 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Warren Gibson > Assignee: Barry LaFond > > Add context sensitive help to MM Designer -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-389) Query Plan Viewer: Double-clicking on a source query access node creates a screen that spans two windows in a multi-monitor display, but should default to single screen

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-389?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-389. ----------------------------------- Resolution: Out of Date Designer doesn't use it's custom SQL perspective. It defaults to DTP's Data Source Perspective > Query Plan Viewer: Double-clicking on a source query access node creates a screen that spans two windows in a multi-monitor display, but should default to single screen > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-389 > URL: https://issues.jboss.org/browse/TEIIDDES-389 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Reporter: Michael Walker > Assignee: Barry LaFond > Priority: Minor > Attachments: screenshot-1.jpg > > > Double-click on a source query access node in the query plan viewer in Designer. If you are using a multiple-monitor display, the source query will span both screens. This is awkward and hard to read. The default should be single-screen if possible. Minor usability issue. -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-518) DTP context menu options on Teiid tables should consider whether virtual model supports update.

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-518?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-518. ----------------------------------- Fix Version/s: (was: Future) Resolution: Won't Fix DTP is not under Designer control > DTP context menu options on Teiid tables should consider whether virtual model supports update. > ----------------------------------------------------------------------------------------------- > > Key: TEIIDDES-518 > URL: https://issues.jboss.org/browse/TEIIDDES-518 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 7.0 > Environment: Teiid Designer 7.0 + JBoss Dev Studio 3.0.1GA > Teiid 7.1 Alpha on EAP 5.1 > RHEL 6, OpenJDK 1.6 > Reporter: Ken Johnson > > In DTP, Context menu for Table contains several options under Data->(Edit, Load, Extract, Sample Contents). For virtual tables, Extract and Sample Contents are fine. Edit and Load will attempt to write data. Thus a few issues: > a) These options should be disabled if the table in question does not have Supports Update checked. > b) These options should be tested when the table *does* have Update and Insert procedures defined. > c) Tables in SYS schema should never be writable. > When working with physical tables, all options should be available and work correctly. Cursory testing indicates this is the case - at least with a MySQL data source underlying the model. -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2094) Support for dynamic extension metadata

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2094?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2094: ---------------------------------------- I don't see any difference in your 2 use-cases. It's obvious that extension properties on view models requires MEDs since there are no corresponding "annotations" in the Teiid Runtime. Source models, by their nature, are tied to translators which do have coded annotations that are used to define the extended properties. When dealing with custom translators, users must write the translator and probably use tooling to write that translator. To me, it seems more intuitive to require the user to define their Extension properties in the form of a schema (aka MED file) . We happen to have tooling that can help users create error-free MEDs but the format/definition is pretty straight forward and can be edited by hand if tooling is an issue. I think the biggest issue I have is that we now have a disconnect between design-time and runtime extension metadata. * Extending our metamodels has always been an available feature in Designer, whether the old EMF-based extension model or the new MXD (MED) framework. * Our MED use-cases/requirements included providing a means to : ** define and model new relational properties that the runtime supported (built-in MEDs) ** allow users to add design-time only extension properties (not added to indexed VDB metadata) ** allow users to add runtime extension properties required by custom translators ** allow users to version-control their MED files (including validation to warn users of conflicting or out of date versions applied to models) This jira is pushing for Designer to: * remove the requirement for MEDs being used for custom translators * make it much harder to present any sense of version-control/validation for the user in the tooling since there doesn't appear to be any info coming through the API to make that available * force the user to extract and register the MED definition from a source model if they wish to create a source model from scratch for that same data source/translator Note that *@ExtensionMetadataProperty* annotation only supports: *applicable Object type(s), display name, description, isRequired* MED properties also support the following methods which is needed by the UI: * *getDefaultValue()* * *isMasked()* * *allowedValues()* * *fixedValue()* * *Locale support for Display names and Descriptions* Because of this missing data, the conversion of the runtime property definition into a design-time property definition will be incomplete. Designer can infer that a type Boolean will mean true/false, but a String property with specific "allowed values" will be treated as a generic editable string value. Because all MED properties have a "default" value, only non-default values are actually indexed. So still not sure on how to satisfy both the support for runtime dynamic extension metadata and make it useful in design-time and clear to the user what is going on. > Support for dynamic extension metadata > --------------------------------------- > > Key: TEIIDDES-2094 > URL: https://issues.jboss.org/browse/TEIIDDES-2094 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Reporter: Ramesh Reddy > Assignee: Paul Richardson > Priority: Critical > > Currently when Teiid core implements a new translator or customer/user implements a custom translator that has extension metadata, before they can use the translator in Designer to do some modeling, they need to define MED and register it. > With completion of TEIID-2904, in Teiid 8.7, a Admin api method can be used to interrogate the extension metadata properties defined for a translator. > Currently if user uses Teiid Connection importer with any new translator, it ignores all the extension metadata properties and removes them from the returned DDL that Designer did not recognize. That is really bad for custom connectors, because the VDB will not work properly once it is deployed back to Teiid Server. > I propose to devise a way to generate a dynamic MED for the purposes of current metadata import of the source and use it during the import and not ignore those extension metadata properties. > Depending upon implementation detail, we can also read the translators and their extension metadata support during the initial connection time and create all the required MEDs and register them. -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1127) Auto-generate REST Procedures

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1127?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-1127: -------------------------------- Fix Version/s: 8.6 (was: 8.5) > Auto-generate REST Procedures > ----------------------------- > > Key: TEIIDDES-1127 > URL: https://issues.jboss.org/browse/TEIIDDES-1127 > Project: Teiid Designer > Issue Type: Enhancement > Components: Web Services Support > Affects Versions: 7.5 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 8.6 > > > Need way to auto-generate procedures exposed over REST. Will need some sort of wizard so the user can name the procedures, REST-METHOD and set the URI. -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1829) Add Dynamic Parameter Capability to REST Importer

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1829?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-1829: -------------------------------- Fix Version/s: 8.6 (was: 8.5) > Add Dynamic Parameter Capability to REST Importer > -------------------------------------------------- > > Key: TEIIDDES-1829 > URL: https://issues.jboss.org/browse/TEIIDDES-1829 > Project: Teiid Designer > Issue Type: Feature Request > Components: Web Services Support > Affects Versions: 8.2 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 8.6 > > > Currently the REST importer just takes a URL with parameters included. Need to add an option for dynamic parameters. This will mean generating a procedure instead of a table and building the URL dynamically using the passed in values. -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2054) Change JSON in Generated REST to be Accepts Header Driven Instead of a Different URL

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2054?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-2054: -------------------------------- Fix Version/s: 8.6 (was: 8.5) > Change JSON in Generated REST to be Accepts Header Driven Instead of a Different URL > ------------------------------------------------------------------------------------ > > Key: TEIIDDES-2054 > URL: https://issues.jboss.org/browse/TEIIDDES-2054 > Project: Teiid Designer > Issue Type: Feature Request > Components: Web Services Support > Affects Versions: 8.3.1 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 8.6 > > > Currently, the generated REST WAR has a different path for JSON vs XML. This should be driven by the Accepts header and use the same same URL for both XML and JSON. -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1882) Add Support for JSON Based Web Service Importing

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1882?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-1882: -------------------------------- Fix Version/s: 8.6 (was: 8.5) > Add Support for JSON Based Web Service Importing > ------------------------------------------------ > > Key: TEIIDDES-1882 > URL: https://issues.jboss.org/browse/TEIIDDES-1882 > Project: Teiid Designer > Issue Type: Feature Request > Components: Web Services Support > Affects Versions: 8.2 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 8.6 > > > The current web service importer only supports XML responses. Need to add support for JSON responses. -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2065) Add support for Accumulo Translator

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2065?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2065: ----------------------------------- Assignee: Paul Richardson > Add support for Accumulo Translator > ----------------------------------- > > Key: TEIIDDES-2065 > URL: https://issues.jboss.org/browse/TEIIDDES-2065 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Reporter: Ramesh Reddy > Assignee: Paul Richardson > Fix For: 8.5 > > > Teiid added Accumulo translator in Teiid 8.7 version. This translator comes with few extension metadata properties. This translator also supports import of metadata if the data is defined in the Accumulo. > Designer needs to add, "Model Extension Defs" and validate the import process through Teiid Connection Importer. > BTW, I tried with latest 8.4 nightly it did not work, and did not give any errors out. Just said could not create VDB, no error logs in server. I added the extension model defn manually. > The translator docs can be found at https://docs.jboss.org/author/display/TEIID/Apache+Accumulo+Translator -- 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

10 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues April 2014