December 2014 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2406) Provide option to set JNDI, instead of Connection Profile, in order to do data preview

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2406?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-2406: ---------------------------------------- This is much more like what we have discussed prior in terms of connection profile or data source re-factoring in general in Designer. I know there is JIRA for that. > Provide option to set JNDI, instead of Connection Profile, in order to do data preview > -------------------------------------------------------------------------------------- > > Key: TEIIDDES-2406 > URL: https://issues.jboss.org/browse/TEIIDDES-2406 > Project: Teiid Designer > Issue Type: Feature Request > Components: Data Preview > Affects Versions: 8.6 > Reporter: Van Halbert > > In a collaborative environment, the data sources could already be setup on the server. So in Designer, when doing data preview, it would user friendly to be able to set the JNDI reference to use, instead of having to create a connection profile. And that would eliminate the need to create a new data source in order to preview. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2406) Provide option to set JNDI, instead of Connection Profile, in order to do data preview

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2406?page=com.atlassian.jira.plu... ] Van Halbert updated TEIIDDES-2406: ---------------------------------- Description: In a collaborative environment, the data sources could already be setup on the server. So in Designer, when doing data preview, it would user friendly to be able to set the JNDI reference to use, instead of having to create a connection profile. And that would eliminate the need to create a new data source in order to preview. (was: In a collaborative environment, the data sources could already be setup on the server. So in Designer, when doing data preview, it would user friendly to be able to set the JNDI reference to use, instead of having to create a connection profile.) > Provide option to set JNDI, instead of Connection Profile, in order to do data preview > -------------------------------------------------------------------------------------- > > Key: TEIIDDES-2406 > URL: https://issues.jboss.org/browse/TEIIDDES-2406 > Project: Teiid Designer > Issue Type: Feature Request > Components: Data Preview > Affects Versions: 8.6 > Reporter: Van Halbert > > In a collaborative environment, the data sources could already be setup on the server. So in Designer, when doing data preview, it would user friendly to be able to set the JNDI reference to use, instead of having to create a connection profile. And that would eliminate the need to create a new data source in order to preview. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2406) Provide option to set JNDI, instead of Connection Profile, in order to do data preview

by Van Halbert (JIRA)

