Doug Chestnut wrote:
Andrew Golightly wrote:
Hey everyone,
As you all probably know lucene saves it's indexes in the work
directory. We store our publication in an svn repo, and I am
wondering whether it is wise to save the indexing too.
Advantages:
- If the publication is checked out elsewhere, searching is
immediately available.
Disadvantages:
- If people are working on their own local copies, then the indexing
directory constantly conflicts within svn. And that includes binary
files like: work/lucene/index/authoring/index/segments So resolution
is near impossible.
From what I understand, lenya 1.4 indexes it's pages when
submit/publish is called in the workflow. So if a site was checked
out elsewhere and the indexing was not saved, then the whole site
would have to be manually re-published. Correct?
Well, the pages that were published elsewhere would need to be
republished I guess. We really need a reindex-publication usecase for
this.
Anyone thought more about this? I'm constantly losing my my indexes
everytime I do a "./build.sh clean" If someone is close to releasing a
script that re-indexes the entire publication, please let me know!
thank you :)
Andrew
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
