January 2014 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1982) Improve Error Dialog message for VDB deployment where source doesnt exist

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1982?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-1982: -------------------------------------- Assignee: Barry LaFond > Improve Error Dialog message for VDB deployment where source doesnt exist > ------------------------------------------------------------------------- > > Key: TEIIDDES-1982 > URL: https://issues.jboss.org/browse/TEIIDDES-1982 > Project: Teiid Designer > Issue Type: Enhancement > Components: VDB & Execution > Affects Versions: 8.2 > Reporter: Mark Drilling > Assignee: Barry LaFond > Fix For: 8.4 > > Attachments: ErrorDialog.png, MongoProjectSet.zip > > > In some cases, when a user tries to deploy a VDB where one of the SourceModel DS does not exist, the user is prompted whether to create the source. > I encountered a case though where an Error Dialog was displayed instead, with the message "No Connection Information in model xxx.xmi". For this case(Mongo) there is no CP available. > Attaching model project set to reproduce, and a screen shot of the dialog. > Message could be more informative, e.g. "The Data Source for model xxx.xmi cannot be found on server, and no CP information is available" or similar. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1868) 8.3 Release Work

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1868?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1868. ------------------------------------ Resolution: Done Done > 8.3 Release Work > ---------------- > > Key: TEIIDDES-1868 > URL: https://issues.jboss.org/browse/TEIIDDES-1868 > Project: Teiid Designer > Issue Type: Task > Components: Release Work > Affects Versions: 8.3 > Reporter: Barry LaFond > Assignee: Barry LaFond > Priority: Blocker > Fix For: 8.3 > > > General task for work related to version 8.3.0 -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1971) Connection Reset by Peer messages appearing in JBoss log

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1971?page=com.atlassian.jira.plu... ] Nick Boldt updated TEIIDDES-1971: --------------------------------- Labels: jbds711 jbdsis701 (was: ) > Connection Reset by Peer messages appearing in JBoss log > -------------------------------------------------------- > > Key: TEIIDDES-1971 > URL: https://issues.jboss.org/browse/TEIIDDES-1971 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 8.3 > Reporter: Steven Hawkins > Assignee: Paul Richardson > Priority: Critical > Labels: jbds711, jbdsis701 > Fix For: 8.3.x > > Attachments: retransmission-packet.png, server.log > > > Running Developer Studio 7.1.0.CR1 and using either the server auto-detection or manually defining a server -and using an incorrect management password- results in a console log entry: > 14:00:54,966 ERROR [org.jboss.remoting.remote.connection] (Remoting "..." read-1) JBREM000200: Remote connection failed: java.io.IOException: Connection reset by peer > On server startup without any indication of what it means. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2012) Designer's UDFManager does not account for or track edits to an existing function

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2012?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2012: ----------------------------------- Fix Version/s: 8.3.x > Designer's UDFManager does not account for or track edits to an existing function > --------------------------------------------------------------------------------- > > Key: TEIIDDES-2012 > URL: https://issues.jboss.org/browse/TEIIDDES-2012 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 8.3 > Reporter: Barry LaFond > Fix For: 8.3.x > > > * Created a UDF for a view model. > * Verified it was added to the function library and available in the Function Builder wizard > * Edited the function and changed "category" and save the model > * Returned to a transformation, launched the Function Builder and category was not changed. > Workaround is to close and re-open the project -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2012) Designer's UDFManager does not account for or track edits to an existing function

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2012?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2012. ------------------------------------ Resolution: Done Added checks to allow virtual functions to be added to cached functions or updated/removed when view models change. Done > Designer's UDFManager does not account for or track edits to an existing function > --------------------------------------------------------------------------------- > > Key: TEIIDDES-2012 > URL: https://issues.jboss.org/browse/TEIIDDES-2012 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 8.3 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 8.3.x > > > * Created a UDF for a view model. > * Verified it was added to the function library and available in the Function Builder wizard > * Edited the function and changed "category" and save the model > * Returned to a transformation, launched the Function Builder and category was not changed. > Workaround is to close and re-open the project -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2012) Designer's UDFManager does not account for or track edits to an existing function

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2012?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-2012: -------------------------------------- Assignee: Barry LaFond > Designer's UDFManager does not account for or track edits to an existing function > --------------------------------------------------------------------------------- > > Key: TEIIDDES-2012 > URL: https://issues.jboss.org/browse/TEIIDDES-2012 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 8.3 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 8.3.x > > > * Created a UDF for a view model. > * Verified it was added to the function library and available in the Function Builder wizard > * Edited the function and changed "category" and save the model > * Returned to a transformation, launched the Function Builder and category was not changed. > Workaround is to close and re-open the project -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2012) Designer's UDFManager does not account for or track edits to an existing function

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-2012: -------------------------------------- Summary: Designer's UDFManager does not account for or track edits to an existing function Key: TEIIDDES-2012 URL: https://issues.jboss.org/browse/TEIIDDES-2012 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 8.3 Reporter: Barry LaFond * Created a UDF for a view model. * Verified it was added to the function library and available in the Function Builder wizard * Edited the function and changed "category" and save the model * Returned to a transformation, launched the Function Builder and category was not changed. Workaround is to close and re-open the project -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2011) Designer connectivity feature needs include org.apache.commons.logging for Modeshape connection profile

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2011?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2011. ------------------------------------ Resolution: Rejected Issue was really with modeshape client jar and not Designer. > Designer connectivity feature needs include org.apache.commons.logging for Modeshape connection profile > ------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2011 > URL: https://issues.jboss.org/browse/TEIIDDES-2011 > Project: Teiid Designer > Issue Type: Bug > Components: Datatools Integration > Affects Versions: 8.3 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 8.3.x > > Attachments: modeshape-client-3.3.6.GA-redhat-3.jar, modeshape-roles.properties, modeshape-users.properties, module.xml > > > Designer connectivity feature needs include org.apache.commons.logging for Modeshape connection profile. > Results in java.lang.ClassNotFoundException: org.apache.commons.logging.LogFactory trying to connect to MS repo via JDBC. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1917) Can't delete source model which imports VDB

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1917?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1917: --------------------------------------------------- Filip Elias <felias(a)redhat.com> changed the Status of [bug 1026728|https://bugzilla.redhat.com/show_bug.cgi?id=1026728] from ON_QA to VERIFIED > Can't delete source model which imports VDB > ------------------------------------------- > > Key: TEIIDDES-1917 > URL: https://issues.jboss.org/browse/TEIIDDES-1917 > Project: Teiid Designer > Issue Type: Bug > Components: Dialogs > Affects Versions: 8.3 > Reporter: Van Halbert > Assignee: Paul Richardson > Priority: Critical > Fix For: 8.3 > > > Source model that imports VDB can't be deleted. > Environment JBDS 7.0.0 GA > Tooling 4.1.3.Beta5 (http://download.jboss.org/jbosstools/updates/integration/kepler/integrati...) > Steps to reproduce: > 1. Select File -> Import -> JDBC Database >> Source Model > 2. Create connection profile for VDB (Select Teiid as Connection profile type) > 3. Make sure that Import as VDB source model is checked > 4. Create the source Model > 5. Right-click on the source model and try to delete it, but Delete is inactive -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1918) JDBC importer adds wrong column type for columns of type integer, when importing(Reusing) VDB

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1918?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1918: --------------------------------------------------- Filip Elias <felias(a)redhat.com> changed the Status of [bug 1026892|https://bugzilla.redhat.com/show_bug.cgi?id=1026892] from ON_QA to VERIFIED > JDBC importer adds wrong column type for columns of type integer, when importing(Reusing) VDB > ---------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1918 > URL: https://issues.jboss.org/browse/TEIIDDES-1918 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.3 > Reporter: Van Halbert > Assignee: Mark Drilling > Priority: Critical > Fix For: 8.3 > > > When a VDB is imported(reused) by another VDB and the imported VDB contains table with column of type integer, then the importing VDB will throw validation error. > Steps to reproduce: > 1. Create loopback VDB, add table DATA with two columns, one of type integer and one of the string > 2. Deploy the loopback VDB > 3. Reuse the looback VDB > 3.1. Import the loopback VDB through JDBC importer > "Import as VDB source model" have to be checked > 3.2 Create view model, use table DATA in the view model > 3.3 Create and deploy new VDB > When deploying the VDB, error occures: > TEIID31080 View data validation error: QueryValidatorException-The definition for data has the wrong type for column 1. Expected bigdecimal, but was biginteger. > 15:57:48,718 INFO [org.teiid.RUNTIME] (teiid-async-threads - 1) TEIID40073 The metadata for the VDB aaa.1 is loaded, however it is not valid. Check models for errors. Correct the metadata and re-deploy. > 15:57:48,719 INFO [org.teiid.RUNTIME] (teiid-async-threads - 1) TEIID40003 VDB aaa.1 is set to FAILED -- 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, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues January 2014