Bug 1148064 - QueryGuide: indexLocalOnly="true" with RAM directory provider
Summary: QueryGuide: indexLocalOnly="true" with RAM directory provider
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Documentation
Version: 6.3.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Post GA
: 6.4.0
Assignee: jdg-docs@redhat.com
QA Contact: Radim Vansa
URL:
Whiteboard:
Depends On: 1148686
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-30 15:45 UTC by Radim Vansa
Modified: 2020-09-16 06:06 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
: 1148686 (view as bug list)
Environment:
Last Closed: 2020-09-16 06:05:08 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Radim Vansa 2014-09-30 15:45:45 UTC
In https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Data_Grid/6.3/html/Infinispan_Query_Guide/sect-Configure_Indexing.html in Example 2.3 indexLocalOnly is set to true.

While in this particular configuration the setting works (default cache is local and therefore indexLocalOnly does not affect anything), it may be confusing for users who reuse that configuration in replicated cache.

Please, remove this attribute at all.

Also, in Example 2.4 remove line

 .indexLocalOnly(true)

In Example 2.5, change <indexing index="LOCAL"> to <indexing index="ALL">

Comment 2 Divya Mehra 2014-09-30 15:59:53 UTC
We need Need to simplify the indexing configuration - remove variables that do not provide much value, just increase chances of a customer making an error in configuration.

Comment 3 Radim Vansa 2014-10-01 08:40:18 UTC
Divya, this is a documentation bug BZ. Please move any discussion about indexing configuration into separate BZ.

Comment 4 Divya Mehra 2014-10-01 08:43:37 UTC
Radim, the underlying issues is not that of Documentation, but of the default value of indexLocalOnly, which should be false for any clustered cache (and user should not have to specifically set this value). 

So I would suggest that QE open a separate BZ accordingly.

Comment 5 Misha H. Ali 2014-10-01 23:10:18 UTC
Thanks for logging this bug, Radim. I have one other minor bug that I will be pushing as a 6.3.1 patch and this bug looks like a good candidate for a 6.3.1 patch as well. I'll fix it up ASAP and request review so we can push it live ASAP.

Comment 7 Divya Mehra 2014-10-02 05:58:20 UTC
We can't just remove this from documentation until the product's default behavior is correct across cache configurations - local, replicated, distributed cache - so that we would not require this extra variable any more.

Is there a similar tracking BZ for product?
Only after that is verified can we revise Documentation.

Comment 8 Radim Vansa 2014-10-02 09:03:55 UTC
Misha: no, that's not correct. Any configuration using Infinispan directory provider, as in

http://docbuilder.usersys.redhat.com/22937/#Infinispan_Directory_Provider
http://docbuilder.usersys.redhat.com/22937/#Tuning_Infinispan_Directory

needs to have this flag set. Please, return the flag in those configurations.

Comment 9 Radim Vansa 2014-10-02 09:11:31 UTC
(In reply to Divya Mehra from comment #4)
> Radim, the underlying issues is not that of Documentation, but of the
> default value of indexLocalOnly, which should be false for any clustered
> cache (and user should not have to specifically set this value). 
> 
> So I would suggest that QE open a separate BZ accordingly.

The documentation states how the flag should be set in which configuration. IndexLocalOnly must not be false for clustered cache that shares the state across cluster, such as Infinispan directory does.

I have opened https://bugzilla.redhat.com/show_bug.cgi?id=1148740 for further discussion.

Comment 14 Mike McCune 2016-03-28 22:45:31 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions


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