Can you share the answer you found?
On Sun, Apr 24, 2011 at 8:31 AM, wenlei zhou wrote:
> Hi, WeiWei
> I have found the answer~~ Thank you very much!
>
> regards,
> Zhou Wenlei
>
> On 24 April 2011 19:29, wenlei zhou wrote:
>
> > Hi, WeiWei
> >
> > I find that org.tartarus.snowball.ext.PorterSt
ss you have a mission critical system, the approach should be
> more than sufficient.
>
>
>
> On Sat, Jan 22, 2011 at 10:58 AM, software visualization
> wrote:
> > If I understand you correctly, I think that this :
> >
> > If T2 < T1, Skip the result.
> >
>
User Searches b)
> Search System gets Document ID + Modification Time Stamp (T2) and gives to
> Presentation layer which compares the T1 & T2.
> If T2 < T1, Skip the result.
>
> Assumption : Stored document is always in sync. Documents are
> persisted somewhere and not ser
Hi sorry for the long delay.
The idea is that a single user is editing a single document. As they edit,
any indexes built against the document become stale, actually wrong.
Example: references to specific localities within this document are all
instantly wrong the first time a user types a new be
matter how fast the indexing speed is.
> If you can accept this inconsistency, you do not need to index so
> frequently at all.
>
>
> -- Original --
> From: "software visualization";
> Date: Wed, Dec 29, 2010 06:06 AM
> To: &q
This has probably been asked before but I couldn't find it, so...
Is it possible / advisable / practical to use Lucene as the basis of a live
document search capability? By "live document" I mean a largish document
such as a word processor might be able to handle which is being edited
currently.