Van Halbert created TEIIDDES-2406: ------------------------------------- Summary: Provide option to set JNDI, instead of Connection Profile, in order to do data preview Key: TEIIDDES-2406 URL: https://issues.jboss.org/browse/TEIIDDES-2406 Project: Teiid Designer Issue Type: Feature Request Components: Data Preview Affects Versions: 8.6 Reporter: Van Halbert In a collaborative environment, the data sources could already be setup on the server. So in Designer, when doing data preview, it would user friendly to be able to set the JNDI reference to use, instead of having to create a connection profile. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2349) Changes to project imported from zip cached even after deleting and reimporting

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2349?page=com.atlassian.jira.plu... ] Barry LaFond edited comment on TEIIDDES-2349 at 12/9/14 2:19 PM: ----------------------------------------------------------------- With the new steps, I am able to reproduce, so hopefully I can debug/fix this. Appears the act of closing a project, with the model open in an editor and deleting the project doesn't result in the workspace ContainerImpl (ResourceSet) removing the resources of that project. So after re-importing original project, the ContainerImpl.getOrCreateResource() method actually finds an existing resource in the container given the file URI (in my case it's: file:/home/blafond/Runtime-Workspaces/8_3_0_X/ImportProject/V1.xmi) Need to discover how/why the resource set isn't getting cleaned up. was (Author: blafond): With the new steps, I am able to reproduce, so hopefully I can debug/fix this. > Changes to project imported from zip cached even after deleting and reimporting > ------------------------------------------------------------------------------- > > Key: TEIIDDES-2349 > URL: https://issues.jboss.org/browse/TEIIDDES-2349 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 8.3.4, 8.6.1, 9.0.1 > Environment: JBDS 8.0.0.CR1 > Teiid Designer 8.6.1.Alpha1 > Windows, Linux > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Fix For: 9.0, 8.6.1, 9.0.1 > > Attachments: ImportProject.zip > > > Changes made to a project imported into the workspace from zip seem to persist even after deleting the project (including contents on disk) and importing it again. > Closing and reopening the project after the second import or restarting JBDS solves the issue on Windows, on Linux only restarting JBDS helps. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2405) Teiid Importer *MUST* not require class-name property working with Teiid Sources

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2405?page=com.atlassian.jira.plu... ] Ramesh Reddy updated TEIIDDES-2405: ----------------------------------- Forum Reference: https://developer.jboss.org/message/912894, https://developer.jboss.org/thread/249176 > Teiid Importer *MUST* not require class-name property working with Teiid Sources > -------------------------------------------------------------------------------- > > Key: TEIIDDES-2405 > URL: https://issues.jboss.org/browse/TEIIDDES-2405 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.6 > Reporter: Ramesh Reddy > Priority: Critical > > When working with "new" and "custom" translators in Teiid, the Teiid Importer fails to recognize the class-name property from the retrieved metadata. The following the excerpt from CLI command on a cassandra data source > {code} > {"managedconnectionfactory-class" => { > "type" => STRING, > "display" => "managedconnectionfactory-class", > "read-only" => "true", > "advanced" => "true", > "default" => "org.teiid.resource.adapter.cassandra.CassandraManagedConnectionFactory" > }}, > {code} > That property needs to be used as the "class-name", there must not be any hard coding of this to only known source types. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2405) Teiid Importer *MUST* not require class-name property working with Teiid Sources

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIIDDES-2405: -------------------------------------- Summary: Teiid Importer *MUST* not require class-name property working with Teiid Sources Key: TEIIDDES-2405 URL: https://issues.jboss.org/browse/TEIIDDES-2405 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 8.6 Reporter: Ramesh Reddy Priority: Critical When working with "new" and "custom" translators in Teiid, the Teiid Importer fails to recognize the class-name property from the retrieved metadata. The following the excerpt from CLI command on a cassandra data source {code} {"managedconnectionfactory-class" => { "type" => STRING, "display" => "managedconnectionfactory-class", "read-only" => "true", "advanced" => "true", "default" => "org.teiid.resource.adapter.cassandra.CassandraManagedConnectionFactory" }}, {code} That property needs to be used as the "class-name", there must not be any hard coding of this to only known source types. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2349) Changes to project imported from zip cached even after deleting and reimporting

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2349?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2349: ----------------------------------- Fix Version/s: 9.0 8.6.1 9.0.1 > Changes to project imported from zip cached even after deleting and reimporting > ------------------------------------------------------------------------------- > > Key: TEIIDDES-2349 > URL: https://issues.jboss.org/browse/TEIIDDES-2349 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 8.3.4, 8.6.1, 9.0.1 > Environment: JBDS 8.0.0.CR1 > Teiid Designer 8.6.1.Alpha1 > Windows, Linux > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Fix For: 9.0, 8.6.1, 9.0.1 > > Attachments: ImportProject.zip > > > Changes made to a project imported into the workspace from zip seem to persist even after deleting the project (including contents on disk) and importing it again. > Closing and reopening the project after the second import or restarting JBDS solves the issue on Windows, on Linux only restarting JBDS helps. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2349) Changes to project imported from zip cached even after deleting and reimporting

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2349?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2349: ---------------------------------------- With the new steps, I am able to reproduce, so hopefully I can debug/fix this. > Changes to project imported from zip cached even after deleting and reimporting > ------------------------------------------------------------------------------- > > Key: TEIIDDES-2349 > URL: https://issues.jboss.org/browse/TEIIDDES-2349 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 8.3.4, 8.6.1, 9.0.1 > Environment: JBDS 8.0.0.CR1 > Teiid Designer 8.6.1.Alpha1 > Windows, Linux > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Attachments: ImportProject.zip > > > Changes made to a project imported into the workspace from zip seem to persist even after deleting the project (including contents on disk) and importing it again. > Closing and reopening the project after the second import or restarting JBDS solves the issue on Windows, on Linux only restarting JBDS helps. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2383) Transformation editor removes cache hint in SQL

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2383?page=com.atlassian.jira.plu... ] Van Halbert commented on TEIIDDES-2383: --------------------------------------- This is definitely a hole for the users and their inability to tune their queries. > Transformation editor removes cache hint in SQL > ----------------------------------------------- > > Key: TEIIDDES-2383 > URL: https://issues.jboss.org/browse/TEIIDDES-2383 > Project: Teiid Designer > Issue Type: Bug > Components: Transformations > Affects Versions: 8.6, 9.0 > Reporter: Jan Stastny > Fix For: 9.1 > > > When adding a comment in transformation editor, the comment disappears after saving its content. It happens with any comment. This disables usage of cache hints. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2349) Changes to project imported from zip cached even after deleting and reimporting

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2349?page=com.atlassian.jira.plu... ] Andrej Podhradsky updated TEIIDDES-2349: ---------------------------------------- Steps to Reproduce: # Import the attached project # Change the transformation in the view model to e.g. {code:sql}SELECT 'c1' AS c1{code} # Save the model # Close the project without closing the model # Delete the project (check Delete contents on disk) # Import the project again, open the transformation, notice the changed SQL. # Close and reopen the project, the transformation now contains the original SQL was: # Import the attached project # Change the transformation in the view model to e.g. {code:sql}SELECT 'c1' AS c1{code} # Save the model # Close the project and delete it (check Delete contents on disk) # Import the project again, open the transformation, notice the changed SQL. # Close and reopen the project, the transformation now contains the original SQL > Changes to project imported from zip cached even after deleting and reimporting > ------------------------------------------------------------------------------- > > Key: TEIIDDES-2349 > URL: https://issues.jboss.org/browse/TEIIDDES-2349 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 8.3.4, 8.6.1, 9.0.1 > Environment: JBDS 8.0.0.CR1 > Teiid Designer 8.6.1.Alpha1 > Windows, Linux > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Attachments: ImportProject.zip > > > Changes made to a project imported into the workspace from zip seem to persist even after deleting the project (including contents on disk) and importing it again. > Closing and reopening the project after the second import or restarting JBDS solves the issue on Windows, on Linux only restarting JBDS helps. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

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 2014