This is an automated email from the ASF dual-hosted git repository.
rnewson pushed a change to branch lucene-10
in repository https://gitbox.apache.org/repos/asf/couchdb.git
omit f43617be2 Move up to match Lucene source compatibility
omit 348c2ecff document nouveau handling of lucene 9 & 10
omit ec6eafb0c fix formatting error in previous PR
omit 8b325a5cc add scanner to upgrade nouveau indexes
omit 1610b44ca insert lucene version in new design documents if missing
omit 5f9e63238 nouveau welcome message for version negotiation
omit 489d65f65 support legacy indexes but prevent new ones
add 26a70f832 support legacy indexes but prevent new ones
add 1f0e6888d nouveau welcome message for version negotiation
add 50a7e5892 insert lucene version in new design documents if missing
add 0833ca59e add scanner to upgrade nouveau indexes
add 00e8c24c8 fix formatting error in previous PR
add a00d4ffe9 document nouveau handling of lucene 9 & 10
add b81d059bd Move up to match Lucene source compatibility
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (f43617be2)
\
N -- N -- N refs/heads/lucene-10 (b81d059bd)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
.../src/main/java/org/apache/couchdb/nouveau/api/IndexDefinition.java | 2 ++
1 file changed, 2 insertions(+)
