Re: ERIndexing (was: How to achieve a fuzzy match searcher)
Re: ERIndexing (was: How to achieve a fuzzy match searcher)
- Subject: Re: ERIndexing (was: How to achieve a fuzzy match searcher)
- From: David LeBer <email@hidden>
- Date: Mon, 19 Oct 2009 08:26:57 -0400
On 2009-10-19, at 8:13 AM, Mike Schrag wrote:
it's not like you wouldn't have the exact same problems in lucene-
proper, though ...
We are using ERIndexing for a multiple instance single server
deployment. However, the app is readonly for the indexed EOs, there is
an admin app that writes, but that is only a single instance.
On Oct 19, 2009, at 7:50 AM, Gustavo Pizano wrote:
NICE!, now my hopes are gone!.
so I guess I must make use de facto lucene framework. and follow
the examples in LIA?
ok.. what can one do... :(
thx
G.
On Mon, Oct 19, 2009 at 1:45 PM, Anjo Krank <email@hidden> wrote:
Be aware that ERIndexing is only an experiment (and was write-only
code, I don't use it yet). In particular it has several severe
drawbacks:
- it doesn't really handle multiple instances (possibly) or servers
(definitely). That means, for the cases where you actually *do*
need the speed of lucene, ie. high-traffic, high-volume which means
many servers, you can't use it as is. At least the auto-indexing
won't work without some central notification point that actually
does the indexing and then redistribute the indexes.
If you don't account for that, your indexes won't really match your
DB, which means that you will find the wrong stuff super-fast...
I don't have a good solution to this, maybe someone who actually
uses it might.
- The DB store for the indexes was an experiment to fix at least
the redistribution problem, but this was truly write only, so use
at your own risk.
- it duplicates your DB indexes and depending on your DB type and
query, your query to resolve the faults probably won't be that much
faster than a normal query would have been.
- it should really be an EO adaptor instead, which would mean that
you could use it in a simple displayGroup. But then again, one of
the main points in Lucene is that you don't really need a strict
schema to work with it - although you'll probably have one.
Cheers, Anjo
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
;david
--
David LeBer
Codeferous Software
'co-def-er-ous' adj. Literally 'code-bearing'
site: http://codeferous.com
blog: http://davidleber.net
profile: http://www.linkedin.com/in/davidleber
twitter: http://twitter.com/rebeld
--
Toronto Area Cocoa / WebObjects developers group:
http://tacow.org
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden