I've had the same problem...
I actually solved it by switching collection compression to true.
Uncompressed collections thus have issues with index management.
Bye
At 16:55 23/02/2004, you wrote:
Re: your final question, there is currently no way
to get just the doc ids.
Best you can do to ensure e
Terry Rosenbaum wrote:
Re: your final question, there is currently no way
to get just the doc ids.
Would it make sense to add such feature? What API would look like?
Vadim
Re: your final question, there is currently no way
to get just the doc ids.
Best you can do to ensure efficiency is
to select a small fragment of the resource
thus minimizing the excess bytes transmitted.
WRT the index creation problem,
you could help the project if you can
write a unit test demons
> Have you tried running the unit tests?
No, not now.
The http://marc.theaimsgroup.com/?l=xindice-users&m=107426829426034&w=2
solved my problem, but I dont know why - so I won't create the index during
the creation of the collection, furthermore after that with that given
function.
I've recreated
Have you tried running the unit tests?
The test IndexedSearchTest in
java/tests/src/org/apache/xindice/integration/client/services
includes a number of tests that test not only
whether or not indexed searching is working, but
also test whether or not indexing speeds up
the query. One of the tests u
Hello,
I finally getting headage during the configuration of Xindice. I'm using
Xindice 1.1b3 (currently Ive tried a CVS checkout from today morning) in Jboss
with Jetty as exploded war-archive.
I've created a collection with following code snippet:
---
