January 2018 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-3174) Infinispan-hotrod MXD is not set after JDG materialization wizard

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3174?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-3174. ------------------------------------ Resolution: Done master: https://github.com/Teiid-Designer/teiid-designer/commit/14b1b7d9f2cbc9f9d... > Infinispan-hotrod MXD is not set after JDG materialization wizard > ----------------------------------------------------------------- > > Key: TEIIDDES-3174 > URL: https://issues.jboss.org/browse/TEIIDDES-3174 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 11.1.1 > Reporter: Matej Kralik > Assignee: Barry LaFond > Priority: Critical > Fix For: 11.1.2 > > > When I went through JDG7 materialization creation I noticed that MED for JDG7 source model is not set automatically. So I don't see Primary cache name and staging cache name which I set in the 'Generate Materialized JDG Module' wizard. > I must set MED for this model manually (Modeling -> Manage Model Extension Definition -> Add -> infinispan-hotrod). > After that, I see infinispan-hotrod:CACHE which I defined in the wizard. > Typ of infinispan-hotrod is *imported* so I must have set up a server *before*. > In my point of view, the designer should set MED for JDG7 source model automatically. > My idea: after finish wizard, the designer set infinispan-hotrod MED for this model. If infinispan-hotrod MED is not imported yet, the designer should show an error dialog that server is not defined yet and MED is not available. > When I generate source model for JDG6.6, MED is set correctly (because MED is built-in). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3174) Infinispan-hotrod MXD is not set after JDG materialization wizard

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3174?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-3174: -------------------------------------- Assignee: Barry LaFond > Infinispan-hotrod MXD is not set after JDG materialization wizard > ----------------------------------------------------------------- > > Key: TEIIDDES-3174 > URL: https://issues.jboss.org/browse/TEIIDDES-3174 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 11.1.1 > Reporter: Matej Kralik > Assignee: Barry LaFond > Priority: Critical > Fix For: 11.1.2 > > > When I went through JDG7 materialization creation I noticed that MED for JDG7 source model is not set automatically. So I don't see Primary cache name and staging cache name which I set in the 'Generate Materialized JDG Module' wizard. > I must set MED for this model manually (Modeling -> Manage Model Extension Definition -> Add -> infinispan-hotrod). > After that, I see infinispan-hotrod:CACHE which I defined in the wizard. > Typ of infinispan-hotrod is *imported* so I must have set up a server *before*. > In my point of view, the designer should set MED for JDG7 source model automatically. > My idea: after finish wizard, the designer set infinispan-hotrod MED for this model. If infinispan-hotrod MED is not imported yet, the designer should show an error dialog that server is not defined yet and MED is not available. > When I generate source model for JDG6.6, MED is set correctly (because MED is built-in). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3174) Infinispan-hotrod MXD is not set after JDG materialization wizard

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3174?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-3174: ----------------------------------- Fix Version/s: 11.1.2 > Infinispan-hotrod MXD is not set after JDG materialization wizard > ----------------------------------------------------------------- > > Key: TEIIDDES-3174 > URL: https://issues.jboss.org/browse/TEIIDDES-3174 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 11.1.1 > Reporter: Matej Kralik > Assignee: Barry LaFond > Priority: Critical > Fix For: 11.1.2 > > > When I went through JDG7 materialization creation I noticed that MED for JDG7 source model is not set automatically. So I don't see Primary cache name and staging cache name which I set in the 'Generate Materialized JDG Module' wizard. > I must set MED for this model manually (Modeling -> Manage Model Extension Definition -> Add -> infinispan-hotrod). > After that, I see infinispan-hotrod:CACHE which I defined in the wizard. > Typ of infinispan-hotrod is *imported* so I must have set up a server *before*. > In my point of view, the designer should set MED for JDG7 source model automatically. > My idea: after finish wizard, the designer set infinispan-hotrod MED for this model. If infinispan-hotrod MED is not imported yet, the designer should show an error dialog that server is not defined yet and MED is not available. > When I generate source model for JDG6.6, MED is set correctly (because MED is built-in). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3076) executed vdbs and query previews completely freeze designer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3076?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-3076. ------------------------------------ Assignee: Barry LaFond Resolution: Done > executed vdbs and query previews completely freeze designer > ----------------------------------------------------------- > > Key: TEIIDDES-3076 > URL: https://issues.jboss.org/browse/TEIIDDES-3076 > Project: Teiid Designer > Issue Type: Bug > Components: Data Preview > Affects Versions: 11.0.1 > Environment: JBoss Developer Studio 10.3.0, Linux > Reporter: Michael Echevarria > Assignee: Barry LaFond > Priority: Blocker > Fix For: 11.1.2 > > Attachments: Screenshot from 2017-05-02 16-12-41.png, jdv-api.zip > > > Previewing or querying within JBDS 10 against combinations of file based sources hangs the designer -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3025) Failed to determine if server supports teiid on Fuse on EAP 6.3

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3025?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-3025. ------------------------------------ Resolution: Done > Failed to determine if server supports teiid on Fuse on EAP 6.3 > --------------------------------------------------------------- > > Key: TEIIDDES-3025 > URL: https://issues.jboss.org/browse/TEIIDDES-3025 > Project: Teiid Designer > Issue Type: Task > Affects Versions: 11.0.1 > Environment: Devstudio 10.2.0.GA > Teiid Designer 11.0.1.Final-v20170125-1702-B4135 > fuse-eap-6.3.0.R1 > Reporter: Andrej Podhradsky > Assignee: Barry LaFond > Fix For: 11.1.2, 11.1 > > Attachments: erroLog.txt, errorLog2.txt > > > Failed to determine if server supports teiid on Fuse on EAP 6.3. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3150) Teiid Connection Importer - Provide a way to refresh the existing "datasources"

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3150?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-3150. ------------------------------------ Resolution: Done > Teiid Connection Importer - Provide a way to refresh the existing "datasources" > -------------------------------------------------------------------------------- > > Key: TEIIDDES-3150 > URL: https://issues.jboss.org/browse/TEIIDDES-3150 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Affects Versions: 11.1 > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Fix For: 11.1.2 > > > Currently, there is no way to refresh the available data sources in the Teiid Connection Importer unless the user goes to Servers tab, and disconnects and reconnects. There needs to a way refresh or just latest data sources when this wizard is invoked. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3150) Teiid Connection Importer - Provide a way to refresh the existing "datasources"

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3150?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-3150: ---------------------------------------- master: https://github.com/Teiid-Designer/teiid-designer/commit/d1f9f0ab954ab76ac... added refresh button do importer > Teiid Connection Importer - Provide a way to refresh the existing "datasources" > -------------------------------------------------------------------------------- > > Key: TEIIDDES-3150 > URL: https://issues.jboss.org/browse/TEIIDDES-3150 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Affects Versions: 11.1 > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Fix For: 11.1.2 > > > Currently, there is no way to refresh the available data sources in the Teiid Connection Importer unless the user goes to Servers tab, and disconnects and reconnects. There needs to a way refresh or just latest data sources when this wizard is invoked. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3174) Infinispan-hotrod MXD is not set after JDG materialization wizard

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3174?page=com.atlassian.jira.plu... ] Matej Kralik updated TEIIDDES-3174: ----------------------------------- Description: When I went through JDG7 materialization creation I noticed that MED for JDG7 source model is not set automatically. So I don't see Primary cache name and staging cache name which I set in the 'Generate Materialized JDG Module' wizard. I must set MED for this model manually (Modeling -> Manage Model Extension Definition -> Add -> infinispan-hotrod). After that, I see infinispan-hotrod:CACHE which I defined in the wizard. Typ of infinispan-hotrod is *imported* so I must have set up a server *before*. In my point of view, the designer should set MED for JDG7 source model automatically. My idea: after finish wizard, the designer set infinispan-hotrod MED for this model. If infinispan-hotrod MED is not imported yet, the designer should show an error dialog that server is not defined yet and MED is not available. When I generate source model for JDG6.6, MED is set correctly (because MED is built-in). was: When I went through JDG7 materialization creation I noticed that MED for JDG7 source model is not set automatically. So I don't see Primary cache name and staging cache name which I set in the 'Generate Materialized JDG Module' wizard. I must set MED for this model manually (Modeling -> Manage Model Extension Definition -> Add -> infinispan-hotrod). After that, I see infinispan-hotrod:CACHE which I defined in the wizard. Typ of infinispan-hotrod is *imported* so I must have set up a server *before*. In my points of view, the designer should set MED for JDG7 source model automatically. My idea: after finish wizard, the designer set infinispan-hotrod MED for this model. If infinispan-hotrod MED is not imported yet, the designer should show an error dialog that server is not defined yet and MED is not available. When I generate source model for JDG6.6, MED is set correctly (because MED is built-in). > Infinispan-hotrod MXD is not set after JDG materialization wizard > ----------------------------------------------------------------- > > Key: TEIIDDES-3174 > URL: https://issues.jboss.org/browse/TEIIDDES-3174 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 11.1.1 > Reporter: Matej Kralik > Priority: Critical > > When I went through JDG7 materialization creation I noticed that MED for JDG7 source model is not set automatically. So I don't see Primary cache name and staging cache name which I set in the 'Generate Materialized JDG Module' wizard. > I must set MED for this model manually (Modeling -> Manage Model Extension Definition -> Add -> infinispan-hotrod). > After that, I see infinispan-hotrod:CACHE which I defined in the wizard. > Typ of infinispan-hotrod is *imported* so I must have set up a server *before*. > In my point of view, the designer should set MED for JDG7 source model automatically. > My idea: after finish wizard, the designer set infinispan-hotrod MED for this model. If infinispan-hotrod MED is not imported yet, the designer should show an error dialog that server is not defined yet and MED is not available. > When I generate source model for JDG6.6, MED is set correctly (because MED is built-in). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3174) Infinispan-hotrod MXD is not set after JDG materialization wizard

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3174?page=com.atlassian.jira.plu... ] Matej Kralik updated TEIIDDES-3174: ----------------------------------- Workaround Description: # Set up and run server if you don't have any server (infinispan-hotrod MED will be imported) # Left-click on generated JDG source model and select Modeling -> Manage Model Extension Definition # Click to Add... and select infinispan-hotrod # click to ok and finish button (now, model has set extension and property infinispan-hotrod:CACHE is set) was: # Set up and run server if you don't have any server (infinispan-hotrod MXD will be imported) # Left-click on generated JDG source model and select Modeling -> Manage Model Extension Definition # Click to Add... and select infinispan-hotrod # click to ok and finish button (now, model has set extension and property infinispan-hotrod:CACHE is set) > Infinispan-hotrod MXD is not set after JDG materialization wizard > ----------------------------------------------------------------- > > Key: TEIIDDES-3174 > URL: https://issues.jboss.org/browse/TEIIDDES-3174 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 11.1.1 > Reporter: Matej Kralik > Priority: Critical > > When I went through JDG7 materialization creation I noticed that MED for JDG7 source model is not set automatically. So I don't see Primary cache name and staging cache name which I set in the 'Generate Materialized JDG Module' wizard. > I must set MED for this model manually (Modeling -> Manage Model Extension Definition -> Add -> infinispan-hotrod). > After that, I see infinispan-hotrod:CACHE which I defined in the wizard. > Typ of infinispan-hotrod is *imported* so I must have set up a server *before*. > In my points of view, the designer should set MED for JDG7 source model automatically. > My idea: after finish wizard, the designer set infinispan-hotrod MED for this model. If infinispan-hotrod MED is not imported yet, the designer should show an error dialog that server is not defined yet and MED is not available. > When I generate source model for JDG6.6, MED is set correctly (because MED is built-in). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3174) Infinispan-hotrod MXD is not set after JDG materialization wizard

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3174?page=com.atlassian.jira.plu... ] Matej Kralik updated TEIIDDES-3174: ----------------------------------- Description: When I went through JDG7 materialization creation I noticed that MED for JDG7 source model is not set automatically. So I don't see Primary cache name and staging cache name which I set in the 'Generate Materialized JDG Module' wizard. I must set MED for this model manually (Modeling -> Manage Model Extension Definition -> Add -> infinispan-hotrod). After that, I see infinispan-hotrod:CACHE which I defined in the wizard. Typ of infinispan-hotrod is *imported* so I must have set up a server *before*. In my points of view, the designer should set MED for JDG7 source model automatically. My idea: after finish wizard, the designer set infinispan-hotrod MED for this model. If infinispan-hotrod MED is not imported yet, the designer should show an error dialog that server is not defined yet and MED is not available. When I generate source model for JDG6.6, MED is set correctly (because MED is built-in). was: When I went through JDG7 materialization creation I noticed that MXD for JDG7 source model is not set automatically. So I don't see Primary cache name and staging cache name which I set in the 'Generate Materialized JDG Module' wizard. I must set MXD for this model manually (Modeling -> Manage Model Extension Definition -> Add -> infinispan-hotrod). After that, I see infinispan-hotrod:CACHE which I defined in the wizard. Typ of infinispan-hotrod is *imported* so I must have set up a server *before*. In my points of view, the designer should set MXD for JDG7 source model automatically. So after finish wizard, the designer set infinispan-hotrod MXD for this model. If infinispan-hotrod MXD is not imported yet, designer shows a error dialog. When I generate source model for JDG6.6, MXD is set correctly (because MXD is built-in). > Infinispan-hotrod MXD is not set after JDG materialization wizard > ----------------------------------------------------------------- > > Key: TEIIDDES-3174 > URL: https://issues.jboss.org/browse/TEIIDDES-3174 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 11.1.1 > Reporter: Matej Kralik > Priority: Critical > > When I went through JDG7 materialization creation I noticed that MED for JDG7 source model is not set automatically. So I don't see Primary cache name and staging cache name which I set in the 'Generate Materialized JDG Module' wizard. > I must set MED for this model manually (Modeling -> Manage Model Extension Definition -> Add -> infinispan-hotrod). > After that, I see infinispan-hotrod:CACHE which I defined in the wizard. > Typ of infinispan-hotrod is *imported* so I must have set up a server *before*. > In my points of view, the designer should set MED for JDG7 source model automatically. > My idea: after finish wizard, the designer set infinispan-hotrod MED for this model. If infinispan-hotrod MED is not imported yet, the designer should show an error dialog that server is not defined yet and MED is not available. > When I generate source model for JDG6.6, MED is set correctly (because MED is built-in). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 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 2018