Better detect vector module in non-default setups (e.g., custom module layers) #12677
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.
Hi @ChrisHegarty,
while working on #12667 and #12676 I noticed that the code which detects if vector module is enabled and readable has some limitations because it only looks into the boot layer.
If you create your own module layer with Lucene and the incubator module, Lucene does not detect it correctly. This code uses the
ModuleLayerof the Lucene module and usesfindModuleto check if it is there (we do this in other Lucene code in the same way, e.g. to detectsun.misc.Unsafe,...). Only in case of unnamed module (thengetLayer()returns null), then the code uses boot layer.In addition to #12676 it also only calls
thisModule.addReads(vectorModule)when it actually wants to enable it. For the pure check (e.g., java 17) ist does not add a read.