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

Bug 1335006

Summary:	Examples - hbase as a data source - remove.cli script does not work
Product:	[JBoss] JBoss Data Virtualization 6	Reporter:	Juraj Duráni <jdurani>
Component:	Examples	Assignee:	Van Halbert <vhalbert>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jan Stastny <jstastny>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.3.0	CC:	blafond, dlesage, jolee, mbaluch, vhalbert
Target Milestone:	DR4
Target Release:	6.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	The remove.cli script did not work. You could not remove a driver if some data source was still using it. As a consequence, users had to manually remove items one by one in reverse order. The script has now been fixed. As a result, it now removes all items correctly.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-13 17:36:08 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:

Description Juraj Duráni 2016-05-11 06:48:41 UTC

Description of problem:
remove.cli script does not work. You need to remove items in revers order. You cannot remove driver if some data source is still using it. Please update remove.cli script:

From:
> module remove --name=org.apache.phoenix
> /subsystem=datasources/jdbc-driver=phoenix:remove()
> /subsystem=datasources/data-source=QSPhoenixDS:remove()

To:
> /subsystem=datasources/data-source=QSPhoenixDS:remove()
> /subsystem=datasources/jdbc-driver=phoenix:remove()
> module remove --name=org.apache.phoenix

Comment 2 Valiantsina Hubeika 2017-09-04 16:31:32 UTC

Tested and verified:

$EAP_HOME/bin/jboss-cli.sh -c --file=$EAP_HOME/quickstarts/hbase-as-a-datasource/src/scripts/remove.cli
{"outcome" => "success"}
{"outcome" => "success"}
{
    "outcome" => "success",
    "result" => undefined
}

Comment 3 David Le Sage 2017-11-23 04:26:27 UTC

Documented as a resolved issue in the release notes.