May 2014 - teiid-designer-issues - Jboss List Archives

[JBoss JIRA] (TEIIDDES-2180) Remove Eclipse Common Dependency in AnnotationUtils

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2180?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-2180: -------------------------------- Description: Need to remove the Eclipse common dependency in the AnnotationUtils class where assert() is used to check the version. Also, this will allow us to remove the Eclipse common jar form the generated REST war. (was: Need to remove the Eclipse common dependency in the TeiidServerVersion class where assert() is used to check the version. Also, this will allow us to remove the Eclipse common jar form the generated REST war.) > Remove Eclipse Common Dependency in AnnotationUtils > --------------------------------------------------- > > Key: TEIIDDES-2180 > URL: https://issues.jboss.org/browse/TEIIDDES-2180 > Project: Teiid Designer > Issue Type: Feature Request > Components: Housekeeping, Web Services Support > Affects Versions: 8.5 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 8.5 > > > Need to remove the Eclipse common dependency in the AnnotationUtils class where assert() is used to check the version. Also, this will allow us to remove the Eclipse common jar form the generated REST war. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2180) Remove Eclipse Common Dependency in AnnotationUtils

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2180?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-2180: -------------------------------- Summary: Remove Eclipse Common Dependency in AnnotationUtils (was: Remove Eclipse Common Dependency in TeiidServerVersion) > Remove Eclipse Common Dependency in AnnotationUtils > --------------------------------------------------- > > Key: TEIIDDES-2180 > URL: https://issues.jboss.org/browse/TEIIDDES-2180 > Project: Teiid Designer > Issue Type: Feature Request > Components: Housekeeping, Web Services Support > Affects Versions: 8.5 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 8.5 > > > Need to remove the Eclipse common dependency in the TeiidServerVersion class where assert() is used to check the version. Also, this will allow us to remove the Eclipse common jar form the generated REST war. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2109) Create a Connections context menu group next to Modeling group

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2109?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2109: ----------------------------------- Fix Version/s: 8.6 (was: 8.5) > Create a Connections context menu group next to Modeling group > -------------------------------------------------------------- > > Key: TEIIDDES-2109 > URL: https://issues.jboss.org/browse/TEIIDDES-2109 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling, Views > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 8.6 > > Attachments: connection-action-menu.png > > > For source models, the Modeling action now contains a number of connection or translator related actions that really don't have anything to do with modeling. > * Create a *Connection* menu group and place below *Modeling* group > * Move the following actions to the *Connection* group > ** Create Data Source > ** Edit Translator Overrides > ** Remove Connection Info > ** Set Connection Profile > ** Set Translator Name > ** View Connection Profile Info > * Maybe group these into Translator/Profile actions with separators -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2178) Teiid Connection importer by default only waits for 120 seconds for schema

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2178?page=com.atlassian.jira.plu... ] Mark Drilling reopened TEIIDDES-2178: ------------------------------------- I will change the dialog message from - Loading did not complete within 120 sec for VDB: "importVDB" to "importVDB" did not load within xxx seconds. If desired, the timeout can be increased in the Teiid Designer preferences. > Teiid Connection importer by default only waits for 120 seconds for schema > -------------------------------------------------------------------------- > > Key: TEIIDDES-2178 > URL: https://issues.jboss.org/browse/TEIIDDES-2178 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Affects Versions: 8.4, 8.3.2 > Reporter: Ramesh Reddy > Assignee: Mark Drilling > > When using the Teiid connection importer it sends the query to the server and waits for up to 120 seconds for server to return metadata. If the server returned data it is fine, otherwise it fails. > Some times when working with larger metadata or slower connections it may take more than 120 seconds, the UI should give user an option to terminate or wait for another +n of seconds. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2181) Teiid Instance URL is displayed wrong

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2181?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-2181. ------------------------------------- Assignee: Mark Drilling Resolution: Duplicate Issue This has been addressed in Designer 8.5 with the linked JIRA. > Teiid Instance URL is displayed wrong > ------------------------------------- > > Key: TEIIDDES-2181 > URL: https://issues.jboss.org/browse/TEIIDDES-2181 > Project: Teiid Designer > Issue Type: Bug > Reporter: Ramesh Reddy > Assignee: Mark Drilling > Attachments: mmproto.png > > > !mmproto.png! > There is no protocol as "mm://" for making a admin connection. The admin connection as you know is managed totally by JBoss EAP. This label has caused confusion in terms of how Teiid uses the admin connection. This is how Teiid may have used 7.x series, but not in 8.x series. I believe I saw this one another place, may be on Teiid Connection Instance page. This needs to be corrected. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2178) Teiid Connection importer by default only waits for 120 seconds for schema

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2178?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-2178: ---------------------------------------- It is not evident for the user that is configurable, it is much easier to add confirmation from user before you send somebody on configuration hunt. I did not know, I certainty think a casual user will ever figure that out. > Teiid Connection importer by default only waits for 120 seconds for schema > -------------------------------------------------------------------------- > > Key: TEIIDDES-2178 > URL: https://issues.jboss.org/browse/TEIIDDES-2178 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Affects Versions: 8.4, 8.3.2 > Reporter: Ramesh Reddy > Assignee: Mark Drilling > > When using the Teiid connection importer it sends the query to the server and waits for up to 120 seconds for server to return metadata. If the server returned data it is fine, otherwise it fails. > Some times when working with larger metadata or slower connections it may take more than 120 seconds, the UI should give user an option to terminate or wait for another +n of seconds. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2178) Teiid Connection importer by default only waits for 120 seconds for schema

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2178?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-2178. ------------------------------------- Assignee: Mark Drilling Resolution: Rejected The timeout is configurable - see Teiid Designer preferences. > Teiid Connection importer by default only waits for 120 seconds for schema > -------------------------------------------------------------------------- > > Key: TEIIDDES-2178 > URL: https://issues.jboss.org/browse/TEIIDDES-2178 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Affects Versions: 8.4, 8.3.2 > Reporter: Ramesh Reddy > Assignee: Mark Drilling > > When using the Teiid connection importer it sends the query to the server and waits for up to 120 seconds for server to return metadata. If the server returned data it is fine, otherwise it fails. > Some times when working with larger metadata or slower connections it may take more than 120 seconds, the UI should give user an option to terminate or wait for another +n of seconds. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2181) Teiid Instance URL is displayed wrong

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIIDDES-2181: -------------------------------------- Summary: Teiid Instance URL is displayed wrong Key: TEIIDDES-2181 URL: https://issues.jboss.org/browse/TEIIDDES-2181 Project: Teiid Designer Issue Type: Bug Reporter: Ramesh Reddy !mmproto.png! There is no protocol as "mm://" for making a admin connection. The admin connection as you know is managed totally by JBoss EAP. This label has caused confusion in terms of how Teiid uses the admin connection. This is how Teiid may have used 7.x series, but not in 8.x series. I believe I saw this one another place, may be on Teiid Connection Instance page. This needs to be corrected. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2181) Teiid Instance URL is displayed wrong

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2181?page=com.atlassian.jira.plu... ] Ramesh Reddy updated TEIIDDES-2181: ----------------------------------- Attachment: mmproto.png > Teiid Instance URL is displayed wrong > ------------------------------------- > > Key: TEIIDDES-2181 > URL: https://issues.jboss.org/browse/TEIIDDES-2181 > Project: Teiid Designer > Issue Type: Bug > Reporter: Ramesh Reddy > Attachments: mmproto.png > > > !mmproto.png! > There is no protocol as "mm://" for making a admin connection. The admin connection as you know is managed totally by JBoss EAP. This label has caused confusion in terms of how Teiid uses the admin connection. This is how Teiid may have used 7.x series, but not in 8.x series. I believe I saw this one another place, may be on Teiid Connection Instance page. This needs to be corrected. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2177) Teiid Connection Importer should continue to finish even the schema returns no tables

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2177?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2177: ---------------------------------------- Per the last comment on TEIIDDES-1981, we've been elevating Designer's DS needs and capabilities up to the JBT/JBDS level since there are other JBT projects that work with/use Connection Profiles and deployed Data Sources. Teiid is a server submodule and just happens to have an API that can do some DS management. Feel free to chime in on : JBDS-2852 > Teiid Connection Importer should continue to finish even the schema returns no tables > ------------------------------------------------------------------------------------- > > Key: TEIIDDES-2177 > URL: https://issues.jboss.org/browse/TEIIDDES-2177 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Affects Versions: 8.4, 8.3.2 > Reporter: Ramesh Reddy > > Moving my comment from TEIIDDES-1981, as that is completely ignored > Some basic metadata importing has been added to MongoDB translator in 8.7. It may not work with complex documents but simple documents should work. See https://issues.jboss.org/browse/TEIID-2849 > IMO, the way Teiid Connection importer should work is, when the importer does not return any tables it should still go ahead and create a "empty" source model but finish creating the data source stuff etc. Such that when user does add a view manually it works seamlessly. Or give a user an option to create a empty model rather than terminating the whole process. That way JBoss DS is always created when Teiid Connection Importing is used. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 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 May 2014