Bug 1335004

Summary:	Examples - hbase as a data source - setup.cli script uses deprecated option
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:	low
Version:	6.3.0	CC:	blafond, dlesage, jolee, jstastny, 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 setup.cli script for the HBase data source contained depreacted commands and required the user to manually reload the server before a data source could be created. The script has now been updated with corrected instructions. As a result, users do not need to reload the server before creating HBase data sources.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-13 17:40:58 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:35:35 UTC

Description of problem:
As far as I know, option 'enabled=true' of 'add' operation for data-source is deprecated in CLI. Moreover, user needs to reload server to be able to use create data source. Please, update the script like follows:

From:
> /subsystem=datasources/data-source=QSPhoenixDS:add(jndi-name="java:/QSPhoenixDS",driver-name=phoenix,connection-url=jdbc:phoenix:127.0.0.1:2181,user-name=sa,password=sa,enabled=true,use-java-context=true)

To:
> /subsystem=datasources/data-source=QSPhoenixDS:add(jndi-name="java:/QSPhoenixDS",driver-name=phoenix,connection-url=jdbc:phoenix:127.0.0.1:2181,user-name=sa,password=sa,use-java-context=true)
> /subsystem=datasources/data-source=QSPhoenixDS:enable

Comment 1 Juraj Duráni 2016-05-11 06:44:40 UTC

Also remove :reload() at the end of setup.cli script.

Comment 3 David Le Sage 2017-11-23 04:33:25 UTC

Documented as a resolved issue in the release notes.