November 2015 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2648) Add option in JDBC importer to set all "updatable" table properties to true/false

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2648?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-2648: -------------------------------------- Assignee: Dan Florian > Add option in JDBC importer to set all "updatable" table properties to true/false > --------------------------------------------------------------------------------- > > Key: TEIIDDES-2648 > URL: https://issues.jboss.org/browse/TEIIDDES-2648 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export, Patch Release > Reporter: Barry LaFond > Assignee: Dan Florian > Fix For: 9.2.1 > > > Add feature similar to TEIIDDES-2624 in JDBC importer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2674) When deleting project with read-only model TD produces 4 warnings instead of 1

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2674?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-2674: -------------------------------------- Assignee: Dan Florian > When deleting project with read-only model TD produces 4 warnings instead of 1 > ------------------------------------------------------------------------------ > > Key: TEIIDDES-2674 > URL: https://issues.jboss.org/browse/TEIIDDES-2674 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling, Patch Release > Affects Versions: 9.0.4 > Environment: MAC OS X > Reporter: Matus Makovy > Assignee: Dan Florian > Priority: Minor > Fix For: 9.2.1 > > Attachments: Screen Shot 2015-10-02 at 9.38.33.png > > > When you try to delete project with read-only model in it, TD shows a warning that there is this kind of model, but instead of one there are 4 warnings. > See screenshot -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2710) WS Create Operation Wizard - Creating a method with no input message

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2710?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-2710: -------------------------------------- Assignee: Barry LaFond > WS Create Operation Wizard - Creating a method with no input message > -------------------------------------------------------------------- > > Key: TEIIDDES-2710 > URL: https://issues.jboss.org/browse/TEIIDDES-2710 > Project: Teiid Designer > Issue Type: Bug > Components: Patch Release, Web Services Support > Affects Versions: 9.0.4 > Reporter: Matus Makovy > Assignee: Barry LaFond > Fix For: 9.2.1 > > > Coppied from BZ: > Description of problem: > Web service model , create operation model does not allow to create operations without input or output. Indeed it's possible to ignore warning messages and create the operation anyway. In that case wizard puts nameless and typeless messages in the schema and requires removing messages from the schema with an alternate editor. > Version-Release number of selected component (if applicable): > > TD 9.0.3.Finalv2015 > How reproducible: > Try to create a new operation in web service model > Steps to Reproduce: > 1. Pick one the interfaces that you have in wsdl > 2. Create a new operation, give it a name > 3. Try to get rid of input message, remove it's name and create > Actual results: > Malformed view schema > Expected results: > create the operation without the undesired message type > Additional info: -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2435) [Usability] The default user when connecting to server should be blanked out

