| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\
| |
| |
| |
| | |
vespa-engine/vekterli/wire-fuzzy-prefix-match-through-query-stack
Wire fuzzy prefix matching support through the query stack
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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...!
|
| |\ \
| | |
| | |
| | |
| | | |
vespa-engine/toregge/stop-populating-extra-summary-fields
Stop populating extra summary fields.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Since autumn 2022 the document summary framework in the backend has
supported handling summary fields as pure virtual fields. A summary
field is just an output name, a source field (from the document type)
and an optional transform specifying how to produce the output. All
usages of summary fields are virtual as of Vespa 8.253.17 (November
2023), and the generation and population of some summary fields as
extra document fields can now be removed.
|
| |\ \ \
| | | |
| | | | |
Change default value of NEW_PATH_FOR_DISK_ENCRYPTION_KEY_METADATA to …
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
vespa-engine/lesters/set-llama-threads-in-unit-test
Specifically set number of threads to use in llama unit test
|
| | | | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
vespa-engine/balder/remove-asserts-and-test-with-invalid-typedcells
Test that distance calculation with invalid typed cells does not trig… MERGEOK
|
| | | | | | | |
|
| |\ \ \ \ \ \
| |/ / / / /
|/| | | | |
| | | | | |
| | | | | | |
vespa-engine/toregge/test-hnsw-index-prepare-add-document-and-find-top-k-with-missing-tensor
Test hnsw index prepare_add_document and find_top_k with missing tensor [MERGEOK]
|
| | | | | | | |
|
| |\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
Downscale groups
|
| | |/ / / / |
|
| |\ \ \ \ \
| |/ / / /
|/| | | |
| | | | |
| | | | | |
vespa-engine/toregge/return-max-distance-when-typed-cells-are-invalid
Return max distance when typed cells are invalid [MERGEOK]
|
| |/ / / / |
|
| |\ \ \ \
| | | | |
| | | | | |
Set minimum number of threads to 1
|
| | | | | | |
|
| |/ / / / |
|
| |\ \ \ \
| | | | |
| | | | | |
Bratseth/group size reduction
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
chore(deps): update dependency eslint to v9.1.0
|
| | | | | | | |
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | | |
fix(deps): update aws-java-sdk monorepo to v1.12.705
|
| | |/ / / / / |
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
vespa-engine/renovate/maven-jar-plugin.vespa.version
chore(deps): update dependency org.apache.maven.plugins:maven-jar-plugin to v3.4.1
|
| | |/ / / / /
| | | | | |
| | | | | |
| | | | | | |
v3.4.1
|
| |\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
chore(deps): update dependency vite to v5.2.10
|
| |/ / / / / |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
vespa-engine/renovate/maven-gpg-plugin.vespa.version
Update dependency org.apache.maven.plugins:maven-gpg-plugin to v3.2.4
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
v3.2.4
|
| |\ \ \ \ \ \
| |_|/ / / /
|/| | | | |
| | | | | |
| | | | | | |
vespa-engine/renovate/maven-resolver.vespa.version
Update maven-resolver.vespa.version to v1.9.19
|
| | |/ / / / |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Avoid starting quest db for /nodes/v2 unit tests
|
| | | | | | | |
|
| |\ \ \ \ \ \
| |_|/ / / /
|/| | | | | |
Move Results to the only place it is used.
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| |\ \ \ \ \ \
| |_|_|_|/ /
|/| | | | | |
fix(deps): update aws-java-sdk monorepo to v1.12.704
|
| | | | | | | |
|
| |\ \ \ \ \ \
| |_|_|/ / /
|/| | | | |
| | | | | |
| | | | | | |
vespa-engine/toregge/stop-adding-extra-documentid-field-to-document-type
Stop adding extra documentid field to document type.
|
| | | |_|_|/
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Since autumn 2022 the document summary framework in the backend has supported
handling summary fields as pure virtual fields. A summary field is just an
output name, a source field (from the document type) and an optional transform
specifying how to produce the output. All usages of summary fields are virtual
as of Vespa 8.253.17 (November 2023), and the generation and population of
some summary fields as extra document fields can now be removed.
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
vespa-engine/toregge/log-warning-when-type-is-specified-for-document-summary
Log warning when type is specified for document summary.
|
| | | | | | | |
|
