[
https://issues.apache.org/jira/browse/GEODE-2944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shelley Lynn Hughes-Godfrey updated GEODE-2944:
-----------------------------------------------
Affects Version/s: 1.2.0
> lucene queries on String values (vs. objects) requires obscure/undocumented
> defaultField (__REGION_VALUE_FIELD)
> ---------------------------------------------------------------------------------------------------------------
>
> Key: GEODE-2944
> URL: https://issues.apache.org/jira/browse/GEODE-2944
> Project: Geode
> Issue Type: Bug
> Components: lucene
> Affects Versions: 1.2.0
> Reporter: Shelley Lynn Hughes-Godfrey
>
> When a lucene index is created, one must indicate the field to create the
> index on. When the object value is a simple String, that must be specified
> as --field=__REGION_VALUE_FIELD.
> For example,
> create lucene index --name=newIndex --region=testRegion
> --field=__REGION_VALUE_FIELD
> However, the lucene help text (for the gfsh command) does not provide this
> detail. In addition, it seems that when executing a lucene search, this must
> be entered again as --defaultField=__REGION_VALUE_FIELD.
> While this is probably not something one would use in production, I imagine
> it will be used by developers experimenting with Lucene, so we should
> consider adding this to the help text.
> {noformat}
> gfsh>help create lucene index
> NAME
> create lucene index
> IS AVAILABLE
> true
> SYNOPSIS
> Create a lucene index that can be used to execute queries.
> SYNTAX
> create lucene index --name=value --region=value --field=value(,value)*
> [--analyzer=value(,value)*]
> PARAMETERS
> name
> Name of the lucene index to create.
> Required: true
> region
> Name/Path of the region on which to create the lucene index.
> Required: true
> field
> fields on the region values which are stored in the lucene index.
> Required: true
> analyzer
> Type of the analyzer for each field.
> Required: false
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
