: This is really cool. U... How does it integrate with the Data Import
: Handler?
my DIH knowledge is extremely limited, but i'm guessing approach #1 is
trivial (there is an easy way to concat DB values to build up solr field
values right?); approach #2 would probably be possible using
On Thu, Dec 11, 2008 at 4:41 AM, Chris Hostetter
[EMAIL PROTECTED] wrote:
: This is really cool. U... How does it integrate with the Data Import
: Handler?
my DIH knowledge is extremely limited, but i'm guessing approach #1 is
trivial (there is an easy way to concat DB values to build up
This is really cool. U... How does it integrate with the Data Import
Handler?
Lance
-Original Message-
From: Chris Hostetter [mailto:[EMAIL PROTECTED]
Sent: Friday, December 05, 2008 8:31 PM
To: solr-user@lucene.apache.org
Subject: Re: Dealing with field values as key/value pairs
: So i'm basically looking for design pattern/best practice for that scenario
: based on people's experience.
I've taken two approaches in the past...
1) encode the id and the label in the field value; facet on it;
require clients to know how to decode. This works really well for simple
Yeh, sorry was not clear in my question. Storage would end up being done
the same way of course
I guess I'm more looking for feedback about what people have used as a
strategy to handle this type of situation. This goes for faceting as well.
Assuming I do faceting by author and there is 2
Hi all,
I'm looking for ideas about how to best deal with a situation where I
need to deal with storing key/values pairs in the index for consumption
in the client.
Typical example would be to have a document with multiple genres where
for simplicity reasons i'd like to send both the 'id'
In the end lucene stores stuff as strings.
Even if you do store your data as map FieldType , Solr May not be able
to treat it like a map.
So it is fine to put is the map as one single string
On Mon, Dec 1, 2008 at 10:07 PM, Stephane Bailliez [EMAIL PROTECTED] wrote:
Hi all,
I'm looking for
