February 2011 - teiid-designer-issues

[JBoss JIRA] Updated: (TEIIDDES-392) WSDL into Relational Model Importer should to support basic auth for HTTP WSDL URIs.

by John Doyle (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-392?page=com.atlassian.jira.plug... ] John Doyle updated TEIIDDES-392: -------------------------------- Summary: WSDL into Relational Model Importer should to support basic auth for HTTP WSDL URIs. (was: SAP WSDL URLs do not validate with the SOAP-Relational importer.) Assignee: (was: John Doyle) Affects Version/s: 6.0.0 7.3 Description: The SOAP-Relational importer can import WSDLs from URLs or the file system. WSDLs offered by SAP Netweaver via URSs do not validate because SAP requires HTTP basic auth to get the WSDL. The importer should support this and the new Web Service connection profile should provide the credentials. (was: The SOAP-Relational importer can import WSDLs from URLs or the file system. WSDLs offered by SAP Netweaver via URSs do not validate.) > WSDL into Relational Model Importer should to support basic auth for HTTP WSDL URIs. > -------------------------------------------------------------------------------------- > > Key: TEIIDDES-392 > URL: https://issues.jboss.org/browse/TEIIDDES-392 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 6.0.0, 7.3 > Reporter: John Doyle > > The SOAP-Relational importer can import WSDLs from URLs or the file system. WSDLs offered by SAP Netweaver via URSs do not validate because SAP requires HTTP basic auth to get the WSDL. The importer should support this and the new Web Service connection profile should provide the credentials. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-293) WSDL to Relational Model Importer: WSDL imports into model with incorredt types and column names.

by John Doyle (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-293?page=com.atlassian.jira.plug... ] John Doyle updated TEIIDDES-293: -------------------------------- Summary: WSDL to Relational Model Importer: WSDL imports into model with incorredt types and column names. (was: WSDL to Relational Importer: WSDL causes NPE when generating model.) Affects Version/s: 7.2 7.3 Component/s: (was: Import/Export) I retested this in JBDS 4.0.0 (aka Designer 7.1.1) and it no longer produces an NPE, and our new XML modeling technique should be able to handle request of arbitrary complexity. However, this WSDL produces a model that uses incorrect data types in the XMLTABLE fuctions. int rather than integer datetime rather than timestamp Also, some of the columns that get their names qualified do not get the name qualified in the XMLTABLE function. For instance the column on the procedure is precision_, but the XMLTABLE function contains precision. > WSDL to Relational Model Importer: WSDL imports into model with incorredt types and column names. > ------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-293 > URL: https://issues.jboss.org/browse/TEIIDDES-293 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.1, 7.2, 7.3 > Reporter: John Doyle > Assignee: John Doyle > Labels: wsdltorelational > Attachments: TmsWebService.wsdl > > > The attached WSDL causes an NPE when the model objects are being created. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (TEIIDDES-291) XML-Relational and WSDL-Relational importers do not understand the substitutionGroup attribute of xsd:Element

by John Doyle (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-291?page=com.atlassian.jira.plug... ] John Doyle commented on TEIIDDES-291: ------------------------------------- The WSDL to Relational Importer has changed it's implementation since this JIRA was written, and the XML-Relational importer no longer exists. However this JIRA still applies. I think in order to resolve this issue correctly (I'm not convinced that this occurs often enough to warrant a fix), the importer would need to recognize the choice and prompt the user to "pick one". Alternatively, the importer could build view models for all the options, but the user would have to create some dynamic SQL to figure out what views to execute depending upon what the XML actually is at runtime. I can't imagine that actually working. > XML-Relational and WSDL-Relational importers do not understand the substitutionGroup attribute of xsd:Element > ------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-291 > URL: https://issues.jboss.org/browse/TEIIDDES-291 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.1 > Reporter: John Doyle > Assignee: John Doyle > Priority: Minor > Attachments: XSDTest7.java > > > See the issue tracker: > https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&ti... > Take a look at section 2.2.2.2 of the XSD spec. > http://www.w3.org/TR/xmlschema-1/ > Or this nice example: > http://www.w3schools.com/Schema/schema_complex_subst.asp > As I read the spec, these substitution groups have no effect on the structure of the XML defined by the XSD, only the names that allowed for a particular element in the XML. > We don't support this in the importer now. We would have to add functionality to find the substitution groups and add additional XPaths so that the connector could either /name or /navn in the xml document. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIIDDES-291) XML-Relational and WSDL-Relational importers do not understand the substitutionGroup attribute of xsd:Element

