[
https://issues.apache.org/jira/browse/LUCENE-9928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir resolved LUCENE-9928.
-
Fix Version/s: main (9.0)
Resolution: Fixed
> speed up analysis/icu regeneration
> --
rmuir merged pull request #82:
URL: https://github.com/apache/lucene/pull/82
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contac
[
https://issues.apache.org/jira/browse/LUCENE-9928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17327961#comment-17327961
]
ASF subversion and git services commented on LUCENE-9928:
-
Commi
neoremind commented on pull request #91:
URL: https://github.com/apache/lucene/pull/91#issuecomment-824891023
I use `TimSort` instead of `InPlaceMergeSorter`, expect it to be faster, but
it turns out to be slower. @jpountz would you check my latest commit to see if
I implement Tim Sort cor
cpoerschke opened a new pull request #2482:
URL: https://github.com/apache/lucene-solr/pull/2482
I think a `solr/CHANGES.txt` entry for Solr 8.x is not warranted given the
specialised use of the class but it would seem nice to provide some indication
to anyone using it w.r.t. the class bei
jpountz commented on pull request #91:
URL: https://github.com/apache/lucene/pull/91#issuecomment-825004979
Oh, this is disappointing, maybe the arrays are too small for TimSorter to
actually perform better than InPlaceMergeSorter.
I'd be keen to proceed with the change that always p
dsmiley commented on a change in pull request #2482:
URL: https://github.com/apache/lucene-solr/pull/2482#discussion_r618630451
##
File path: solr/core/src/java/org/apache/solr/update/SolrIndexConfig.java
##
@@ -303,6 +304,10 @@ private MergePolicy buildMergePolicy(SolrResource
MichelLiu commented on pull request #92:
URL: https://github.com/apache/lucene/pull/92#issuecomment-825347763
I had a problem with the tiered merge policy. As I continuously updated a
batch of data over time and time, then I got a lot of segments with 4.9G which
segDelPct already greater t
