You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@lucene.apache.org by "Adrien Grand (Jira)" <ji...@apache.org> on 2022/04/19 13:39:00 UTC

[jira] [Resolved] (LUCENE-10506) ProfilerCollector to support customizing how name is derived

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

Adrien Grand resolved LUCENE-10506.
-----------------------------------
    Fix Version/s: 9.2
       Resolution: Fixed

> ProfilerCollector to support customizing how name is derived
> ------------------------------------------------------------
>
>                 Key: LUCENE-10506
>                 URL: https://issues.apache.org/jira/browse/LUCENE-10506
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: modules/sandbox
>            Reporter: Luca Cavanna
>            Priority: Minor
>             Fix For: 9.2
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> ProfilerCollector (part of the sandbox) has a private method called deriveCollectorName that extracts the class simple name from the provided collector and sets it as the name of the collector which becomes part of the profile results later.
> While the default behaviour is reasonable, there are cases where it would be useful to extend this logic, and perhaps not use class names, or enhance that with more context that the collectors could provide. This could be achieved by making the deriveCollectorName method protected.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

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