Would it be possible to allow an operator to choose which version of Lucene to use? Such that if they are prepared for the issues you describe, they could still go ahead and upgrade to 7.10. Or are there breaking API changes which would make that hard/impossible to accommodate in our code base?
--Jens From: nabarun nag <n...@apache.org> Date: Monday, September 27, 2021 at 11:49 AM To: dev@geode.apache.org <dev@geode.apache.org> Subject: [DISCUSS] Upgrading to Lucene 7.1.0 Hi dev team, Recently, a commit was pushed to develop which upgraded the Lucene version used in Apache Geode to 7.1.0. These new Lucene indexes are not compatible with the previous versions hence it breaks the rolling upgrade contract. We are no longer able to execute Lucene queries when there are severs of mixed versions in the cluster. One solution that was provided was to not allow Lucene queries to be executed when there are mixed versions of servers present in the cluster. After a discussion, it was put forward that this was not an optimal user experience. Also, that this change of default behavior was not discussed in the dev list. Alternative solutions that were put forward were that Geode allowed the user to pick the version of Lucene to be used. Another that since this is a major upgrade to Lucene with some breaking API changes, should we sync this upgrade with the release of Apache Geode 2.0 We would love to hear your thoughts or alternative solutions to this issue. Regards Nabarun.
