This is an automated email from the ASF dual-hosted git repository.
dbarnes pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/geode.git
The following commit(s) were added to refs/heads/develop by this push:
new 6190edc GEODE-4047 User Guide: Update Lucene docs to include nested
objects, reviewer’s correction
6190edc is described below
commit 6190edcc327070c2899f0a8c3c81d8e0549fb0c6
Author: Dave Barnes <[email protected]>
AuthorDate: Fri Dec 15 12:05:02 2017 -0800
GEODE-4047 User Guide: Update Lucene docs to include nested objects,
reviewer’s correction
---
geode-docs/tools_modules/lucene_integration.html.md.erb | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/geode-docs/tools_modules/lucene_integration.html.md.erb
b/geode-docs/tools_modules/lucene_integration.html.md.erb
index 666d806..3a87100 100644
--- a/geode-docs/tools_modules/lucene_integration.html.md.erb
+++ b/geode-docs/tools_modules/lucene_integration.html.md.erb
@@ -59,9 +59,8 @@ When you create a Lucene index, you must provide three pieces
of information:
You must specify at least one field to be indexed.
-If the object value for the entries in the region comprises a single field to
be indexed and
-searched (for example, some keys have values that are simply strings), then
use `__REGION_VALUE_FIELD`
-to specify the field to be indexed. `__REGION_VALUE_FIELD` serves as the
field name for entry values of all
+If the object value for the entries in the region comprises a primitive type
value without a field name,
+then use `__REGION_VALUE_FIELD` to specify the field to be indexed.
`__REGION_VALUE_FIELD` serves as the field name for entry values of all
primitive types, including `String`, `Long`, `Integer`, `Float`, and `Double`.
Each field has a corresponding analyzer to extract terms from text. When no
analyzer is specified,
@@ -182,7 +181,7 @@ The `FlatFormatSerializer` creates one document for each
parent object, adding a
in a nested object, identified by its qualified name. Similarly, collections
are flattened and
treated as tokens in a single field. For example, the `FlatFormatSerializer`
could convert a
Customer object, with the structure described above, into a document
containing fields such as `name`, `contacts.name`,
-and `contacts.homepage.title`. Each segment is a field name, not a field type,
+and `contacts.homepage.title` based on the indexed fields specified at index
creation. Each segment is a field name, not a field type,
because a class (such as Customer) could have more than one field of the same
type (such as Person).
The serializer creates and indexes the fields you specify when you request
index creation.
@@ -236,7 +235,7 @@ gfsh query:
```
gfsh>search lucene --name=customerIndex --region=Customer
--queryString="contacts.name:Jones77*"
- --defaultField=contacts.name
+ --defaultField=name
```
## <a id="lucene-index-query" class="no-quick-link"></a>Queries
--
To stop receiving notification emails like this one, please contact
['"[email protected]" <[email protected]>'].
