[ https://issues.apache.org/jira/browse/GEODE-2957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16026686#comment-16026686 ]
ASF GitHub Bot commented on GEODE-2957: --------------------------------------- GitHub user karensmolermiller opened a pull request: https://github.com/apache/geode/pull/543 GEODE-2957 gfsh create lucene index "null" becomes "DEFAULT" @DivineEnder @nabarunnag @ladyVader @boglesby @joeymcallister @davebarnes97 Please review. You can merge this pull request into a Git repository by running: $ git pull https://github.com/karensmolermiller/geode feature/GEODE-2957 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/geode/pull/543.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #543 ---- commit fd7dfd0f61f8e46ff8b3a157ffa8f8dacdf74d31 Author: Karen Miller <kmil...@pivotal.io> Date: 2017-05-26T18:57:49Z GEODE-2957 gfsh create lucene index "null" becomes "DEFAULT" ---- > 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)