I have not had the time to look into it too closely. Looks like one
would need to remove the context use of the existing index usecase (use
of page envelope to get pub and id) and make a usecase that iterates
through all the documents and indexes.
I would like to make a solr module. Eric Hatcher (lucene guru) works
down the hall from me and was showing some very cool solr functionality
to me last week. Using a separate indexing/searching server would help
with your problems I think.
--Doug
Andrew Golightly wrote:
Michael Wechner wrote:
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.
agreed, whereas something like this already exists within Lenya 1.2.x
But we should also make the location of the index configurable with
local config files. Maybe it's already possible or easy to fix, but I
have not found time yet to check.
Anyone made any progress on this idea? Does it already exist in some way
and I've just missed it?
Andrew
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
