June 2018 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2474) Update rest logic to be streaming

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2474?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2474: ----------------------------------- Fix Version/s: 11.3 (was: 11.2) > Update rest logic to be streaming > --------------------------------- > > Key: TEIIDDES-2474 > URL: https://issues.jboss.org/browse/TEIIDDES-2474 > Project: Teiid Designer > Issue Type: Quality Risk > Components: Patch Release, Teiid Integration, Web Services Support > Reporter: Steven Hawkins > Assignee: Ted Jones > Fix For: 11.3 > > > With TEIID-3390 Teiid will by default cleanup temp lobs when a result/statement is closed. TeiidRSProviderPost would need to implement StreamingOutput or other logic similar to the server side TeiidRSProvider to properly handle the streaming. As a workaround older generated rest wars will need to be setup with connection pools that set the session variable clean_lobs_onclose to false - see https://docs.jboss.org/author/display/TEIID/LOBs -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2473) Support multiple metadata tags

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2473?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2473. ------------------------------------ Fix Version/s: (was: 11.2) Resolution: Won't Do > Support multiple metadata tags > ------------------------------ > > Key: TEIIDDES-2473 > URL: https://issues.jboss.org/browse/TEIIDDES-2473 > Project: Teiid Designer > Issue Type: Feature Request > Components: Patch Release, Teiid Integration > Reporter: Steven Hawkins > Assignee: Dan Florian > > With TEIID-3372 we allowed metadata tags under a model, rather than relying on comma separated values. Any Designer side logic dealing with the DMR layer will need to be updated to match the new server side logic - see ModelMetaData getSourceMetadataType and getSourceMetadataText -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2318) Add support for wildcards in WSDL to Web Service importer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2318?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2318: ----------------------------------- Fix Version/s: 11.3 (was: 11.2) > Add support for wildcards in WSDL to Web Service importer > --------------------------------------------------------- > > Key: TEIIDDES-2318 > URL: https://issues.jboss.org/browse/TEIIDDES-2318 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export, Patch Release > Affects Versions: 8.3.3 > Reporter: Debbie Steigner > Assignee: Ted Jones > Fix For: 11.3 > > > Add support for Schema wildcards [1] to the WSDL to Web Service Importer. Currently you'll receive an NPE. > [1] http://www.w3.org/TR/xmlschema-1/#Wildcards -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2270) Add capability to import a project for migrations.

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2270?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2270. ------------------------------------ Fix Version/s: (was: 11.2) Resolution: Won't Do > Add capability to import a project for migrations. > -------------------------------------------------- > > Key: TEIIDDES-2270 > URL: https://issues.jboss.org/browse/TEIIDDES-2270 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 8.5 > Reporter: Hisanobu Okuda > Assignee: Barry LaFond > > This capability would allow a user to easily upgrade their Designer version without losing anything. The workspace export/import would bring along projects, preferences, connector bindings, extension jars, etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2265) Allow MultiSelect Columns for creation of indexes

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2265?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2265: ----------------------------------- Fix Version/s: Future (was: 11.2) > Allow MultiSelect Columns for creation of indexes > ------------------------------------------------- > > Key: TEIIDDES-2265 > URL: https://issues.jboss.org/browse/TEIIDDES-2265 > Project: Teiid Designer > Issue Type: Enhancement > Components: Modeling > Reporter: Tom Johnston > Assignee: Barry LaFond > Fix For: Future > > > I just realized a pain point. > I have a need to create a number of indexes on views (as they are going to be materialized) but there seems no easy way but one by one. > I envision the following: > Multi-select columns (in Model explorer OR Table editor ) and click Modeling and choose Create index (also UK and PK I would think) .. suggest a 'template' (i.e. tableName_ColumnName_IX (auto add 1...x if something or more than one exists) If I choose 2 cols from one table then a check to create one or multiple (default to multiple) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2232) Cannot create JDBC/Oracle connection profile using ServiceName syntax

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2232?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2232: ----------------------------------- Fix Version/s: Future (was: 11.2) > Cannot create JDBC/Oracle connection profile using ServiceName syntax > --------------------------------------------------------------------- > > Key: TEIIDDES-2232 > URL: https://issues.jboss.org/browse/TEIIDDES-2232 > Project: Teiid Designer > Issue Type: Bug > Components: Patch Release, Teiid Integration > Affects Versions: 8.4 > Reporter: Tom Johnston > Assignee: Barry LaFond > Fix For: Future > > Attachments: Connection.PNG, Plugins.PNG, Update_Site.PNG > > > Cannot successfully create a jdbc url like: > "jdbc:oracle:thin:scott/tiger@//myhost:1521/myservicename" > which is found here: > http://docs.oracle.com/cd/B14117_01/java.101/b10979/urls.htm > Note the "../myservicename" -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2219) Preview Issue - when non-Type4 JDBC driver is used.

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2219?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2219. ------------------------------------ Fix Version/s: (was: 11.2) Resolution: Won't Do > Preview Issue - when non-Type4 JDBC driver is used. > --------------------------------------------------- > > Key: TEIIDDES-2219 > URL: https://issues.jboss.org/browse/TEIIDDES-2219 > Project: Teiid Designer > Issue Type: Bug > Components: Data Preview, Patch Release > Affects Versions: 8.5 > Reporter: Mark Drilling > Assignee: Mark Drilling > Attachments: ojdbc14.jar > > > Encountered issue when trying to preview an Oracle source table in Designer. The preview failed with the following in the server log: > 10:39:44,877 WARN [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue0) TEIID30020 Processing exception for request N0JYBgYp8yw2.0 'TEIID30498 Capabilities for OracleSource were not avaialable. The command could not be planned properly.'. Originally QueryPlannerException PlanToProcessConverter.java:324. Enable more detailed logging to see the entire stacktrace. > Upon debug, I found that the 'type' for my deployed oracle driver 'ojdbc14.jar' was not found on the server. The ojdbc14.jar was actually getting deployed in ExecutionAdmin, but the type was not present - because it was not a type4 jdbc driver. > However, the preview proceeded (and failed) with the above exception. > We need to investigate and handle this case more gracefully in Designer. The preview should not proceed - we should catch this error and display to the user - and stop the preview attempt. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2052) 'Mark as Deployable' on a war not working for remote (OpenShift) server

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2052?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2052. ------------------------------------ Fix Version/s: (was: 11.2) Resolution: Won't Do > 'Mark as Deployable' on a war not working for remote (OpenShift) server > ----------------------------------------------------------------------- > > Key: TEIIDDES-2052 > URL: https://issues.jboss.org/browse/TEIIDDES-2052 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 8.3.1 > Reporter: Mark Drilling > Assignee: Mark Drilling > > I created a war (using Rest War generator) in Designer and added it to my project. Then to deploy it, I selected it and used the 'Mark as Deployable" action. > This worked fine on my local server (both deploy and undeploy) but then I switched to an OpenShift external server instance (used port-forwarding). > The 'Mark as Deployable' action doesnt work for the Openshift external server. Maybe the action is doing a copy of the war into the deployments folder? > We don't provide the action, but we should either troubleshoot or potentially provide our own action which deploys a war using the admin api. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

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 updated TEIIDDES-2050: ----------------------------------- Fix Version/s: Future (was: 11.2) > 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: Future > > > 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 was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1809) WAR File (REST, SOAP) Creation usability enhancements

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1809?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1809: ----------------------------------- Fix Version/s: Future (was: 11.2) > WAR File (REST, SOAP) Creation usability enhancements > ------------------------------------------------------ > > Key: TEIIDDES-1809 > URL: https://issues.jboss.org/browse/TEIIDDES-1809 > Project: Teiid Designer > Issue Type: Enhancement > Components: Patch Release, Web Services Support > Reporter: Ramesh Reddy > Assignee: Ted Jones > Fix For: Future > > > I have seen so many time in the community, where users are confused in asking them to create JNDI file to VDB and deploy the VDB and WAR file. I have two suggestions in this regard to help improve the situation > 1) Instead of (or in addition) asking to enter {REPLACE_WITH_VDB_JNDI_NAME}, offer to create data source to the VDB. If the server is attached, you have all details, or pop up create datasource dialog to create. > 2) Instead of (or in addition) to saving the WAR file, offer to deploy directly to the server, that will save time and would seem seamless operation we can provide. > 3) I often find myself struck in figuring out what is WSDL Endpoint or what are REST endpoints exposed by the WAR deployed, it there is any help we can show at the end of this dialog box (if they choose to deploy) that would save time in them figuring out (going to documentation etc). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 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 June 2018