From: Arnone, Anthony <aarnone@ri...> - 2005-10-24 16:48:05
Very sorry about that. That was the old CLucene API. I've now rewritten
the API to accept an STL hash. The offending line
The document object will contain a structure that the CLucene API
Has been changed to
The document object will contain a STL hash that the CLucene API expects
Anyway, the way this works is that the CLucene API will now take a
generic hash of all the fields in a document (body, title, meta_desc,
etc...) and fill its internal document with those fields. The hash looks
something like this:
Those char's will eventually be replaced with wchar_t's. What this means
to the API is this:
<field_name, <field_contents, field_type> >
field_name is the name of the field (body, title, etc..)
field_contents is the actual words/data in the field
field_type is the CLucene type, which can be one of four different
Take a look at DocumentRef::initialize() in htcommon/DocumentRef.cc to
see what kind of fields are already defined, along with their types.
Hope this clears it up somewhat,
[mailto:htdig-dev-admin@...] On Behalf Of Gustave
Sent: Saturday, October 22, 2005 11:46 AM
Subject: [htdig-dev] what is a structure?
Anthony and Neal:
I'm reading the design document=20
(http://opensource.rightnow.com/htdig4_refactor_design.pdf) and I see=20
several references to custom "structures". My understanding of a=20
structure is that it is a labeled array (whose elements may also be=20
labeled arrays). Is that what you are referring to? If not, if you=20
could point me to what you are talking about, that would be great.
Thanks in advance.
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
ht://Dig Developer mailing list:
List information (subscribe/unsubscribe, etc.)