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 2014/05/11 00:06:48 UTC

[jira] [Created] (LUCENE-5657) Can/should we open up thread to thread state allocator in IndexWriter?

Michael McCandless created LUCENE-5657:
------------------------------------------

             Summary: Can/should we open up thread to thread state allocator in IndexWriter?
                 Key: LUCENE-5657
                 URL: https://issues.apache.org/jira/browse/LUCENE-5657
             Project: Lucene - Core
          Issue Type: Improvement
            Reporter: Michael McCandless


In LUCENE-5644 we removed the ability to provide a custom DocumentsWriterPerThreadPool, when we switched to a simpler LIFO scheduler ... I think this (a custom thread pool) is a super-expert thing to do... should we open it up again?

If so I think we need better testing around it; I added two separate tests but neither would fail either the old or the new thread pool ...



--
This message was sent by Atlassian JIRA
(v6.2#6252)

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