[
https://issues.apache.org/jira/browse/LUCENE-5757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14030550#comment-14030550
]
Robert Muir commented on LUCENE-5757:
-------------------------------------
But then we'd have the same class name in both places.
I think the reflection part to be moved to tests should have a separate class
name than the other stuff that we are keeping in lucene/core (which is mostly
constants and simple math).
> Move RAMUsageEstimator "reflector" to test-framework
> ----------------------------------------------------
>
> Key: LUCENE-5757
> URL: https://issues.apache.org/jira/browse/LUCENE-5757
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Robert Muir
>
> This method is "banned" already because it can crawl slowly across large
> object graphs.
> I think it should be in the test framework. It needs enhancements for testing
> such as some way to filter what is crawled.
> Currently lots of code in lucene tries to provide accounting information but
> its all totally untested. We need to fix the test situation or remove
> Accountable and such methods completely.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
