: The problem with TikaEntityProcessor is this installation is still running
: v1.4.1 so I'll need to upgrade.
:
: Any short and sweet instructions for upgrading to 3.2? I have a pretty
: straight forward Tomcat install, would just dropping in the new war suffice?
It should be fairly straight f
On 06/28/2011 12:04 PM, Chris Hostetter wrote:
: 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) t
: 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
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 "
multi value field would allow you to repeat the field when indexing
keywords: "xxx"
keywords: "yyy"
keywords: "sss"
etc
Thanks Lee. the problem
Hi Tod,
A list of keywords would be fine in a non multi valued field:
keywords : "xxx yyy sss aaa "
multi value field would allow you to repeat the field when indexing
keywords: "xxx"
keywords: "yyy"
keywords: "sss"
etc
On 27 June 2011 16:13, Tod wrote:
> This was a little curious to me a
This was a little curious to me and I wondered what the thought process
was behind it before I decide to change it.
Thanks - Tod
