Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1098405

Summary: Imported VDB as source model can not be updated using a wizard provided by Teiid Designer
Product: [JBoss] JBoss Data Virtualization 6 Reporter: Hisao Furuichi <hfuruich>
Component: TeiidAssignee: Barry LaFond <blafond>
Status: CLOSED NOTABUG QA Contact: Filip Elias <felias>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0.0CC: atangrin, blafond, dlesage, hokuda, lfabriko, mbaluch, mmakovy, nshendye, vhalbert
Target Milestone: ER1   
Target Release: 6.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
It is not possible to update a VDB which has been imported as a source model using the Designer plug-in as the "Update (if existing model selected)" check box is not visible for imported virtual databases being used as source models.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-24 08:20:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
import_by_jdbc_connection.png
none
import_by_jdbc_teiid_connection1.png
none
import_by_jdbc_teiid_connection2.png none

Description Hisao Furuichi 2014-05-16 06:13:28 UTC 
Description of problem:
At first, I can create a sourcemodel based on VDB. See attached screenshot named import_by_jdbc_teiid_connection1.png. I'll call this sourcemodel like "imported VDB as source model".
Although imported relational db as sourcemodel can be updated using a "Create source model for JDBC data source" wizard provided by Teiid Designer, imported VDB as sourcemodel can not be updated.

This is the instruction to updated imported relational db as sourcemodel.

1: create VDB which has a sourcemodel for relational db
2: deploy VDB
3: update schema for relational db like: ALTER TABLE person ADD COLUMN name varchar(20); 
4: start "Create source model for JDBC data source" wizard
5: mark the check box named "Update(if existing model selected) check box" Screenshot is attached as import_by_jdbc_connection.png
6: finish up the wizard.

When I try to update an imported VDB as source model, I can't mark the check box named "Update(if existing model selected) check box". Screenshot is attached as import_by_jdbc_teiid_connection2.png

Steps to Reproduce:
1. create a VDB
2. create another VDB which has a sourcemodel based on the VDB created at step 1
3. modify VDB created at step 1
4. using "Create source model for JDBC data source", update VDB created at step 2

Actual results:
User can not mark the check box named "Update(if existing model selected) check box" 

Expected results:
User can mark the check box named "Update(if existing model selected) check box", and can update a VDB.

Additional info:
I used Teiid Designer 8.3.2.Final-v20140328-2123-B54
Comment 1 Hisao Furuichi 2014-05-16 06:15:02 UTC 
Created attachment 896195 [details]
import_by_jdbc_connection.png
Comment 2 Hisao Furuichi 2014-05-16 06:15:41 UTC 
Created attachment 896196 [details]
import_by_jdbc_teiid_connection1.png
Comment 3 Hisao Furuichi 2014-05-16 06:16:16 UTC 
Created attachment 896197 [details]
import_by_jdbc_teiid_connection2.png
Comment 5 JBoss JIRA Server 2016-06-03 22:43:32 UTC 
Steven Hawkins <shawkins> updated the status of jira TEIID-2982 to Closed
Comment 6 Lucie Fabrikova 2016-07-07 05:00:48 UTC 
The checkbox "Update (if existing model selected)" is still disabled.

In 
org.teiid.designer.jdbc.ui.wizards.JdbcImportOptionsPage.java, there is:


if( this.importer.isVdbSourceModel() ) {
..
this.updateCheckBox.setEnabled(false);
..
}
Comment 8 Matus Makovy 2016-07-07 12:58:06 UTC 
I was talking to Barry about this and from the TD point of view this a correct behavior. If you import from Teiid VDB the checkbox is disabled on purpose.
Comment 10 Van Halbert 2016-07-07 13:35:39 UTC 
The Teiid engine provided the feature to override the visibility.  Why is designer not enabling that option?   By default being "false" is fine.  But it should allow the use to change the visibility after importing.
Comment 11 Matus Makovy 2016-07-08 10:01:09 UTC 
I am not sure if this issue has something to do with visibility. This might a question for Barry.
Comment 12 Barry LaFond 2016-07-11 14:04:38 UTC 
The Import VDB Designer support was limited to allowing users to import source models from deployed VDBs via JDBC.

These VDB Source Models are treated as read-only and can be used as any other source. The Import VDB come into play when adding your view models to your VDB. Any reference to a VDB Source Model will be interpreted as an ImportVDB and the source model will NOT be added to the VDB.

The description of this BZ indicated the user expected to be able to "re-import" a VDB Source Model.  When we designed this feature, we decided to treat the imported model as read-only since it represented the "schema" for a model in a specific VDB on the server.

As addition to the read-only state of the model, we disabled the ability to "update" the source model and required users to delete their VDB source model first, then re-import it from their "changed" VDB.
Comment 14 Matus Makovy 2017-04-24 08:20:11 UTC 
According to Barry's comment this is not a bug.