Hi, We have modified the Lucene plugin slightly to allow for *document* based indexing and will share that work as soon as it has been tested and made a more generic/reusable.
This change allows a Lucene documents to be created for any/all ORecord values, via template, and is quite useful when building enterprise search . I need input on current limitations before we continue: - We created the field "all" as a meta field - It currently changes values when the vertex is saved to trigger index update - A better way would be to allow for a proper meta-field (containing "@rid+@version" value to trigger updates on any change) - Specifying the "all" field in a query triggers index use (where all LUCENE '<search-terms>') - Any ideas on how to improve this implementation? - The template is passed to the indexer via metadata - currently quite crude (would benefit from assistance from someone more OrientDB savvy than me) - any other way? - We would very much like to move to Lucene 5.2 - any plans of upgrading from 4.7? Anyways; this is our first potential contribution to OrientDB and I would very much like to connect to someone @OrientDB that can assist with details and changes required to make it easily re-usable/proper. Best regards, -Stefan -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
