That's why I thought it might be wrong.
It would be a nice feature to be able to specify which sub-elements to index, even if it wasn't complete xpath support. Just to say, differentiate say employee/id from company/id.
Maybe I have to rethink my schema - I was trying to reserve attribute use for some specific purposes.
On Wednesday, November 13, 2002, at 11:47 AM, Jeff Greif wrote:
Try it one more time with -p id
I don't think you can specify an index based on an xpath, only on an element
or [EMAIL PROTECTED] name (with wildcarding allowed).
The source code (org.apache.xindice.core.indexer.Indexer.java) says:
/**
* getPattern returns the pattern recognized by this Indexer. Patterns
* must be in the form of (elem|*)[@(attr|*)] to tell the IndexManager
* which element types to send to it, so for example:
* <pre>
* [EMAIL PROTECTED] Indexes all contacts by name attribute
* memo Indexes the text of all memo elements
* [EMAIL PROTECTED] Indexes all contact attributes
* [EMAIL PROTECTED] Indexes the name attribute for all elements
* * Indexes the text of all elements
* [EMAIL PROTECTED] Indexes all attributes of all elements
* </pre>
* These patterns are used by the IndexManager when handling SAX events.
* All events that match the specified pattern will result in an add or
* remove call to the Indexer.
*
* @return The Pattern used
*/
Jeff ----- Original Message ----- From: "Matthew Van Horn" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Tuesday, November 12, 2002 6:12 PM Subject: Re: [Fwd: Performance question (Am I doing something wrong?)]
I am thinking maybe I screwed up entering the index properly. I did this: xindiceadmin ai -c /db/resumes -n idindex -p "/candidate/biographic_data/id" --maxkeysize 32 -t trimmed -v
Is that correct?
