On Sat, Aug 6, 2011 at 4:17 PM, eks dev <eks...@yahoo.co.uk> wrote:
> Thanks Yonik,
> assuming I am not going to index ID , than only an option 4. remains so far.
> I have no other ideas, and Log* merge policy would mean all 4 Indexing magic
> went to nothing :)
> Colud then the following do the job?
> clone DefaultIndexWriterProvider into my codebase (ugly, keep in sync , but
> doable)
> make it provide
> EnhancedSolrIndexWriter extends SolrIndexWriter
> @Override
> commit(...){
> super.commit(Map<String, String> Core.getUserMap());
> }
> the same with close(...)
>
> If yes, Is this feature something solr could use? Map<String, String>
> userParams somewhere in Core that gets committed with whatever it has at
> commit time. I could wrap up a patch by modifying SolrIndexWriter directly
> then?
Yes, this would be useful.
If there is a map to be maintained, I guess it would live in the update handler.
The hard part here is thinking about good APIs to specify what goes in
it I think.
Can you open an issue for this?
-Yonik
http://www.lucidimagination.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
