I now have added a first version to the cvs HEAD.

To use it simply add the following to your store defintion:
<propertiesindexer
      classname="org.apache.slide.index.lucene.LucenePropertiesIndexer">
  <parameter name="indexpath">index</parameter>
</propertiesindexer>

Currenty I observed following indexing overhead (add 2500 (small)files and collection):

  index size ~400Kbyte

  without indexing   ~7min
  with indexing     ~11min

  and on a faster machine

  without indexing  ~3.5min
  with indexing     ~5.5min

Regards,
Stefan

Stefan L�tzkendorf wrote:
Hi all,

I have a first implmentation of a propertiesindexer base on lucene.

Operators currenlty supported are:
   eq, lt, lte, gt, gte, is-collection, is-principal, and, or.
Data types supported:
   String, Date, Int (Text will follow).

It is transaction aware in a limited sense: the index is updeted
only if a transaction is commited.

It will be configurable for user defined properties (define data type
and anylyzer).

I know that Darren is currently working on this stuff to so I'm
thinking what to do.
I would be glad to add this stuff as a new package in the stores section
"org.apache.slide.index.lucene". An other option would be to add it to
the proposals section (which is not my favorite (:-)).

What do you think?
Regards, Stefan





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to