Mailing-List: contact couchdb-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: couchdb-user@incubator.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
From: =?iso-8859-1?q?S=F8ren_Hilmer?= <sh@widetrail.dk>
Organization: wideTrail
To: couchdb-user@incubator.apache.org
Subject: Working on Lucene
Date: Fri, 21 Mar 2008 16:02:55 +0100
User-Agent: KMail/1.9.5
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200803211602.56058.sh@widetrail.dk>

Hi,

I have hacked a little on the LuceneIndexer, and fixed some bugs to get it=
=20
compiling and running, though I also had to patch couchdb4j (patch was from=
=20
the couchdb4j issues page). Also found that the readme needs some tuning,=20
LuceneIndexer in couch.ini is now FullTextSearchQueryServer, right?

But all is still not well, here is a few of questions that I hope someone c=
an=20
supply answers to:

1) couchdb4j uses "_all_docs_by_update_seq" to get a specific revision of a=
=20
document. The trunk version of couchdb does not support this. Has it been=20
discontinued in favor of "_all_docs_by_seq" ?

2) What was actually the intention of the LuceneIndexer, I guess that it=20
should traverse all the databases and all the documents within these and=20
store the result in the database "couchdbfulltext", right? Some work to=20
achieve this seams necessary.

3)  When a database has a changed document, the indexer should re-index it,=
=20
right?

4) I have still not looked at the LuceneSearcher, how is that hooked into=20
couchdb?

I hope to get it working and supply a patch when it does, hopefully I am no=
t=20
treading on anyones toes here.

=2D-S=F8ren
=2D-=20
S=F8ren Hilmer, M.Sc., M.Crypt.
wideTrail			Phone:	+45 25481225
Pilev=E6nget 41		Email:	sh@widetrail.dk
DK-8961  Alling=E5bro	Web:	www.widetrail.dk