[
https://issues.apache.org/jira/browse/GEODE-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030145#comment-16030145
]
ASF GitHub Bot commented on GEODE-3002:
---------------------------------------
Github user joeymcallister commented on a diff in the pull request:
https://github.com/apache/geode/pull/550#discussion_r119217398
--- Diff: geode-docs/tools_modules/gfsh/command-pages/search.html.md.erb ---
@@ -62,12 +62,12 @@ search lucene --name=value --region=value
--queryStrings=value --defaultField=va
</tr>
<tr>
<td><span class="keyword parmname"
style="whitespace:nowrap;">‑‐queryStrings</span></td>
-<td><em>Required</em>. Query string to search the lucene index.</td>
+<td><em>Required</em>. Query string to search the lucene index. Use
<code>__REGION_VALUE_FIELD</code> as the field name within the query string
when the field is a primitive value.</td>
--- End diff --
Is there a contextual reason to use "lucene index" here, rather than
"Lucene" index with a capital L?
> Improve doc of (Lucene) __REGION_VALUE_FIELD
> --------------------------------------------
>
> Key: GEODE-3002
> URL: https://issues.apache.org/jira/browse/GEODE-3002
> Project: Geode
> Issue Type: Bug
> Components: docs
> Reporter: Karen Smoler Miller
> Assignee: Karen Smoler Miller
> Priority: Minor
>
> The original description of {{__REGION_VALUE_FIELD}} is not quite right. In
> addition, there is an example gfsh command using this value that is wrong.
> It is in the {{gfsh create lucene index}} command reference page.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
