Bug 1024315

Summary: Infinispan Query Guide: 4.1.2. Configuring Infinispan Query
Product: [JBoss] JBoss Data Grid 6 Reporter: Anna Manukyan <amanukya>
Component: DocumentationAssignee: Mandar Joshi <majoshi>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: amanukya, jdg-bugs, mhusnain, pyaduvan, sanne
Target Milestone: GA   
Target Release: 6.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Build Name: 14318, Infinispan Query Guide-6.2-Beta-1 Build Date: 22-10-2013 18:24:19 Topic ID: 13533-481465 [Latest]
Last Closed: 2013-12-06 11:48:49 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:

Description Anna Manukyan 2013-10-29 11:29:17 UTC
This bug relates to the general meaning of this chapter.

1. There are 2 different chapters with the same naming - 4.1.2 and 4.2.2 . 

2. The Procedure 4.1. "Configure Infinispan Query for Red Hat JBoss Data Grid" is confusing and not understandable:
  * where the specified properties should be written (in which file, located where);

3. I guess the procedure given here refers again to the Hibernate Search and not to the Infinispan Queries, but in the first sentences of this chapter it is told that the procedure is for configuring Infinispan Queries in JDG.

Comment 2 Anna Manukyan 2013-10-29 11:37:01 UTC
One more thing related this issue, in the procedure 4.1, 1st step code snippet - it is written:

default.<indexname>.directory_provider infinispan

should this line appear this way or there should be equals sign in between?

Comment 5 Misha H. Ali 2013-12-06 06:00:34 UTC
These should be fixed now. Please follow up by checking the mentioned sections and comparing with the reported problems. If unsure, check with either:

* Sanne
* Adrian (anistor)
* martin gencur
* vitalii

To see if this issue is fixed and close it NOTABUG if not.