aboutsummaryrefslogtreecommitdiffstats
path: root/container-search/src/test/java/com/yahoo/search
Commit message (Collapse)AuthorAgeFilesLines
* Handle implicit/explicit set languages for significance searcherMariusArhaug28 hours1-31/+137
|
* isNExplicit => nIsExplicit and update ABI.Henning Baldersheim6 days1-2/+2
|
* If hits has been set higher than default weakand targethits, adjust all ↵Henning Baldersheim6 days1-9/+40
| | | | weakand with not explicit set heap size up to hits.
* Merge pull request #31654 from ↵Marius Arhaug7 days2-1/+50
|\ | | | | | | | | vespa-engine/marius/add-significance-rank-override Add significance rank override
| * Fix CR comments from GeirMariusArhaug7 days1-2/+3
| |
| * Add significance rank overrideMariusArhaug7 days2-3/+51
| |
* | assertTrue => assertInstanceOfHenning Baldersheim10 days1-6/+6
| |
* | No opportunism for single term queries. They are already optimal in the backend.Henning Baldersheim2024-06-131-1/+9
| |
* | Support setting 'select' in a query profileJon Bratseth2024-06-123-2/+19
|/
* Add rendering of hits (and trace and timing etc) in llm renderingLester Solbakken2024-06-101-1/+1
|
* Remove hyphen in second phase rank score drop limit property name.Tor Egge2024-06-071-1/+1
|
* Add ranking.secondPhase.rankScoreDropLimit query parameter.Tor Egge2024-06-061-0/+10
|
* Remove unnecessary assertionLester Solbakken2024-06-011-1/+1
|
* Add copyrightHenning Baldersheim2024-05-301-0/+2
|
* - Add an opportunistic weakand searcher that will first replace the weakAnd ↵Henning Baldersheim2024-05-302-5/+44
| | | | | | with AND, and fall back to original plan if not enough hits. - Place it after the WeakAndReplacementSearch that transforms OR => WeakAND.
* Merge pull request #31194 from vespa-engine/bratseth/stemming-traceJon Bratseth2024-05-161-2/+3
|\ | | | | Trace no stemming due to language=UNKNOWN
| * Update ↵Jon Bratseth2024-05-161-1/+0
| | | | | | | | container-search/src/test/java/com/yahoo/search/yql/YqlParserTestCase.java
| * Merge branch 'master' into bratseth/stemming-traceJon Bratseth2024-05-135-20/+63
| |\
| * | Trace no stemming due to language=UNKNOWNJon Bratseth2024-05-121-2/+4
| | |
* | | Merge pull request #31140 from ↵Marius Arhaug2024-05-154-5/+75
|\ \ \ | |_|/ |/| | | | | | | | vespa-engine/marius/add-more-significance-searcher-tests Add additional significance searcher tests
| * | Update corpus size value in test to match updated docv2.json fileMariusArhaug2024-05-151-1/+1
| | |
| * | Add additional significance searcher testsMariusArhaug2024-05-074-4/+74
| | |
* | | Update expected exception message.Henning Baldersheim2024-05-131-1/+1
|/ /
* | Revert "Update jackson2.vespa.version to v2.17.0"Henning Baldersheim2024-05-061-1/+1
| |
* | Merge pull request #30751 from vespa-engine/renovate/jackson2.vespa.versionHenning Baldersheim2024-05-061-1/+1
|\ \ | | | | | | Update jackson2.vespa.version to v2.17.0
| * | Update expected error positionHenning Baldersheim2024-05-061-1/+1
| |/
* | Merge pull request #31113 from vespa-engine/bratseth/group-rotationHenning Baldersheim2024-05-062-6/+17
|\ \ | | | | | | Require a higher bar to take groups in rotation
| * | Require a higher bar to take groups in rotationJon Bratseth2024-05-042-6/+17
| |/
* | Populate significance properties from configBjørn Christian Seime2024-05-061-1/+3
| |
* | Fail with error if the significance setup for the selected schemas are ↵Bjørn Christian Seime2024-05-061-0/+32
| | | | | | | | conflicting
* | Configure signficance searcher through `SchemaInfo`Bjørn Christian Seime2024-05-061-12/+10
|/
* Add significance rank profileMariusArhaug2024-04-301-1/+17
|
* Fix CR commentsMariusArhaug2024-04-302-11/+17
|
* Merge pull request #30871 from vespa-engine/marius/add-significance-searcherMarius Arhaug2024-04-242-0/+167
|\ | | | | Add significance searcher
| * fix cr failuresMariusArhaug2024-04-161-8/+42
| |
| * add author tagsMariusArhaug2024-04-101-0/+6
| |
| * add testsMariusArhaug2024-04-102-0/+127
| |
* | Merge pull request #30976 from ↵Henning Baldersheim2024-04-223-21/+29
|\ \ | | | | | | | | | | | | vespa-engine/vekterli/wire-fuzzy-prefix-match-through-query-stack Wire fuzzy prefix matching support through the query stack
| * | Wire fuzzy prefix matching support through the query stackTor Brede Vekterli2024-04-193-21/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Adds `prefix:[true|false]` annotation support to the `fuzzy` query operator in the YQL and JSON query languages. Fuzzy prefix matching semantics are wired through to the matcher implementations for both indexed and streaming search. Example usage: {maxEditDistance:1,prefix:true}fuzzy("foo") Will match `foo`, `foobar`, `foxtrot`, `zookeeper` and so on. It can be combined with the existing prefix locking feature: {maxEditDistance:1,prefixLength:2,prefix:true}fuzzy("foo") Which will match `foo`, `foobar`, `foxtrot` etc, but _not_ `zookeeper` since the locked prefix (`fo`) does not match. Due to the complexities involved with extending the legacy binary query stack representation, signalling prefix matching for the fuzzy term is done by pragmatically adding a new, generic "prefix matching" term-level flag. This is currently ignored for everything except fuzzy query items. Modernizing the query stack format to make it more extensible (i.e. move encoding to Protobuf) is on the backlog...!
* | | Aviod using exception for normal control flow.Henning Baldersheim2024-04-192-53/+35
| | |
* | | Revert <?>. Can not be used with components and injection.Henning Baldersheim2024-04-191-2/+2
| | |
* | | Use <?>Henning Baldersheim2024-04-181-2/+2
|/ /
* | Update expected uca version for chinese.Henning Baldersheim2024-04-171-1/+1
| |
* | Replace all usages of Arrays.asList with List.of where possible.Henning Baldersheim2024-04-1226-125/+104
| |
* | Unify on List.ofHenning Baldersheim2024-04-117-22/+17
| |
* | Unify on Set.ofHenning Baldersheim2024-04-112-6/+7
| |
* | Unify on Map.ofHenning Baldersheim2024-04-111-78/+0
|/
* Improve embedder error messagesJon Bratseth2024-03-292-5/+11
|
* Add synthetic targets so that you can always use cluster.schema as source ↵Henning Baldersheim2024-03-221-11/+4
| | | | | | | for both streaming and indexed. - Make a SearchChainInvocationSpec proxy for all possible searchcluster.schema combinations. - It will modify the query with the actual source to use, and restrict to the given schema.
* Revert "fold AND and SAND items into top-level WEAKAND"Arne H Juul2024-03-221-47/+18
|