Bug 1265849 - Data Sets extension - Elastic Search Data provider is not provided neither in kie-wb and kie-drools-wb, but the provider type is available for being selected from Data Sets auhoring view
Data Sets extension - Elastic Search Data provider is not provided neither in...
Product: JBoss BPMS Platform 6
Classification: JBoss
Component: BAM (Show other bugs)
Unspecified Unspecified
high Severity unspecified
: ER4
: 6.2.0
Assigned To: Roger Martínez
Jan Hrcek
Depends On:
  Show dependency treegraph
Reported: 2015-09-23 18:45 EDT by Roger Martínez
Modified: 2015-10-29 09:23 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Roger Martínez 2015-09-23 18:45:25 EDT
Description of problem:

In both kie-wb and kie-drools-wb, a user is able, from the UI, to create a new data set using the Elastic Search data provider in the Data Sets authoring view, but on the other hand, the backend side artifact for elastic search is not packaged in the resulting WAR.

The problem is that the artifact was excluded in both workbenchs some time ago due to compilation problems, and the exclusion has to be removed now as the Elastic Search data provider is available and working fine in latest Dashbuilder distribution.

- https://github.com/droolsjbpm/kie-wb-distributions/blob/6.3.x/kie-wb/kie-wb-webapp/pom.xml#L634

- https://github.com/droolsjbpm/kie-wb-distributions/blob/6.3.x/kie-drools-wb/kie-drools-wb-webapp/pom.xml#L479

NOTE: This bug is same as the JIRA one -> https://issues.jboss.org/browse/JBPM-4776

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Actual results:

Elastic search data provider does not work.

Expected results:

Additional info:
Comment 3 Jan Hrcek 2015-10-29 09:23:14 EDT
Ok, I tried connecting to Elastic search instance running locally and it's working fine. Verified with BPM Suite 6.2.0 ER4.

Note You need to log in before you can comment on or make changes to this bug.