December 2018 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2699) Issues with Dynamic VDB import/export

by Matej Kralik (Jira)

[ https://issues.jboss.org/browse/TEIIDDES-2699?page=com.atlassian.jira.plu... ] Matej Kralik updated TEIIDDES-2699: ----------------------------------- Labels: release_notes (was: ) > Issues with Dynamic VDB import/export > ------------------------------------- > > Key: TEIIDDES-2699 > URL: https://issues.jboss.org/browse/TEIIDDES-2699 > Project: Teiid Designer > Issue Type: Task > Components: Patch Release, VDB & Execution > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Priority: Blocker > Labels: release_notes > Fix For: 11.2.1 > > > Tracking jira for all issues with dynamic VDB import and export -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2963) Add Multi-selection capabilities on the directory tree

by Matej Kralik (Jira)

[ https://issues.jboss.org/browse/TEIIDDES-2963?page=com.atlassian.jira.plu... ] Matej Kralik updated TEIIDDES-2963: ----------------------------------- Labels: release_notes (was: ) > Add Multi-selection capabilities on the directory tree > ------------------------------------------------------ > > Key: TEIIDDES-2963 > URL: https://issues.jboss.org/browse/TEIIDDES-2963 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Reporter: Debbie Steigner > Assignee: Barry LaFond > Priority: Minor > Labels: release_notes > Fix For: 11.2.1 > > > When importing tables with a lot of columns, if the user wants to remove a bunch of columns, he needs to select them individually. > Can the Designer have Multi-Selection capabilities, i.e. Shift or Control keys -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2963) Add Multi-selection capabilities on the directory tree

by Matej Kralik (Jira)

[ https://issues.jboss.org/browse/TEIIDDES-2963?page=com.atlassian.jira.plu... ] Matej Kralik closed TEIIDDES-2963. ---------------------------------- > Add Multi-selection capabilities on the directory tree > ------------------------------------------------------ > > Key: TEIIDDES-2963 > URL: https://issues.jboss.org/browse/TEIIDDES-2963 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Reporter: Debbie Steigner > Assignee: Barry LaFond > Priority: Minor > Labels: release_notes > Fix For: 11.2.1 > > > When importing tables with a lot of columns, if the user wants to remove a bunch of columns, he needs to select them individually. > Can the Designer have Multi-Selection capabilities, i.e. Shift or Control keys -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2895) No warning after deleting schema and UDF Jars

by Mario Majernik (Jira)

[ https://issues.jboss.org/browse/TEIIDDES-2895?page=com.atlassian.jira.plu... ] Mario Majernik updated TEIIDDES-2895: ------------------------------------- Labels: release_notes (was: ) > No warning after deleting schema and UDF Jars > --------------------------------------------- > > Key: TEIIDDES-2895 > URL: https://issues.jboss.org/browse/TEIIDDES-2895 > Project: Teiid Designer > Issue Type: Bug > Components: Editors > Affects Versions: 10.0.1 > Reporter: Mario Majernik > Assignee: Barry LaFond > Priority: Major > Labels: release_notes > Fix For: 11.2.1 > > Attachments: ScreenShot1.png, XmlStagingTableProject.zip > > > There is no warning after deleting schema which is used by models. VDB is deployed without warnings. Following query fails on missing schema. > Should be there some warning that schema was deleted and VDB should not be deploy on server without schema. > EDIT: The same thing with UDF Jars. No warning after deleting but VDB is corrupt after deploying on server. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2895) No warning after deleting schema and UDF Jars

by Mario Majernik (Jira)

[ https://issues.jboss.org/browse/TEIIDDES-2895?page=com.atlassian.jira.plu... ] Mario Majernik closed TEIIDDES-2895. ------------------------------------ > No warning after deleting schema and UDF Jars > --------------------------------------------- > > Key: TEIIDDES-2895 > URL: https://issues.jboss.org/browse/TEIIDDES-2895 > Project: Teiid Designer > Issue Type: Bug > Components: Editors > Affects Versions: 10.0.1 > Reporter: Mario Majernik > Assignee: Barry LaFond > Priority: Major > Labels: release_notes > Fix For: 11.2.1 > > Attachments: ScreenShot1.png, XmlStagingTableProject.zip > > > There is no warning after deleting schema which is used by models. VDB is deployed without warnings. Following query fails on missing schema. > Should be there some warning that schema was deleted and VDB should not be deploy on server without schema. > EDIT: The same thing with UDF Jars. No warning after deleting but VDB is corrupt after deploying on server. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3087) There isn't a way to set the Connection type on a VDB in the Designer

by Matej Kralik (Jira)

[ https://issues.jboss.org/browse/TEIIDDES-3087?page=com.atlassian.jira.plu... ] Matej Kralik reopened TEIIDDES-3087: ------------------------------------ > There isn't a way to set the Connection type on a VDB in the Designer > --------------------------------------------------------------------- > > Key: TEIIDDES-3087 > URL: https://issues.jboss.org/browse/TEIIDDES-3087 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 11.0.1 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Priority: Major > Fix For: 11.1.2, 11.2.1 > > Attachments: connectionTypeNone.mkv > > > Because of https://issues.jboss.org/browse/TEIID-4957 a customer would need to be able to set the Connection Type on a VDB in the Designer before deploying it. There currently is not a way to do that. You cannot use the User Properties because it writes to the vdb.xml as <property name="connection-type" value="NONE"/> and it needs to be <connection-type>NONE</connection-type> -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3087) There isn't a way to set the Connection type on a VDB in the Designer

by Matej Kralik (Jira)

[ https://issues.jboss.org/browse/TEIIDDES-3087?page=com.atlassian.jira.plu... ] Matej Kralik resolved TEIIDDES-3087. ------------------------------------ Resolution: Done > There isn't a way to set the Connection type on a VDB in the Designer > --------------------------------------------------------------------- > > Key: TEIIDDES-3087 > URL: https://issues.jboss.org/browse/TEIIDDES-3087 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 11.0.1 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Priority: Major > Fix For: 11.2.1, 11.1.2 > > Attachments: connectionTypeNone.mkv > > > Because of https://issues.jboss.org/browse/TEIID-4957 a customer would need to be able to set the Connection Type on a VDB in the Designer before deploying it. There currently is not a way to do that. You cannot use the User Properties because it writes to the vdb.xml as <property name="connection-type" value="NONE"/> and it needs to be <connection-type>NONE</connection-type> -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3087) There isn't a way to set the Connection type on a VDB in the Designer

by Matej Kralik (Jira)

[ https://issues.jboss.org/browse/TEIIDDES-3087?page=com.atlassian.jira.plu... ] Matej Kralik commented on TEIIDDES-3087: ---------------------------------------- It is working now but in my point of view, the default value should be BY_VERSION as it is described in the teiid [documentation|https://teiid.gitbooks.io/documents/content/admin/VDB_Versioning.html]. Because NONE value will cause that new connection are disallowed. So the user cannot notice that default value is NONE and can be surprised when they are not able to connect to the deployed VDB. For backward-compatibility, Before the fix, the VDB behavior without the connection type was same as with BY_VERSION type. For us, it is also the test blocker because lots of tests create VDB (doesn't change connection type), deploy it and want to connect to it. After connection, the tests failed at "Connection is null". We should update majority parts of tests. I was created simple fix for it: https://github.com/Teiid-Designer/teiid-designer/pull/590 [~blafond] Please, look at that pull request. Thx > There isn't a way to set the Connection type on a VDB in the Designer > --------------------------------------------------------------------- > > Key: TEIIDDES-3087 > URL: https://issues.jboss.org/browse/TEIIDDES-3087 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 11.0.1 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Priority: Major > Fix For: 11.1.2, 11.2.1 > > Attachments: connectionTypeNone.mkv > > > Because of https://issues.jboss.org/browse/TEIID-4957 a customer would need to be able to set the Connection Type on a VDB in the Designer before deploying it. There currently is not a way to do that. You cannot use the User Properties because it writes to the vdb.xml as <property name="connection-type" value="NONE"/> and it needs to be <connection-type>NONE</connection-type> -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2954) Dynamic VDB doesn't contains apostrophe around procedure

by Matej Kralik (Jira)

[ https://issues.jboss.org/browse/TEIIDDES-2954?page=com.atlassian.jira.plu... ] Matej Kralik closed TEIIDDES-2954. ---------------------------------- > Dynamic VDB doesn't contains apostrophe around procedure > -------------------------------------------------------- > > Key: TEIIDDES-2954 > URL: https://issues.jboss.org/browse/TEIIDDES-2954 > Project: Teiid Designer > Issue Type: Bug > Components: Dynamic VDBs > Affects Versions: 10.0.2 > Environment: Fedora 24 > Reporter: Matej Kralik > Priority: Major > Attachments: completeJDGproject2.zip > > > I have a project with JDG materialization. I have set > After load script to: execute BookCacheSource.native('swap cache names'); > and > Before load script to: execute BookCacheSource.native('truncate cache'); > When I generated Dynamic VDB and I want to deploy it, server shows me error that: > {code:java} > org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered ", \"teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT\" 'execute BookCacheSource.native('[*]swap[*] cache names" at line 10, column 188. > Was expecting: "," | ")" > {code} > When I added another apostrophe to procedures in the DDL, > execute BookCacheSource.native(''truncate cache''); > execute BookCacheSource.native(''swap cache names''); > deploy was successful. > I think that DDL parser should add it automatically. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3052) No default server defined

by Matej Kralik (Jira)

[ https://issues.jboss.org/browse/TEIIDDES-3052?page=com.atlassian.jira.plu... ] Matej Kralik closed TEIIDDES-3052. ---------------------------------- > No default server defined > ------------------------- > > Key: TEIIDDES-3052 > URL: https://issues.jboss.org/browse/TEIIDDES-3052 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 9.1, 10.1 > Environment: Windows 7, 64-bit > JBoss Developer Studio 10.2.0.GA > JBoss Data Virt Development (Teiid Designer) Integration Stack 10.1.0.GA > > Reporter: Steve Tran > Assignee: Barry LaFond > Priority: Minor > Fix For: 11.2.1 > > Attachments: Screenshot from 2017-03-02 10-11-09.png, Screenshot from 2017-03-02 10-11-25.png > > > After starting the server, the "Default Server" is not automatically refreshed. This will cause an issue when attempting to deploy a VDB because the context menu won't have the deploy option. The workaround is to refresh the servers tab, which will reconnect the default server. Nothing major, but sometimes the default server gets automatically refreshed, and most times it doesn't. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues December 2018