geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-2957) null used as a default parameter when specifying analyzers
Date Wed, 31 May 2017 23:15:04 GMT

    [ https://issues.apache.org/jira/browse/GEODE-2957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032177#comment-16032177
] 

ASF subversion and git services commented on GEODE-2957:
--------------------------------------------------------

Commit 806751805cb47877b609ee35cbfa21b362a3d7b3 in geode's branch refs/heads/feature/GEODE-2632-19
from [~karensmolermiller]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=8067518 ]

GEODE-2957 gfsh create lucene index "null" becomes "DEFAULT"

    This closes #543


> 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)

Mime
View raw message