Repository navigation
Conversation
nvzm123
force-pushed
the
zackm_pylucene_runtime_integration
branch
from
October 6, 2026 21:40
2cf654f to
1f6460d
Compare
nvzm123
force-pushed
the
zackm_lucene_benchmark_backend
branch
from
October 6, 2026 21:40
38bf707 to
4f7d192
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
Draft 3 of 5 in the Lucene backend split. It depends on the generic plugin
contract and PyLucene runtime layers below it.
Summary
This layer deliberately does not register public package entry points yet, so
its behavior can be reviewed and unit-tested before package activation.
Validation
152 passed;
git diff --check: passed.