You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Michael McCandless (JIRA)" <ji...@apache.org> on 2013/01/04 01:36:13 UTC

[jira] [Created] (LUCENE-4658) Per-segment tracking of external/side-car data

Michael McCandless created LUCENE-4658:
------------------------------------------

             Summary: Per-segment tracking of external/side-car data
                 Key: LUCENE-4658
                 URL: https://issues.apache.org/jira/browse/LUCENE-4658
             Project: Lucene - Core
          Issue Type: Improvement
            Reporter: Michael McCandless


Spinoff from David's idea on LUCENE-4258
(https://issues.apache.org/jira/browse/LUCENE-4258?focusedCommentId=13534352&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13534352 )

I made a prototype patch that allows custom per-segment "side-car
data".  It adds an abstract ExternalSegmentData class.  The idea is
the app implements this, and IndexWriter will pass each Document
through to it, and call on it to do flushing/merging.  I added a
setter to IndexWriterConfig to enable it, but I think this would
really belong in Codec ...

I haven't tackled the read-side yet, though this is already usable
without that (ie, the app can just open its own files, read them,
etc.).

The random test case passes.

I think for example this might make it easier for Solr/ElasticSearch
to implement things like ExternalFileField.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org