Bug 1335006 - Examples - hbase as a data source - remove.cli script does not work
Summary: Examples - hbase as a data source - remove.cli script does not work
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Examples
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: DR4
: 6.4.0
Assignee: Van Halbert
QA Contact: Jan Stastny
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-11 06:48 UTC by Juraj Duráni
Modified: 2018-02-13 17:36 UTC (History)
5 users (show)

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.
Clone Of:
Environment:
Last Closed: 2018-02-13 17:36:08 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker TEIID-4315 0 Minor Resolved HBase Quickstart issues 2018-02-07 23:35:23 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.