by John Doyle (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-291?page=com.atlassian.jira.plug... ] John Doyle reassigned TEIIDDES-291: ----------------------------------- Assignee: (was: John Doyle) > XML-Relational and WSDL-Relational importers do not understand the substitutionGroup attribute of xsd:Element > ------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-291 > URL: https://issues.jboss.org/browse/TEIIDDES-291 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.1 > Reporter: John Doyle > Priority: Minor > Attachments: XSDTest7.java > > > See the issue tracker: > https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&ti... > Take a look at section 2.2.2.2 of the XSD spec. > http://www.w3.org/TR/xmlschema-1/ > Or this nice example: > http://www.w3schools.com/Schema/schema_complex_subst.asp > As I read the spec, these substitution groups have no effect on the structure of the XML defined by the XSD, only the names that allowed for a particular element in the XML. > We don't support this in the importer now. We would have to add functionality to find the substitution groups and add additional XPaths so that the connector could either /name or /navn in the xml document. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIIDDES-881) Teiid Designer admin connections should be based on a configurable runtime.

by John Doyle (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-881?page=com.atlassian.jira.plug... ] John Doyle reassigned TEIIDDES-881: ----------------------------------- Assignee: (was: John Doyle) > Teiid Designer admin connections should be based on a configurable runtime. > --------------------------------------------------------------------------- > > Key: TEIIDDES-881 > URL: https://issues.jboss.org/browse/TEIIDDES-881 > Project: Teiid Designer > Issue Type: Feature Request > Components: VDB & Execution > Affects Versions: 7.1.1, 7.2, 7.3 > Reporter: John Doyle > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > The admin and preview connections for Teiid Designer rely on paths that specify plugin + version. Updates to the tooling therefore break existing connections when the version changes. We should instead rely on a user configurable runtime configuration like other JBoss runtimes. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-881) Teiid Designer admin connections should be based on a configurable runtime.

by John Doyle (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-881?page=com.atlassian.jira.plug... ] John Doyle moved JBIDE-7225 to TEIIDDES-881: -------------------------------------------- Project: Teiid Designer (was: Tools (JBoss Tools)) Key: TEIIDDES-881 (was: JBIDE-7225) Affects Version/s: 7.2 7.1.1 7.3 (was: 3.2.0.M2) Component/s: VDB & Execution (was: teiid) Fix Version/s: (was: LATER) > Teiid Designer admin connections should be based on a configurable runtime. > --------------------------------------------------------------------------- > > Key: TEIIDDES-881 > URL: https://issues.jboss.org/browse/TEIIDDES-881 > Project: Teiid Designer > Issue Type: Feature Request > Components: VDB & Execution > Affects Versions: 7.2, 7.1.1, 7.3 > Reporter: John Doyle > Assignee: John Doyle > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > The admin and preview connections for Teiid Designer rely on paths that specify plugin + version. Updates to the tooling therefore break existing connections when the version changes. We should instead rely on a user configurable runtime configuration like other JBoss runtimes. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (TEIIDDES-880) Execution Plan for a query executed in Teiid is hard to find in JBDS

by John Doyle (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-880?page=com.atlassian.jira.plug... ] John Doyle commented on TEIIDDES-880: ------------------------------------- DTP has two separate implemtations for fetching the plan and executing the query. Teiid does not make this distinction. My initial investigation into this JIRA leads me to think that we need to stop using the DTP supplied BaseExplainAction and CallableSQLResultRunnable as our implemetation and roll our own implementation that handles both concerns in a single execution. > Execution Plan for a query executed in Teiid is hard to find in JBDS > -------------------------------------------------------------------- > > Key: TEIIDDES-880 > URL: https://issues.jboss.org/browse/TEIIDDES-880 > Project: Teiid Designer > Issue Type: Feature Request > Components: VDB & Execution > Affects Versions: 7.1.1, 7.2, 7.3 > Reporter: Ramesh Reddy > > Currently viewing of the execution plan is little cumbersome, it is not readily available as it did previous incarnation of the MetaMatrix Designer. Currently, the user needs to right click on the query and select "Teiid_7.1 --> Query Plan" see the query plan. > When a query is executed, the statement executed has the query already associated with it, so there is no good reason for user to take yet another step before they can see the query plan. It should be automatically populated in the "Execution Plan" tab when the query is executed. Or provide tool bar button on the "SQL Results" panel, that will take user to the "Execution Plan" of the current query. In case of query plan not available this tool bar button could be greyed out. > Since the query plan is in XML, show it in XML editor (read-only), that will let the user collapse or expand the the nodes to see and understand it, otherwise these are rather long, could be confusing to scroll. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-880) Execution Plan for a query executed in Teiid is hard to find in JBDS

