Well, lucene is blazingly quick and sometimes things take less time than one might expect, but your combination of large and very large is not encouraging. It doesn't sounds like the new API method would necessarily need an exact reply - could you run something in the background out of peak hours that built the XML response or at least saved numbers for it to be built quickly when requested? Depending on the volatility of your indexes, the background job could be somewhat intelligent and only update the figures for indexes that have had significant activity. Defining significant activity is left as an exercise for the reader ...
Good luck. -- Ian. On Tue, Nov 3, 2009 at 9:23 AM, Henrik Hjalmarsson <henrik.hjalmars...@raa.se> wrote: > Hello > > I am trying to develop an API for a search application that is using Lucene > 2.4.1 > The search application is maintained by RAA (swedish goverment organization > that keeps track of historical and cultural data). > > I have gotten a demand for an API method that returns an XML response, > listing all the indexes in this application and the number of unique values > these indexes can have, filtered by a query that is recieved in the method > request. > > The application contains a large amount of indexes and some indexes contains > a very large amount of unique values. Is there some way to achive this in an > effective way? > > With regards Henrik > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
