This is an automated email from the ASF dual-hosted git repository.

dsmiley pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/solr-site.git


The following commit(s) were added to refs/heads/main by this push:
     new 23a2797a3 Add comparison harness link to Solr/Lucene migration post 
(#185)
23a2797a3 is described below

commit 23a2797a39aa39d94bd4c39ed3103fbb1d1a04d1
Author: parveensaini <[email protected]>
AuthorDate: Sun May 24 14:03:03 2026 -0700

    Add comparison harness link to Solr/Lucene migration post (#185)
---
 content/pages/blogposts/2026-05-02-solr-lucene-migration-correctness.md | 1 +
 1 file changed, 1 insertion(+)

diff --git 
a/content/pages/blogposts/2026-05-02-solr-lucene-migration-correctness.md 
b/content/pages/blogposts/2026-05-02-solr-lucene-migration-correctness.md
index a05f01080..48620849e 100644
--- a/content/pages/blogposts/2026-05-02-solr-lucene-migration-correctness.md
+++ b/content/pages/blogposts/2026-05-02-solr-lucene-migration-correctness.md
@@ -10,3 +10,4 @@ save_as: blogposts/solr-lucene-migration-correctness.html
 Major Solr/Lucene upgrades can introduce subtle ranking behavior changes even 
when functional tests continue to pass. This article discusses a practical 
side-by-side validation approach for detecting candidate-set changes, rank 
deltas, score distribution drift, and latency differences during migration 
testing.
 
 The complete post can be read here: [Validating Ranking Correctness During 
Solr/Lucene 
Migrations](https://dzone.com/articles/solr5-to-solr8-migration-ads-system).
+A companion comparison harness and detailed checklist are available at 
[solr-lucene-migration-correctness](https://github.com/parveensaini/solr-lucene-migration-correctness).

Reply via email to