Hi, I can prepare that indexing fields, please send requirements - ie what field should go into which index
Yes, the 'all' field contains any field ever found, but be aware that at the current moment, no funny tokenizer/analyzer is used, so the number of tokens may decrease (for instance, they are case sensitive now). As for the live search, I could plug the index into the test site - if I can edit search_engine.py file and somebody can insert the trigger, should be very easy. Then you can all test as much as you want. What would you think? roman On Thu, Aug 19, 2010 at 4:48 PM, Tibor Simko <[email protected]> wrote: > On Thu, 19 Aug 2010, Roman Chyla wrote: >> Index size: 1.1 GB (not optimized -- therefore bigger) > > Does `all' emulate our `any field' index? Seems to have more terms, so > seems to include more fields. > > It would be good to create a Lucene equivalent of some of our indexes, > say title: > > title: 210__a 245__a 246__a 242__a > > and compare only that regarding number of terms, size, etc. > > Also, the indexing times are good, what about the search times, say > `model NOT x-ray' in `title'? It would be good to sit together to play > with the instance live... > > Best regards > -- > Tibor Simko >