by John Doyle (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-880?page=com.atlassian.jira.plug... ] John Doyle moved JBIDE-7887 to TEIIDDES-880: -------------------------------------------- Project: Teiid Designer (was: Tools (JBoss Tools)) Key: TEIIDDES-880 (was: JBIDE-7887) Component/s: VDB & Execution (was: teiid) Fix Version/s: (was: 3.2.x) > Execution Plan for a query executed in Teiid is hard to find in JBDS > -------------------------------------------------------------------- > > Key: TEIIDDES-880 > URL: https://issues.jboss.org/browse/TEIIDDES-880 > Project: Teiid Designer > Issue Type: Feature Request > Components: VDB & Execution > Affects Versions: 7.1.1, 7.2, 7.3 > Reporter: Ramesh Reddy > Assignee: John Doyle > > Currently viewing of the execution plan is little cumbersome, it is not readily available as it did previous incarnation of the MetaMatrix Designer. Currently, the user needs to right click on the query and select "Teiid_7.1 --> Query Plan" see the query plan. > When a query is executed, the statement executed has the query already associated with it, so there is no good reason for user to take yet another step before they can see the query plan. It should be automatically populated in the "Execution Plan" tab when the query is executed. Or provide tool bar button on the "SQL Results" panel, that will take user to the "Execution Plan" of the current query. In case of query plan not available this tool bar button could be greyed out. > Since the query plan is in XML, show it in XML editor (read-only), that will let the user collapse or expand the the nodes to see and understand it, otherwise these are rather long, could be confusing to scroll. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-880) Execution Plan for a query executed in Teiid is hard to find in JBDS

by John Doyle (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-880?page=com.atlassian.jira.plug... ] John Doyle updated TEIIDDES-880: -------------------------------- Assignee: (was: John Doyle) Affects Version/s: 7.2 7.1.1 7.3 > Execution Plan for a query executed in Teiid is hard to find in JBDS > -------------------------------------------------------------------- > > Key: TEIIDDES-880 > URL: https://issues.jboss.org/browse/TEIIDDES-880 > Project: Teiid Designer > Issue Type: Feature Request > Components: VDB & Execution > Affects Versions: 7.1.1, 7.2, 7.3 > Reporter: Ramesh Reddy > > Currently viewing of the execution plan is little cumbersome, it is not readily available as it did previous incarnation of the MetaMatrix Designer. Currently, the user needs to right click on the query and select "Teiid_7.1 --> Query Plan" see the query plan. > When a query is executed, the statement executed has the query already associated with it, so there is no good reason for user to take yet another step before they can see the query plan. It should be automatically populated in the "Execution Plan" tab when the query is executed. Or provide tool bar button on the "SQL Results" panel, that will take user to the "Execution Plan" of the current query. In case of query plan not available this tool bar button could be greyed out. > Since the query plan is in XML, show it in XML editor (read-only), that will let the user collapse or expand the the nodes to see and understand it, otherwise these are rather long, could be confusing to scroll. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIIDDES-879) [Designer] Provide Teiid driver in a plug-in wrapper to save the user the step of creating a DTP Driver Definition

by John Doyle (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-879?page=com.atlassian.jira.plug... ] John Doyle reassigned TEIIDDES-879: ----------------------------------- Assignee: (was: John Doyle) > [Designer] Provide Teiid driver in a plug-in wrapper to save the user the step of creating a DTP Driver Definition > ------------------------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-879 > URL: https://issues.jboss.org/browse/TEIIDDES-879 > Project: Teiid Designer > Issue Type: Feature Request > Components: Eclipse Integration > Affects Versions: 7.1.1, 7.2, 7.3 > Reporter: Brian Fitzpatrick > > For the Teiid driver... Is it possible to wrap the driver jar in a plug-in and automatically set it up? Or set up multiple versions (7.0, 7.1, etc.)? Though it's server-dependent, we should be able to control that enough to simplify life for the user and auto-configure a driver instance. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 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 February 2011