Bug 1033324 - Remove references to Limiting Object Embedding to Specific Paths
Summary: Remove references to Limiting Object Embedding to Specific Paths
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Documentation
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: GA
: 6.2.0
Assignee: Misha H. Ali
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-21 21:03 UTC by Sanne Grinovero
Modified: 2014-01-16 00:01 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Build Name: 14318, Infinispan Query Guide-6.2-1 Build Date: 21-11-2013 08:29:28 Topic ID: 21708-495668 [Latest]
Last Closed: 2014-01-16 00:01:26 UTC
Type: Bug


Attachments (Terms of Use)

Description Sanne Grinovero 2013-11-21 21:03:33 UTC
Title: Limiting Object Embedding to Specific Paths

Describe the issue: this feature is not relevant to JDG users.
Remove the whole section

Comment 2 Misha H. Ali 2013-11-22 00:23:59 UTC
We will remove this at the end.

Comment 3 Misha H. Ali 2013-11-22 04:57:46 UTC
Made the following changes:

    The targetElement Property [21684]
#  Section: Limiting Object Embedding to Specific Paths [21708]
#    Using the includePaths Property [21706]
#    Implementing Specific Paths [21707]
  Section: Boosting [14275]

Comment 4 Martin Gencur 2013-11-25 13:49:30 UTC
Verified that these were removed:
#  Section: Limiting Object Embedding to Specific Paths [21708]
#    Using the includePaths Property [21706]
#    Implementing Specific Paths [21707]

What does "boosting" mean? "Dynamic Index Time Boosting" ?  ....Sanne recommended to preserve this.

Comment 5 Misha H. Ali 2013-11-27 02:46:05 UTC
Adding Vitalii for a quick QE verification.

Comment 6 Misha H. Ali 2014-01-16 00:01:26 UTC
The fix for this bug is now generally released and available here:

https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Data_Grid/6.2/index.html


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