I’d suggest a slightly different approach: use a dual-index model. So you get your rough data into Lucene or Solr indexA.
Then have an index-to-index writer to read from indexA, transform the data, then write to indexB So indexA is “draft”, but your final application runs off of indexB. The nice thing is you can do this as many times as needed. Also, if you use Solr, you can leverage SolrJ and update chains to get the data exactly as you need it. -- Mark Bennett / LucidWorks: Search & Big Data / mark.benn...@lucidworks.com Office: 408-898-4201 / Telecommute: 408-733-0387 / Cell: 408-829-6513 On Apr 4, 2014, at 3:27 AM, spok <s...@milkyweb.de> wrote: > Hi, > > is there a possibility to use (and change) relative document path in lucene > index, so that > index can be generated on system a with documents stored in location a1, and > then > index can be moved i. e. to a cd with documents stored in location cd1, > where > relative position between index and document location has changed? > > Thanks in advance > > spok > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/relative-document-path-in-lucene-index-tp4129096.html > Sent from the Lucene - General mailing list archive at Nabble.com.
