You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shai Erera (JIRA)" <ji...@apache.org> on 2012/12/11 14:57:21 UTC

[jira] [Resolved] (LUCENE-4615) Remove Int/FloatArrayAllocator from facet module?

     [ https://issues.apache.org/jira/browse/LUCENE-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shai Erera resolved LUCENE-4615.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 5.0
                   4.1
         Assignee: Shai Erera
    Lucene Fields: New,Patch Available  (was: New)

Thanks for the review Mike. Committed to trunk and 4x.
                
> Remove Int/FloatArrayAllocator from facet module?
> -------------------------------------------------
>
>                 Key: LUCENE-4615
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4615
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Michael McCandless
>            Assignee: Shai Erera
>             Fix For: 4.1, 5.0
>
>         Attachments: LUCENE-4615.patch
>
>
> Spinoff from LUCENE-4600.
> It makes me nervous to have allocation tied to our public APIs ... and the ability for Int/FloatArrayAllocator to hold onto N arrays indefinitely makes me even more nervous.  I think we should just trust java/GC to do their job here and free the storage as soon as faceting is done.

--
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