geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From joeymcallister <>
Subject [GitHub] geode pull request #550: GEODE-3002 Clarify __REGION_VALUE_FIELD in Lucene d...
Date Tue, 30 May 2017 21:16:23 GMT
Github user joeymcallister commented on a diff in the pull request:
    --- Diff: geode-docs/tools_modules/gfsh/command-pages/ ---
    @@ -62,12 +62,12 @@ search lucene --name=value --region=value --queryStrings=value --defaultField=va
     <td><span class="keyword parmname" style="whitespace:nowrap;">&#8209;&#8208;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?

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message