March 2014 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1732) Stream line steps to implement all the steps around materialization

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1732?page=com.atlassian.jira.plu... ] Barry LaFond edited comment on TEIIDDES-1732 at 3/20/14 2:31 PM: ----------------------------------------------------------------- Currently in Designer you can 1) Right-click on a virtual table and select *Modeling > Create Materialized Views" 2) Select/create new Source Model (materialized landing location) 3) click Finish/OK and it'll create the corresponding source table and reference that table in the original virtual table See: http://docs.jboss.org/teiid/designer/8.4/user-guide/en-US/html/metadata-s... was (Author: blafond): Currently in Designer you can 1) Right-click on a virtual table and select *Modeling > Create Materialized Views" 2) Select/create new Source Model (materialized landing location) 3) click Finish/OK and it'll create the corresponding source table and reference that table in the original virtual table > Stream line steps to implement all the steps around materialization > -------------------------------------------------------------------- > > Key: TEIIDDES-1732 > URL: https://issues.jboss.org/browse/TEIIDDES-1732 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Affects Versions: 8.2 > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 8.5 > > > Would like to stream line the steps to putting materialization to work. Example: > - Right mouse click on view, select materialization > - present wizard to walk thru the following options: > - create physical table based on selected view/table (export/import of ddl is supported, but would like the table automatically created) > - put name of mat table into the selected table/view to be materialized > - [optional] export DDL (file system or clipboard) > - [optional] create procedure that has the "select into" for refreshing > Having the procedure provides the immediate ability to call to refresh, without having to remember what tables. Also, with the feature of native queries, could add the truncate call to clear the table. > Once thru this wizard, (I think) everything is in place to do materialization for the specified table. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1984) Enhance security for data roles UI

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1984?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1984. ------------------------------------ Resolution: Done replaced check-box icons with round non-button icons. Done > Enhance security for data roles UI > ---------------------------------- > > Key: TEIIDDES-1984 > URL: https://issues.jboss.org/browse/TEIIDDES-1984 > Project: Teiid Designer > Issue Type: Enhancement > Components: Eclipse Integration > Affects Versions: 8.2, 8.3 > Environment: Windows 7 sp1 64 bit, Eclipse Kepler build: 20130614-0229, JDK 1.6.0_45 > Reporter: Patrick Deenen > Assignee: Barry LaFond > Priority: Minor > Fix For: 8.5 > > > Feature Improvement Request: The "security" checkbox in the data roles editor is not really a checkbox. You need to double-click it in order to get a window to open where you can configure conditions on tables. So therefore, why use a checkbox component? Also, the fact that table level conditions are configured from there and not from the "conditions" tab is confusing. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2003) Usability - In a model, group by types (i.e, Table, procedure, etc.)

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2003?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2003: ---------------------------------------- 1) Create optional dynamic tree folders for *tables*, *procedures* within a model 2) Simply order the children via the content provider ..... tables first, then procedures etc.... > Usability - In a model, group by types (i.e, Table, procedure, etc.) > -------------------------------------------------------------------- > > Key: TEIIDDES-2003 > URL: https://issues.jboss.org/browse/TEIIDDES-2003 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Affects Versions: 8.3 > Reporter: Van Halbert > > From a usability standpoint, and when working with large models, it would good to group by type (i.e, Table, procedure, etc.) when laying out a model in the tree on the left. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2026) Missed metadata on import

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2026?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2026. ------------------------------------ Assignee: Barry LaFond Resolution: Rejected >From debugging, it's apparent that the Oracle driver does not return the NUM_DISTINCT nor NUM_NULLS property values > Missed metadata on import > ------------------------- > > Key: TEIIDDES-2026 > URL: https://issues.jboss.org/browse/TEIIDDES-2026 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.7, 8.3 > Reporter: Johnathon Lee > Assignee: Barry LaFond > > After import, NUM_DISTINCT and NUM_NULLS metadata found in the source system shows as "-1" when the underlying datasource has values. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2041) Null Pointer Exception creating DB2 JDBC Connection

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2041?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2041. ------------------------------------ Assignee: Barry LaFond Resolution: Rejected This was a system/hardware set-up issue. > Null Pointer Exception creating DB2 JDBC Connection > --------------------------------------------------- > > Key: TEIIDDES-2041 > URL: https://issues.jboss.org/browse/TEIIDDES-2041 > Project: Teiid Designer > Issue Type: Bug > Environment: Designer 8.3.1.Final-v20140122-1920-B21. Running in eclipse Kepler on Windows 7 with jdk1.7.0_45 > Reporter: Jim Riley > Assignee: Barry LaFond > > When trying to Make a JDBC connection to DB2 Database a Null Pointer Exception is encountered. The Ping to test the connection is successful. > I tried connecting to a AIX DB2 instance and a Mainframe instance. The result was the same. > The detailed messages is: > Could not connect to New Generic JDBC. > Error creating SQL Model Connection connection to New Generic JDBC. (Error: null) > java.lang.NullPointerException > OK > The log file contains: > !ENTRY org.eclipse.datatools.connectivity 4 -1 2014-02-06 10:18:14.869 > !MESSAGE Could not connect to DMS Net Driver JDBC. > !SUBENTRY 1 org.eclipse.datatools.connectivity 4 -1 2014-02-06 10:18:14.869 > !MESSAGE Error creating SQL Model Connection connection to DMS Net Driver JDBC. (Error: null) > !STACK 0 > java.lang.NullPointerException > at org.eclipse.datatools.connectivity.sqm.internal.core.util.DatabaseProviderHelper.getCatalogDatabase(DatabaseProviderHelper.java:37) > at org.eclipse.datatools.connectivity.sqm.internal.core.util.DatabaseProviderHelper.setDatabase(DatabaseProviderHelper.java:47) > at org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionInfoImpl.initializeJDBCConnection(ConnectionInfoImpl.java:718) > at org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionInfoImpl.<init>(ConnectionInfoImpl.java:690) > at org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionFactory.createConnection(ConnectionFactory.java:38) > at org.eclipse.datatools.connectivity.sqm.core.SQMConnectionFactory.createConnection(SQMConnectionFactory.java:45) > at org.eclipse.datatools.connectivity.sqm.internal.core.connection.ConnectionFactory.createConnection(ConnectionFactory.java:59) > at org.eclipse.datatools.connectivity.internal.ConnectionFactoryAdapterProvider.createConnection(ConnectionFactoryAdapterProvider.java:114) > at org.eclipse.datatools.connectivity.internal.ManagedConnection.createConnection(ManagedConnection.java:163) > at org.eclipse.datatools.connectivity.internal.CreateConnectionJob.run(CreateConnectionJob.java:56) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > !SUBENTRY 1 unknown 0 0 2014-02-06 10:18:14.869 -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2066) Re-deploy of VDB with auto-generated REST wars does not always deploy wars

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2066?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2066: ----------------------------------- Fix Version/s: 8.5 Assignee: Mark Drilling > Re-deploy of VDB with auto-generated REST wars does not always deploy wars > -------------------------------------------------------------------------- > > Key: TEIIDDES-2066 > URL: https://issues.jboss.org/browse/TEIIDDES-2066 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 8.3.1 > Reporter: Mark Drilling > Assignee: Mark Drilling > Fix For: 8.5 > > > When re-deploying a VDB that auto-generates REST wars, the wars do not always get deployed and registered on the teiid instance. > I have logged the (linked) issue with teiid, but in the meantime we should change the ExecutionAdmin logic to explicitly un-deploy a VDB (if it exists) before doing the deploy. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2069) Improve Default Server naming and make it consistent

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2069?page=com.atlassian.jira.plu... ] Barry LaFond edited comment on TEIIDDES-2069 at 3/20/14 12:58 PM: ------------------------------------------------------------------ I'd be good with setting default to the JBoss Server display name. As far as I can tell, we don't provide any dialog or name entry widget to set the Teiid display name. User has to create server first, then open server editor and click on Teiid Instance tab to get to it. was (Author: blafond): I'd be good with setting default to the JBoss Server display name. > Improve Default Server naming and make it consistent > ---------------------------------------------------- > > Key: TEIIDDES-2069 > URL: https://issues.jboss.org/browse/TEIIDDES-2069 > Project: Teiid Designer > Issue Type: Enhancement > Components: Teiid Integration > Affects Versions: 8.4 > Reporter: Mark Drilling > Assignee: Mark Drilling > Fix For: 8.5 > > Attachments: ServerDefaultView.png, SetDefaultServerDialog.png > > > We are inconsistent in the way we name/display the default teiid instances in designer. > We supply a 'Display Name' on the server teiid instance panel, but it is empty by default. So when you have multiple local JBoss servers (and dont supply a display name) they are all displayed as 'mm://localhost:9999' in the default server view. This is really confusing as to which instance you've selected as the default. > Also, in the 'Change Default Dialog'. The names in the dropdown get really long and ugly - especially if you provide a teiid instance name. See attached screenshot. > I'm thinking, just set a default for the teiid instance 'display name' initially. Either just use the JBoss server name or something based on it. Then use that name consistently in the Default server view and selection dialog. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2069) Improve Default Server naming and make it consistent

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2069?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2069: ----------------------------------- Fix Version/s: 8.5 Assignee: Mark Drilling I'd be good with setting default to the JBoss Server display name. > Improve Default Server naming and make it consistent > ---------------------------------------------------- > > Key: TEIIDDES-2069 > URL: https://issues.jboss.org/browse/TEIIDDES-2069 > Project: Teiid Designer > Issue Type: Enhancement > Components: Teiid Integration > Affects Versions: 8.4 > Reporter: Mark Drilling > Assignee: Mark Drilling > Fix For: 8.5 > > Attachments: ServerDefaultView.png, SetDefaultServerDialog.png > > > We are inconsistent in the way we name/display the default teiid instances in designer. > We supply a 'Display Name' on the server teiid instance panel, but it is empty by default. So when you have multiple local JBoss servers (and dont supply a display name) they are all displayed as 'mm://localhost:9999' in the default server view. This is really confusing as to which instance you've selected as the default. > Also, in the 'Change Default Dialog'. The names in the dropdown get really long and ugly - especially if you provide a teiid instance name. See attached screenshot. > I'm thinking, just set a default for the teiid instance 'display name' initially. Either just use the JBoss server name or something based on it. Then use that name consistently in the Default server view and selection dialog. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2083) VDB datasource creation enhancements

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2083?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-2083: ---------------------------------------- Yes, if you two separate users are using the pool and and connections are cached then that can be issue. Unless you set the idle connection to zero, i.e. you create connection every time. or we configure like user-specific pools. I know web-services choose connection pool because, WAR could be deployed in a separate VM, but when deployed in the same VM the same issue will happen IMO. Since these are two are embedded applications the risk is low, but still issue at large IMO. > VDB datasource creation enhancements > ------------------------------------ > > Key: TEIIDDES-2083 > URL: https://issues.jboss.org/browse/TEIIDDES-2083 > Project: Teiid Designer > Issue Type: Enhancement > Components: Teiid Integration > Reporter: Ramesh Reddy > > 1) When a VDB is deployed, "Create VDB DataSource" dialog pops up, it asks the user whether to create a data source for VDB, but does not provide a "cancel" button to opt out. There should be a "cancel" to opt out. > * BML - There is a Cancel button on the dialog > 2) If you are re-deploying the same VDB, the same dialog pops up again asking the same question, it should be changed to honor the previous answer. > 3) Say if the user did create a data source, then in re-deploy case the data source either needs to be deleted and re-created or flush the connections in the old data source, so that the connections point to valid VDB rather than stale connections. > 4) It would be even nice, "Remember My Decision" kind of preference, that could always create or not create data source, rather than keep asking the user. > BTW, this feature is only useful for the Web Service scenarios, so I would start off with OFF position. May be turn it on only ask when web service model in the work space if you want to be fancy. Also detect the name of data source in the web-service war creation scenarios, or let them create with a button right next to it. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2083) VDB datasource creation enhancements

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2083?page=com.atlassian.jira.plu... ] Van Halbert commented on TEIIDDES-2083: --------------------------------------- In our testing with dashboard, teiid datasource is created using a pool with pass thru. Are you saying there could be issues with this? I'm thinking, are we not testing it correctly to hit the issue. > VDB datasource creation enhancements > ------------------------------------ > > Key: TEIIDDES-2083 > URL: https://issues.jboss.org/browse/TEIIDDES-2083 > Project: Teiid Designer > Issue Type: Enhancement > Components: Teiid Integration > Reporter: Ramesh Reddy > > 1) When a VDB is deployed, "Create VDB DataSource" dialog pops up, it asks the user whether to create a data source for VDB, but does not provide a "cancel" button to opt out. There should be a "cancel" to opt out. > * BML - There is a Cancel button on the dialog > 2) If you are re-deploying the same VDB, the same dialog pops up again asking the same question, it should be changed to honor the previous answer. > 3) Say if the user did create a data source, then in re-deploy case the data source either needs to be deleted and re-created or flush the connections in the old data source, so that the connections point to valid VDB rather than stale connections. > 4) It would be even nice, "Remember My Decision" kind of preference, that could always create or not create data source, rather than keep asking the user. > BTW, this feature is only useful for the Web Service scenarios, so I would start off with OFF position. May be turn it on only ask when web service model in the work space if you want to be fancy. Also detect the name of data source in the web-service war creation scenarios, or let them create with a button right next to it. -- 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, 11 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 March 2014