|
I've been working on the XML-RPC interface and have
been pounding my head against the
wall for the last few hours until I found
this: It seems there is a bug in the dropIndexer() routine leaving
document
fragments in the SysConfig.tbl file.
Test case: all of the operations were done using
the command line tools after I noticed that my XML-RPC calls
were failing.
1. Build CVS from
1/24/2002
2. Create a new collection
xindiceadmin ac -c /db -n test
3. Add a document or two (I used
the address book format for this test)
4. Create an index:
xindiceadmin ai -c /db/test -n test1 -p lname
5. Create another index:
xindiceadmin ai -c /db/test -n test2 -p fname
6. At this point, the
SysConfig.tbl file looks fine.
7. Now drop the first indexer:
xindiceadmin di -c /db/test -n test1
8. SysConfig.tbl file is
corrupted with a document fragment of the remaining indexer
9. Drop the second indexer:
xindiceadmin di -c /db/test -n test2
10. Ditto on the document fragment, now there
are two!
Any ideas?
Kurt
|
- Re: Indexer creation/removal Kurt Ward
- Re: Indexer creation/removal Kurt Ward
- Re: Bug:Indexer creation/removal Kurt Ward
