docs(15.9): engine-fused hybrid search pages up to pagination_depth (default 1000) - #558
Merged
Merged
Conversation
…default 1000) A search fused in the search engine no longer hands pages past rank.fusion.pagination_depth to Fess-side fusion. It pages through at most min(rank.fusion.pagination_depth, indexer.max.result.window.size) results, and a page that starts beyond that is refused like a page past index.max_result_window. - rank-fusion.rst: default pagination_depth 1000; drop the "page past pagination_depth is fused by Fess" case; describe the paging limit, the lower-bound hit count at or above the depth, the empty page past the last fused hit, and the latency cost of a larger depth; the knn k of a fused request is content_chunker.search.knn.k; reducing the depth is listed under slow search - search-semantic.rst: knn.k is no longer raised to pagination_depth; deep pages with engine-side fusion stop at pagination_depth - properties.rst / properties.po: regenerated rank.fusion.pagination_depth row (default and description) All seven languages of the development tree.
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.
Summary
Document how engine-side rank fusion pages in Fess 15.9 after codelibs/fess#3506 (and #3505).
A search fused in the search engine (
rank.fusion.engine.enabled=true, and the request can be fused) used to hand any page pastrank.fusion.pagination_depthto Fess-side fusion, which by default meant keyword-only results. With #3506 it pages through at mostmin(rank.fusion.pagination_depth, indexer.max.result.window.size)results and stops there, the same way any other search stops atindex.max_result_window. The default depth goes from 200 to 1000, and the semantic branch's knnkiscontent_chunker.search.knn.kinstead ofmax(knn.k, pagination_depth).Changes
All seven languages (ja, en, de, es, fr, ko, zh-cn), development tree (15.9) only.
config/rank-fusion.rstrank.fusion.pagination_depthdefault1000; the value sent never exceedsindexer.max.result.window.size.pagination_depthis fused by Fess" case from the list of searches not fused in the engine.pagination_depth(page count, next page and page numbers stop there; a page starting beyond it gets the same error as a page beyondindex.max_result_window; a page after the last fused hit but within the limit is empty; non-fused searches page as before); the hit count is a lower bound (GREATER_THAN_OR_EQUAL_TO) at or above the depth; a larger depth slows every fused search.kof a fused request iscontent_chunker.search.knn.k.pagination_depth; "Slow Search" lists reducingpagination_depthfor engine-side fusion.config/search-semantic.rstcontent_chunker.search.knn.k: enlarged for deep paging only when Fess performs the fusion.pagination_depth(default1000).config/properties.rst/config/properties.po: regenerated withtools/update_properties_doc.shagainst the #3506 branch. Only therank.fusion.pagination_depthrow (default and description) is taken; other differences between the generated pages and the currentfess_config.propertiesare left for a separate update. The catalogues carry no translations yet, so only the msgid changes.Verification
python3 tools/gen_properties_doc.py --check: the 7 properties pages agreepython3 -m unittest discover -s tools -p 'test_*.py': 79 tests OKpython3 tools/check_headings.pyon the 15.8 and 15.9 trees: no mismatches (no headings changed)config/directory before and after the change: no new warnings in the changed files, and no unrendered inline markup in the outputDependency
This documents codelibs/fess#3506 (milestone 15.9.0), which is still open. Merge it after that PR.