[
https://issues.apache.org/jira/browse/SOLR-14819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189822#comment-17189822
]
Thomas DuBuisson commented on SOLR-14819:
-----------------------------------------
[~broustant] yes there were other issues detected in Lucene-solr. Muse
(running Infer, FSB, Error Prone) is better used to comment on pull requests,
giving issues while the responsible dev has context. This has the benefit of
letting you look at any false positive only once and not every time you look at
a big bug list.
That intro aside, the list I have for lucene-solr is here:
[https://console.muse.dev/result/TomMD/lucene-solr/01EH5WXS6C1RH1NFYHP6ATXTZ9?tab=results]
We could install Muse (github app but free as in beer) on the lucene-solr repo
and just get the issues commented (ex: [https://github.com/TomMD/shiro/pull/2)]
if that's of interest.
> SOLR has linear log operations that could trivially be linear
> -------------------------------------------------------------
>
> Key: SOLR-14819
> URL: https://issues.apache.org/jira/browse/SOLR-14819
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Thomas DuBuisson
> Priority: Trivial
> Time Spent: 1h
> Remaining Estimate: 0h
>
> The SOLR code has a few linear log operations that could be linear. That is,
> operations of
>
> ```
> for(key in hashmap) doThing(hashmap.get(key));
>
> ```
>
> vs just `for(value in hashmap) doThing(value)`
>
> I have a PR incoming on GitHub to fix a couple of these issue as [found by
> Infer on
> Muse|https://console.muse.dev/result/TomMD/lucene-solr/01EH5WXS6C1RH1NFYHP6ATXTZ9?search=JsonSchemaValidator&tab=results].
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
