gautamworah96 opened a new pull request #776:
URL: https://github.com/apache/lucene/pull/776


   I discovered this hanging zip file in the main branch while working on 
trying to directly replace actual index files 
([LUCENE-10482](https://issues.apache.org/jira/browse/LUCENE-10482)).
   
   I suspect that we had replaced this file in the branch_9x branch (with a 
newer `old` index and some updates to the TestBackwardsCompatibility class) but 
forgot to remove it from the main branch..
   
   Also, according our usual back-compat policy, Lucene 9 should definitely 
support 8.11 indexes but that restriction does not apply to Lucene 10 (`main` 
branch).
   
   We had initially introduced this file and a new test class file 
facet/taxonomy/directory/TestBackwardsCompatibility.java in 
[LUCENE-9450](https://issues.apache.org/jira/browse/LUCENE-9450)
   
   # Checklist
   
   Please review the following and check all that apply:
   
   - [x] I have reviewed the guidelines for [How to 
Contribute](https://wiki.apache.org/lucene/HowToContribute) and my code 
conforms to the standards described there to the best of my ability.
   - [x] I have created a Jira issue and added the issue ID to my pull request 
title.
   - [x] I have given Lucene maintainers 
[access](https://help.github.com/en/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork)
 to contribute to my PR branch. (optional but recommended)
   - [x] I have developed this patch against the `main` branch.
   - [x] I have run `./gradlew check`.
   - [ ] I have added tests for my changes.
   


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to