On 06/27/2011 11:23 AM, lee carroll wrote:
Hi Tod,
A list of keywords would be fine in a non multi valued field:
keywords : "xxx yyy sss aaa qqqq"
multi value field would allow you to repeat the field when indexing
keywords: "xxx"
keywords: "yyy"
keywords: "sss"
etc
Thanks Lee. the problem is I'm manually pushing a document (via
stream.url) and its metadata from a database with the Solr
/update/extract REST service, HTTP GET, using Perl.
I'm streaming over the document content (presumably via tika) and its
gathering the document's metadata which includes the keywords metadata
field. Since I'm also passing that field from the DB to the REST call
as a list (as you suggested) there is a collision because the keywords
field is single valued.
I can change this behavior using a copy field. What I wanted to know is
if there was a specific reason the default schema defined a field like
keywords single valued so I could make sure I wasn't missing something
before I changed things.
While I'm at it, I'd REALLY like to know how to use DIH to index the
metadata from the database while simultaneously streaming over the
document content and indexing it. I've never quite figured it out yet
but I have to believe it is a possibility.
- Tod
