-
Incorrect result degradation response when failing to connect to nodes that are retired or down in a group.
If a node is retired from a group and all documents are migrated to the other nodes we h…
-
The native query parameter is not included in the drop list.
![Screenshot 2022-01-13 at 12 33 49](https://user-images.githubusercontent.com/20928528/149323095-763faebf-9f20-4cf2-89b0-4971615081a7.…
-
**Describe the bug**
When uploading document in system tests, document processors are not triggered correctly. However, if I do that document upload via vespa cli, document processors are triggered c…
-
In mixed and sparse tensor attributes we are heap allocating the memory needed for each tensor value. These allocations are managed by _vespamalloc_. When such tensor attribute is downsized (e.g. when…
-
As demonstrated in https://github.com/sha124/vespa/blob/main/VespaDocSimilarity.ipynb, if there is a parsing error in the query and the search result returns no hits + 4xx, the error is swallowed. The…
-
**Describe the bug**
I am trying to use regex with attribute field in select query but not getting expected results.
Defined schema of fields used in query.
schema amDocument {
document am…
-
**Describe the bug**
One of our YQL queries is no longer returning the same number of hits in hitslist when grouping even if it should be more as before upgrade to vespa 8. (hits and limits should be…
-
Hi , am i right that the json parser is more strict in Vespa 8 than 7 ? We migrated our DEV instance and some of our YQL started to return
{"root":{"id":"toplevel","relevance":1.0,"fields":{"totalC…
-
new to vespa engine. I am trying to use this for some internal dataset
Wanted to get better understanding of some internal details to understand latency and compute resource usage.
When trying to …
-
**Is your feature request related to a problem? Please describe.**
We tried applying `attribute: paged` to a sparse tensor field and got the following error.
> Invalid application package: Error loa…