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 mak
: 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 r
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 sepera
:
...
: 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 you facet on the
individual terms, but the stored vaue re
I'm developing a new schema that includes something similar. The DIH
database select statement uses a left join to gather a set of values for
each main record into a new field, separated by semicolons. I put the
result into a fieldType with the following analyzer chain, which breaks
it up in
just define the keyword field as multivalued and add the keywords separatly,
not as single-valued-string.
cheers.
-Ursprüngliche Nachricht-
Von: Shishir Jain [mailto:shishir.j...@gmail.com]
Gesendet: Donnerstag, 29. Juli 2010 17:10
An: solr-user@lucene.apache.org
Betreff: Facets on mul
