[
https://issues.apache.org/jira/browse/GEODE-2957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030285#comment-16030285
]
ASF GitHub Bot commented on GEODE-2957:
---------------------------------------
Github user joeymcallister commented on a diff in the pull request:
https://github.com/apache/geode/pull/543#discussion_r119232692
--- Diff: geode-docs/tools_modules/lucene_integration.html.md.erb ---
@@ -89,10 +89,10 @@ gfsh>create lucene index --name=indexName
--region=/orders --field=customer,tags
``` pre
// Create an index, specifying a custom analyzer for the second field
-// Note: "null" in the first analyzer position uses the default analyzer
+// Note: "DEFAULT" in the first analyzer position uses the default analyzer
// for the first field
gfsh>create lucene index --name=indexName --region=/orders
- --field=customer,tags
--analyzer=null,org.apache.lucene.analysis.bg.BulgarianAnalyzer
+ --field=customer,tags
--analyzer=DEFAULT,org.apache.lucene.analysis.bg.BulgarianAnalyzer
```
To use the entire value as a single field set the required `--field`
--- End diff --
Cool. LGTM, then. +1
> null used as a default parameter when specifying analyzers
> ----------------------------------------------------------
>
> Key: GEODE-2957
> URL: https://issues.apache.org/jira/browse/GEODE-2957
> Project: Geode
> Issue Type: Bug
> Components: lucene
> Reporter: Jason Huynh
> Assignee: David Anuta
> Fix For: 1.2.0
>
>
> null seems to be the way to specify using the default
> StandardKeywordAnalyzer. This can be used when specifying a long list of
> field/analyzers.
> So the line may look like
> --analyzers="null,SomeAnalyzer,null,null,SomeAnalyzer}
> We should probably change that to default or some other keyword. null seems
> a bit confusing.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
