There was a very impressive demonstration of SOLR at OSCON this year, and it looks very, very easy to set up for light(i.e. reasonable but not-heavy) usage. The default install comes pretty much ready to roll - you'll have to tweak out a "schema" description of what you're indexing, and work on a way to do inserts, updates, and deletes from your database (it's a straight REST interface) - but that's really it.
I've started working on this myself, but I haven't gotten past getting SOLR loaded onto the local machine and digging into my (current) TSearch2 schema to see what I want to load, index, and store within SOLR. -joe On 8/8/07, Gábor Farkas <[EMAIL PROTECTED]> wrote: > > Jarek Zgoda wrote: > > I don't know what do you mean by "transactions" in case of full-text > > search engine as it doesn't do any multi-step updates (only single- > > step deletes or inserts in case of PyLucene). > > > > Anybody who wants to use PyLucene, be aware that you cann't embed (iow > > "use", "import") PyLucene in your Django application code if your web > > server is either forking or threadinig one. You have to build a > > service that is separated from any threading or forking. Does it still > > seems reasonable to anybody? Well, if yes, welcome to pylucene-dev > > mailing list. ;) > > another way to use Lucene in django would be solr > (http://lucene.apache.org/solr/), but i have never tried it. > > gabor > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
