Bug 1011535 - Infinispan Query Guide: Chapter 2
Summary: Infinispan Query Guide: Chapter 2
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Documentation
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER3
: 6.2.0
Assignee: gsheldon
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-24 13:41 UTC by Anna Manukyan
Modified: 2013-11-26 05:52 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Build Name: 14318, Infinispan Query Guide-6.2-Beta-1 Build Date: 23-09-2013 09:40:40 Topic ID: 14251-507055 [Latest]
Last Closed: 2013-11-26 05:52:58 UTC
Type: Bug


Attachments (Terms of Use)

Description Anna Manukyan 2013-09-24 13:41:21 UTC
I have a general note regarding the Chapter 2 of the Infinispan Query Guide. 

During the whole titles it is talking about the general functionality of queries in JBoss Data Grid and Infinispan Queries, but all code snippets are given for Hibernate Search.

Then later it is explained in details how to use Infinispan Queries, but for the user who starts to read the guide I think it would be very confusing to understand whether now this chapter refers to Hibernate search or it is for Infinispan Query.

Personally I was confused with the snippets and needed to look into our tests to understand what is correct now.

Maybe it worth to have some clarification here so that the reader understands what are Chapter 2 titles about? What do you think?

Comment 2 Misha H. Ali 2013-09-26 23:33:27 UTC
Good point, Anna. We are currently asking Sanne to review the whole guide to find things exactly like this. I'm assigning Gemma to this as she has coordinating the IQ guide effort and we can work in a fix for this, either in conjunction with Sanne's comments about this chapter, or independently.

Comment 3 Misha H. Ali 2013-11-26 05:52:58 UTC
This chapter is excluded for 6.2.


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