| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
Balder/jackson 2.17.1
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
vespa-engine/jonmv/improved-feed-throttle-algorithm
Jonmv/improved feed throttle algorithm
|
| | | |
|
| |/
| |
| |
| |
| |
| |
| | |
vespa-engine/revert-31158-jonmv/start-lower-when-feeding"
This reverts commit dc1d2982e21098e0dee252f229762960259382ac, reversing
changes made to 1073327b4b38213311e992f2c2353a376d3404de.
|
|\ \
| |/
|/|
| |
| | |
vespa-engine/vekterli/track-local-docs-received-explicitly
Explicitly track number of locally entries received through visiting
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Using the underlying session's `VisitorStatistics` may not be 1-1
with the actual number of entries the data handler has been invoked
with. This causes issues if anyone tries to cross-check the document
count emitted as part of the results vs. the number of entries
actually present in the result array.
The session updates its statistics based on the what is returned from
the backend as part of _successful_ `CreateVisitorReply` messages.
If a CreateVisitor returns with a transient error, the statistics will
not be updated, but it's unspecified how many (if any) document entries
that particular visitor may already have pushed to the client directly
from the content nodes.
Note that the locally tracked number is only reported if the session
itself is receiving the document data; if a remote data handler is
in use we have to report what the `VisitorStatistics` give us.
|
|\ \
| |/
|/| |
Add remove-orphaned-dns-records flag
|
|/ |
|
|\
| |
| |
| |
| | |
vespa-engine/revert-31158-jonmv/start-lower-when-feeding
Revert "Reduce min inflight for go feeder, and start lower in both go and java"
|
|/ |
|
|\
| |
| | |
Set default zookeeper-server-version to 3.9.2
|
| | |
|
|\ \
| | |
| | | |
Update mockito monorepo to v5.12.0
|
| | | |
|
|\ \ \
| | | |
| | | | |
Update dependency react-router-dom to v6.23.1
|
| |/ / |
|
|\ \ \
| |/ /
|/| | |
Update aws-java-sdk monorepo to v1.12.720
|
|/ / |
|
|\ \
| |/
|/|
| |
| | |
vespa-engine/toregge/use-btree-iterator-move-constructor
Use btree iterator move constructor.
|
| | |
|
|\ \
| | |
| | | |
Increase rounding precision for success factor
|
| | | |
|
|\ \ \
| |/ /
|/| | |
Allow empty roles
|
| | | |
|
|\ \ \
| | | |
| | | | |
Add embedder metrics to vespa9 metricset
|
| | |/
| |/| |
|
|\ \ \
| | | |
| | | | |
Add feature flag for Hubspot
|
| | |/
| |/| |
|
|\ \ \
| |_|/
|/| | |
use least common term to drive strict phrase search
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| | |
stop using beginId since it only makes sense for the first (or full)
docid space
remove misleading assert. We could still end up with an infinite loop
without triggering the assert if the driving term matched the next
document. Also, this assert is not used with other iterators that
require strict children.
|
|\ \
| | |
| | |
| | |
| | | |
vespa-engine/revert-31156-vekterli/explicitly-tracked-received-doc-entries-in-v1-handler
Revert "Explicitly track number of entries received through visiting"
|
|/ / |
|
|\ \
| |/
|/| |
Reduce min inflight for go feeder, and start lower in both go and java
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
vespa-engine/renovate/org.openrewrite.recipe-rewrite-testing-frameworks-2.x
Update dependency org.openrewrite.recipe:rewrite-testing-frameworks to v2.8.0
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
vespa-engine/renovate/org.openrewrite.recipe-rewrite-recipe-bom-2.x
Update dependency org.openrewrite.recipe:rewrite-recipe-bom to v2.11.0
|
| |/ / |
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
vespa-engine/renovate/org.openrewrite.maven-rewrite-maven-plugin-5.x
Update dependency org.openrewrite.maven:rewrite-maven-plugin to v5.30.0
|
| |/ / |
|
|\ \ \
| |/ /
|/| | |
Update aws-java-sdk monorepo to v1.12.718
|
|/ / |
|
|\ \
| | |
| | |
| | |
| | | |
vespa-engine/vekterli/explicitly-tracked-received-doc-entries-in-v1-handler
Explicitly track number of entries received through visiting
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Using the underlying session's `VisitorStatistics` may not be 1-1
with the actual number of entries the data handler has been invoked
with. This causes issues if anyone tries to cross-check the document
count emitted as part of the results vs. the number of entries
actually present in the result array.
The session updates its statistics based on the what is returned from
the backend as part of _successful_ `CreateVisitorReply` messages.
If a CreateVisitor returns with a transient error, the statistics will
not be updated, but it's unspecified how many (if any) document entries
that particular visitor may already have pushed to the client directly
from the content nodes.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
vespa-engine/vekterli/add-cluster-bucket-out-of-sync-metric
Emit single metric for how out of sync the cluster data is
|