You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Robert Muir (Created) (JIRA)" <ji...@apache.org> on 2011/11/03 14:11:32 UTC

[jira] [Created] (LUCENE-3558) SearcherManager and NRTManager should be in the same package

SearcherManager and NRTManager should be in the same package
------------------------------------------------------------

                 Key: LUCENE-3558
                 URL: https://issues.apache.org/jira/browse/LUCENE-3558
             Project: Lucene - Java
          Issue Type: Improvement
            Reporter: Robert Muir
             Fix For: 3.5, 4.0


I didnt even know NRTManager was still around, because its in the .index package, whereas SearcherManager is in the .search package.

Separately, I don't like that this stuff is so 'hard' with core lucene... would it be so bad if this stuff was added to core?

I suspect a lot of people have issues with this stuff (see http://www.lucidimagination.com/search/document/37964e5f0e5d733b) for example.

Worst case is just that, combine mistakes with trying to manage this stuff with MMap unmapping and total lack of error detection
for searching closed readers (LUCENE-3439) and its a mess.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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


[jira] [Commented] (LUCENE-3558) SearcherManager and NRTManager should be in the same package

Posted by "Michael McCandless (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/LUCENE-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13143268#comment-13143268 ] 

Michael McCandless commented on LUCENE-3558:
--------------------------------------------

I think NRTManager should move to oal.search?

And I think moving to core is a good idea.
                
> SearcherManager and NRTManager should be in the same package
> ------------------------------------------------------------
>
>                 Key: LUCENE-3558
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3558
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Robert Muir
>             Fix For: 3.5, 4.0
>
>
> I didnt even know NRTManager was still around, because its in the .index package, whereas SearcherManager is in the .search package.
> Separately, I don't like that this stuff is so 'hard' with core lucene... would it be so bad if this stuff was added to core?
> I suspect a lot of people have issues with this stuff (see http://www.lucidimagination.com/search/document/37964e5f0e5d733b) for example.
> Worst case is just that, combine mistakes with trying to manage this stuff with MMap unmapping and total lack of error detection
> for searching closed readers (LUCENE-3439) and its a mess.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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


[jira] [Updated] (LUCENE-3558) SearcherManager and NRTManager should be in the same package

Posted by "Simon Willnauer (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/LUCENE-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Simon Willnauer updated LUCENE-3558:
------------------------------------

    Attachment: LUCENE-3558.patch
                LUCENE-3558.sh

next iteration moving NRTCachingDirectory to core too. TestNRTManager depends on it and I think its worth it anyway so lets do it here to while we on it. I will open a follow up to enable this in tests etc.
                
> SearcherManager and NRTManager should be in the same package
> ------------------------------------------------------------
>
>                 Key: LUCENE-3558
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3558
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Robert Muir
>            Assignee: Simon Willnauer
>             Fix For: 3.5, 4.0
>
>         Attachments: LUCENE-3558.patch, LUCENE-3558.patch, LUCENE-3558.patch, LUCENE-3558.patch, LUCENE-3558.sh, LUCENE-3558.sh, LUCENE-3558.sh
>
>
> I didnt even know NRTManager was still around, because its in the .index package, whereas SearcherManager is in the .search package.
> Separately, I don't like that this stuff is so 'hard' with core lucene... would it be so bad if this stuff was added to core?
> I suspect a lot of people have issues with this stuff (see http://www.lucidimagination.com/search/document/37964e5f0e5d733b) for example.
> Worst case is just that, combine mistakes with trying to manage this stuff with MMap unmapping and total lack of error detection
> for searching closed readers (LUCENE-3439) and its a mess.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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


[jira] [Updated] (LUCENE-3558) SearcherManager and NRTManager should be in the same package

Posted by "Simon Willnauer (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/LUCENE-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Simon Willnauer updated LUCENE-3558:
------------------------------------

    Attachment: LUCENE-3558.sh
                LUCENE-3558.patch

here is a patch that moves NRTManager & SearcherManager into core. Both are now in o.a.l.search - To apply the patch run the bash file first or the included svn commands
                
> SearcherManager and NRTManager should be in the same package
> ------------------------------------------------------------
>
>                 Key: LUCENE-3558
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3558
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Robert Muir
>            Assignee: Simon Willnauer
>             Fix For: 3.5, 4.0
>
>         Attachments: LUCENE-3558.patch, LUCENE-3558.sh
>
>
> I didnt even know NRTManager was still around, because its in the .index package, whereas SearcherManager is in the .search package.
> Separately, I don't like that this stuff is so 'hard' with core lucene... would it be so bad if this stuff was added to core?
> I suspect a lot of people have issues with this stuff (see http://www.lucidimagination.com/search/document/37964e5f0e5d733b) for example.
> Worst case is just that, combine mistakes with trying to manage this stuff with MMap unmapping and total lack of error detection
> for searching closed readers (LUCENE-3439) and its a mess.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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


[jira] [Commented] (LUCENE-3558) SearcherManager and NRTManager should be in the same package

Posted by "Mark Miller (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/LUCENE-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147230#comment-13147230 ] 

Mark Miller commented on LUCENE-3558:
-------------------------------------

bq. moving NRTCachingDirectory to core too

+1 - if it's the normal recommendation for NRT it should be part of core.
                
> SearcherManager and NRTManager should be in the same package
> ------------------------------------------------------------
>
>                 Key: LUCENE-3558
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3558
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Robert Muir
>            Assignee: Simon Willnauer
>             Fix For: 3.5, 4.0
>
>         Attachments: LUCENE-3558.patch, LUCENE-3558.patch, LUCENE-3558.patch, LUCENE-3558.patch, LUCENE-3558.sh, LUCENE-3558.sh, LUCENE-3558.sh
>
>
> I didnt even know NRTManager was still around, because its in the .index package, whereas SearcherManager is in the .search package.
> Separately, I don't like that this stuff is so 'hard' with core lucene... would it be so bad if this stuff was added to core?
> I suspect a lot of people have issues with this stuff (see http://www.lucidimagination.com/search/document/37964e5f0e5d733b) for example.
> Worst case is just that, combine mistakes with trying to manage this stuff with MMap unmapping and total lack of error detection
> for searching closed readers (LUCENE-3439) and its a mess.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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


[jira] [Commented] (LUCENE-3558) SearcherManager and NRTManager should be in the same package

Posted by "Michael McCandless (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/LUCENE-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13146946#comment-13146946 ] 

Michael McCandless commented on LUCENE-3558:
--------------------------------------------

Thanks Simon!  Can we also move SearcherLifetimeManager?  And... I think we should move NRTCachingDirectory as well (or we can do this separately...).
                
> SearcherManager and NRTManager should be in the same package
> ------------------------------------------------------------
>
>                 Key: LUCENE-3558
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3558
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Robert Muir
>            Assignee: Simon Willnauer
>             Fix For: 3.5, 4.0
>
>         Attachments: LUCENE-3558.patch, LUCENE-3558.sh
>
>
> I didnt even know NRTManager was still around, because its in the .index package, whereas SearcherManager is in the .search package.
> Separately, I don't like that this stuff is so 'hard' with core lucene... would it be so bad if this stuff was added to core?
> I suspect a lot of people have issues with this stuff (see http://www.lucidimagination.com/search/document/37964e5f0e5d733b) for example.
> Worst case is just that, combine mistakes with trying to manage this stuff with MMap unmapping and total lack of error detection
> for searching closed readers (LUCENE-3439) and its a mess.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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


[jira] [Commented] (LUCENE-3558) SearcherManager and NRTManager should be in the same package

Posted by "Steven Rowe (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/LUCENE-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147063#comment-13147063 ] 

Steven Rowe commented on LUCENE-3558:
-------------------------------------

bq. here is a patch that moves NRTManager & SearcherManager into core. Both are now in o.a.l.search - To apply the patch run the bash file first or the included svn commands

I'm curious why you used {{svn copy}} instead of {{svn move}}?
                
> SearcherManager and NRTManager should be in the same package
> ------------------------------------------------------------
>
>                 Key: LUCENE-3558
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3558
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Robert Muir
>            Assignee: Simon Willnauer
>             Fix For: 3.5, 4.0
>
>         Attachments: LUCENE-3558.patch, LUCENE-3558.sh
>
>
> I didnt even know NRTManager was still around, because its in the .index package, whereas SearcherManager is in the .search package.
> Separately, I don't like that this stuff is so 'hard' with core lucene... would it be so bad if this stuff was added to core?
> I suspect a lot of people have issues with this stuff (see http://www.lucidimagination.com/search/document/37964e5f0e5d733b) for example.
> Worst case is just that, combine mistakes with trying to manage this stuff with MMap unmapping and total lack of error detection
> for searching closed readers (LUCENE-3439) and its a mess.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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


[jira] [Commented] (LUCENE-3558) SearcherManager and NRTManager should be in the same package

Posted by "Simon Willnauer (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/LUCENE-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147084#comment-13147084 ] 

Simon Willnauer commented on LUCENE-3558:
-----------------------------------------

bq. Can we also move SearcherLifetimeManager
I wasn't sure about this one - SeracherManager and NRTManager went through serious refactorings since they where added. But we can still do that if it is in core... I will mover the NRTCachingDirectory in a different issue.

bq. I'm curious why you used svn copy instead of svn move?

I used svn cp since the patch removes the files and otherwise some systems have problems if the files don't exist anymore. I used svn mv to create the patch actually :)
                
> SearcherManager and NRTManager should be in the same package
> ------------------------------------------------------------
>
>                 Key: LUCENE-3558
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3558
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Robert Muir
>            Assignee: Simon Willnauer
>             Fix For: 3.5, 4.0
>
>         Attachments: LUCENE-3558.patch, LUCENE-3558.sh
>
>
> I didnt even know NRTManager was still around, because its in the .index package, whereas SearcherManager is in the .search package.
> Separately, I don't like that this stuff is so 'hard' with core lucene... would it be so bad if this stuff was added to core?
> I suspect a lot of people have issues with this stuff (see http://www.lucidimagination.com/search/document/37964e5f0e5d733b) for example.
> Worst case is just that, combine mistakes with trying to manage this stuff with MMap unmapping and total lack of error detection
> for searching closed readers (LUCENE-3439) and its a mess.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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


[jira] [Updated] (LUCENE-3558) SearcherManager and NRTManager should be in the same package

Posted by "Simon Willnauer (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/LUCENE-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Simon Willnauer updated LUCENE-3558:
------------------------------------

    Attachment: LUCENE-3558.sh
                LUCENE-3558.patch

new patch moving SearcherLifetimeManager into core and adds additional @lucene.experimental to NRTManagerReopenThread & SearcherLifetimeManager  

I think this is ready.
                
> SearcherManager and NRTManager should be in the same package
> ------------------------------------------------------------
>
>                 Key: LUCENE-3558
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3558
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Robert Muir
>            Assignee: Simon Willnauer
>             Fix For: 3.5, 4.0
>
>         Attachments: LUCENE-3558.patch, LUCENE-3558.patch, LUCENE-3558.sh, LUCENE-3558.sh
>
>
> I didnt even know NRTManager was still around, because its in the .index package, whereas SearcherManager is in the .search package.
> Separately, I don't like that this stuff is so 'hard' with core lucene... would it be so bad if this stuff was added to core?
> I suspect a lot of people have issues with this stuff (see http://www.lucidimagination.com/search/document/37964e5f0e5d733b) for example.
> Worst case is just that, combine mistakes with trying to manage this stuff with MMap unmapping and total lack of error detection
> for searching closed readers (LUCENE-3439) and its a mess.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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


[jira] [Updated] (LUCENE-3558) SearcherManager and NRTManager should be in the same package

Posted by "Simon Willnauer (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/LUCENE-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Simon Willnauer updated LUCENE-3558:
------------------------------------

    Attachment: LUCENE-3558.patch

new patch containing CHANGES entries
                
> SearcherManager and NRTManager should be in the same package
> ------------------------------------------------------------
>
>                 Key: LUCENE-3558
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3558
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Robert Muir
>            Assignee: Simon Willnauer
>             Fix For: 3.5, 4.0
>
>         Attachments: LUCENE-3558.patch, LUCENE-3558.patch, LUCENE-3558.patch, LUCENE-3558.sh, LUCENE-3558.sh
>
>
> I didnt even know NRTManager was still around, because its in the .index package, whereas SearcherManager is in the .search package.
> Separately, I don't like that this stuff is so 'hard' with core lucene... would it be so bad if this stuff was added to core?
> I suspect a lot of people have issues with this stuff (see http://www.lucidimagination.com/search/document/37964e5f0e5d733b) for example.
> Worst case is just that, combine mistakes with trying to manage this stuff with MMap unmapping and total lack of error detection
> for searching closed readers (LUCENE-3439) and its a mess.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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


[jira] [Assigned] (LUCENE-3558) SearcherManager and NRTManager should be in the same package

Posted by "Simon Willnauer (Assigned) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/LUCENE-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Simon Willnauer reassigned LUCENE-3558:
---------------------------------------

    Assignee: Simon Willnauer
    
> SearcherManager and NRTManager should be in the same package
> ------------------------------------------------------------
>
>                 Key: LUCENE-3558
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3558
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Robert Muir
>            Assignee: Simon Willnauer
>             Fix For: 3.5, 4.0
>
>
> I didnt even know NRTManager was still around, because its in the .index package, whereas SearcherManager is in the .search package.
> Separately, I don't like that this stuff is so 'hard' with core lucene... would it be so bad if this stuff was added to core?
> I suspect a lot of people have issues with this stuff (see http://www.lucidimagination.com/search/document/37964e5f0e5d733b) for example.
> Worst case is just that, combine mistakes with trying to manage this stuff with MMap unmapping and total lack of error detection
> for searching closed readers (LUCENE-3439) and its a mess.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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


[jira] [Commented] (LUCENE-3558) SearcherManager and NRTManager should be in the same package

Posted by "Michael McCandless (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/LUCENE-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147157#comment-13147157 ] 

Michael McCandless commented on LUCENE-3558:
--------------------------------------------

OK we can leave SearcherLifetimeMGR in contrib for now...
                
> SearcherManager and NRTManager should be in the same package
> ------------------------------------------------------------
>
>                 Key: LUCENE-3558
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3558
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Robert Muir
>            Assignee: Simon Willnauer
>             Fix For: 3.5, 4.0
>
>         Attachments: LUCENE-3558.patch, LUCENE-3558.sh
>
>
> I didnt even know NRTManager was still around, because its in the .index package, whereas SearcherManager is in the .search package.
> Separately, I don't like that this stuff is so 'hard' with core lucene... would it be so bad if this stuff was added to core?
> I suspect a lot of people have issues with this stuff (see http://www.lucidimagination.com/search/document/37964e5f0e5d733b) for example.
> Worst case is just that, combine mistakes with trying to manage this stuff with MMap unmapping and total lack of error detection
> for searching closed readers (LUCENE-3439) and its a mess.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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


[jira] [Resolved] (LUCENE-3558) SearcherManager and NRTManager should be in the same package

Posted by "Simon Willnauer (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/LUCENE-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Simon Willnauer resolved LUCENE-3558.
-------------------------------------

       Resolution: Fixed
    Lucene Fields: New,Patch Available  (was: New)

committed to trunk and backported to 3.x
                
> SearcherManager and NRTManager should be in the same package
> ------------------------------------------------------------
>
>                 Key: LUCENE-3558
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3558
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Robert Muir
>            Assignee: Simon Willnauer
>             Fix For: 3.5, 4.0
>
>         Attachments: LUCENE-3558.patch, LUCENE-3558.patch, LUCENE-3558.patch, LUCENE-3558.patch, LUCENE-3558.sh, LUCENE-3558.sh, LUCENE-3558.sh
>
>
> I didnt even know NRTManager was still around, because its in the .index package, whereas SearcherManager is in the .search package.
> Separately, I don't like that this stuff is so 'hard' with core lucene... would it be so bad if this stuff was added to core?
> I suspect a lot of people have issues with this stuff (see http://www.lucidimagination.com/search/document/37964e5f0e5d733b) for example.
> Worst case is just that, combine mistakes with trying to manage this stuff with MMap unmapping and total lack of error detection
> for searching closed readers (LUCENE-3439) and its a mess.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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