by Andrej Šmigala (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2435?page=com.atlassian.jira.plu... ] Andrej Šmigala commented on TEIIDDES-2435: ------------------------------------------ [~blafond] the problem here is that when you define a new server, the JDBC username is prefilled with 'user', as that used to be the default user when installing DV. This is no longer the case, the DV installer lets the user to specify a different username and actually defaults to 'teiidUser'. So, after defining the server, the user will have to go to Server editor and change the JDBC username anyway, so at that point there seems to be no reason to provide a default value at all. > [Usability] The default user when connecting to server should be blanked out > ---------------------------------------------------------------------------- > > Key: TEIIDDES-2435 > URL: https://issues.jboss.org/browse/TEIIDDES-2435 > Project: Teiid Designer > Issue Type: Enhancement > Components: Patch Release, Teiid Integration > Affects Versions: 9.0.1 > Reporter: Van Halbert > Assignee: Paul Richardson > Fix For: 9.2.1 > > > In old versions of the Teiid server, the username "user" was the default. However, with newer versions, there is no default installed user. The person installing has to set that username. Therefore, its requested that the username in Teiid Designer be blanked our so that it eliminates confusion with prior versions. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2713) UDF jar not referenced in exported dynamic VDB

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2713?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-2713: -------------------------------------- Assignee: Paul Richardson > UDF jar not referenced in exported dynamic VDB > ---------------------------------------------- > > Key: TEIIDDES-2713 > URL: https://issues.jboss.org/browse/TEIIDDES-2713 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Patch Release, VDB & Execution > Affects Versions: 9.0.4 > Reporter: Andrej Šmigala > Assignee: Paul Richardson > Fix For: 9.2.1 > > > When exporting a VDB with a User Defined Function, the information about the UDF jar is not present in the resulting dynamic VDB file. > With regular VDB archives, the UDF jar is added to the lib/ directory within the archive and is referenced like so in META-INF/vdb.xml: > {code:xml} > <entry path="/lib/MyTestUdf-1.0-SNAPSHOT.jar"> > <property name="checksum" value="2689317444"/> > </entry> > {code} > This approach is not possible in case of dynamic VDB defined only as an xml file. It is, however, possible to create a module on the server with UDF jar and then reference it in the *-vdb.xml like so: > {code:xml} > <property name ="lib" value ="mytestudf-module"></property> > {code} > It is currently possible to define such property manually in the VDB editor before exporting, but Designer should be able to define one automatically, or at least warn the user when there is a UDF jar present and the lib property is not defined. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2738) REST procedure not imported correctly from dynamic VDB

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2738?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-2738: -------------------------------------- Assignee: Barry LaFond > REST procedure not imported correctly from dynamic VDB > ------------------------------------------------------- > > Key: TEIIDDES-2738 > URL: https://issues.jboss.org/browse/TEIIDDES-2738 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Patch Release, VDB & Execution > Affects Versions: 9.0.4 > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Fix For: 9.2.1 > > > When importing a dynamic VDB with REST procedure, the created procedure does not have the REST options set. > {code:xml} > <?xml version="1.0" encoding="UTF-8" standalone="no"?> > <vdb name="RestProcedureVdbDynamic" version="1"> > <description /> > <property name="{http://teiid.org/rest}auto-generate" value="true" /> > <model name="ProcedureModel" type="VIRTUAL"> > <metadata type="DDL"><![CDATA[ > SET NAMESPACE 'http://teiid.org/rest' AS REST; > CREATE VIRTUAL PROCEDURE testProc (p1 string(4000)) RETURNS TABLE (xml_out xml) OPTIONS ("REST:METHOD" 'GET', "REST:URI" 'test/{p1}') > AS > BEGIN > SELECT XMLELEMENT(NAME test, XMLFOREST(ProcedureModel.testProc.p1 AS elem1, 'elem2' AS elem2)) AS xml_out; > END; > ]]></metadata> > </model> > </vdb> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2469) [Usability] Problem importing SOAP web service via URL

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2469?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2469: ----------------------------------- Component/s: Patch Release > [Usability] Problem importing SOAP web service via URL > ------------------------------------------------------ > > Key: TEIIDDES-2469 > URL: https://issues.jboss.org/browse/TEIIDDES-2469 > Project: Teiid Designer > Issue Type: Quality Risk > Components: Import/Export, Patch Release > Affects Versions: 9.0 > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 9.2.1 > > Attachments: bug.mov, define-rest-procedure-tags-dialog.png > > > Conversation: > [09:44] <jmarley> vhalbert: do you have a document for import soap web service via url > [09:45] <jmarley> we are getting hung up on creating relational model > [09:45] <jmarley> vhalbert: nevermind, > [09:46] <jmarley> vhalbert: there was an error saying we didn't have a column defined, but it was for a different procedure than the one that was selected, which and we didn't know we needed to select the other procedure and assumed it was issue with current procedure we were working with > [09:47] <vhalbert> jmarley, hm > [09:47] <vhalbert> jmarley, so designer was processing something that wasn't selected > [09:48] <jmarley> vhalbert: yes, and didn't give an indication as to which procedure it was referring to -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2435) [Usability] The default user when connecting to server should be blanked out

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2435?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2435: ----------------------------------- Component/s: Patch Release > [Usability] The default user when connecting to server should be blanked out > ---------------------------------------------------------------------------- > > Key: TEIIDDES-2435 > URL: https://issues.jboss.org/browse/TEIIDDES-2435 > Project: Teiid Designer > Issue Type: Enhancement > Components: Patch Release, Teiid Integration > Affects Versions: 9.0.1 > Reporter: Van Halbert > Assignee: Paul Richardson > Fix For: 9.2.1 > > > In old versions of the Teiid server, the username "user" was the default. However, with newer versions, there is no default installed user. The person installing has to set that username. Therefore, its requested that the username in Teiid Designer be blanked our so that it eliminates confusion with prior versions. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[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: ----------------------------------- Component/s: Patch Release > 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: 9.2.1 > > > 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 (v6.4.11#64026)

10 years, 5 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 updated TEIIDDES-2473: ----------------------------------- Component/s: Patch Release > 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 > Fix For: 9.2.1 > > > 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 (v6.4.11#64026)

10 years, 5 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 November 2015