Hi,
Am using Solr facets for my data and have a field which has multiple values
in its field am using ; to delimit those values. So after doing a solr
search it returns me a facet array but that contains ; in the facet value.
I want facet to return each as separate values.
For eg. am using the
on multiple values
Hi,
Am using Solr facets for my data and have a field which has multiple values in
its field am using ; to delimit those values. So after doing a solr search it
returns me a facet array but that contains ; in the facet value.
I want facet to return each as separate values.
For eg
[mailto:shishir.j...@gmail.com]
Gesendet: Donnerstag, 29. Juli 2010 17:10
An: solr-user@lucene.apache.org
Betreff: Facets on multiple values
Hi,
Am using Solr facets for my data and have a field which has multiple values in its field am using
; to delimit those values. So after doing a solr search it returns
On Thu, 29 Jul 2010 20:39:57 +0530
Shishir Jain shishir.j...@gmail.com wrote:
Hi,
Am using Solr facets for my data and have a field which has
multiple values in its field am using ; to delimit those
values. So after doing a solr search it returns me a facet array
but that contains ; in the
: tokenizer class=solr.PatternTokenizerFactory pattern=; * /
...
: Whether to use this idea or Bastian's depends on how the original data source
: is organized.
it also depends on what you want to get *out* if this is a stored field
... using an analyzer like this will deal with letting
On 7/29/2010 12:18 PM, Chris Hostetter wrote:
it also depends on what you want to get *out* if this is a stored field
... using an analyzer like this will deal with letting you facet on the
individual terms, but the stored vaue returned with each document will
still be a single semi-colon
: My initial approach was to grab the values (which are in another table) with a
: DIH subentity and store them in a multivalued field, but that reduced index
: speed to a crawl. That's because instead of one query for the entire import,
: it was making an individual subquery for every document
On 7/29/2010 1:13 PM, Chris Hostetter wrote:
: My initial approach was to grab the values (which are in another table) with a
: DIH subentity and store them in a multivalued field, but that reduced index
: speed to a crawl. That's because instead of one query for the entire import,
: it was
Certainly lots of matches on Solr and facets.
Contrived example:
* Solr 1.4, etc.
* Yellow pages, business listings.
* Business listings have a zip code that I will use in Faceted search.
* Companies with multiple stores/outlets/offices still only have one record,
but all applicable zip codes are
Hi Mark,
If (a) is wanted behaviour, i.e. have a business show up in facets for all
ZIPs, you should define a multi-valued ZIP field. Since a ZIP is a number, I
don't see any reason for any analysis on it, a String or a lightly normalized
field type would do the job both for search and facets.
10 matches
Mail list logo