Skip to content

update broken links #4208

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 30, 2025
Merged

update broken links #4208

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions en/cloud/enclave/enclave.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,11 +19,11 @@ Vespa Cloud Enclave is available in AWS and GCP. Azure is on the roadmap.
resource costs from your cloud provider in _addition_ to the Vespa Cloud costs.

## AWS
* [Getting started](/en/cloud/enclave/aws-getting-started)
* [Getting started](/en/cloud/enclave/aws-deploy-an-application.html)
* [Architecture and security](/en/cloud/enclave/aws-architecture)

## GCP
* [Getting started](/en/cloud/enclave/gcp-getting-started)
* [Getting started](/en/cloud/enclave/gcp-deploy-an-application.html)
* [Architecture and security](/en/cloud/enclave/gcp-architecture)

## Guides
Expand Down
2 changes: 1 addition & 1 deletion en/elasticity.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@ <h2 id="adding-nodes">Adding nodes</h2>
To add or remove nodes from a content cluster, just <code>nodes</code>
tag of the <a href="reference/services-content.html">content</a> cluster in
<a href="reference/services.html">services.xml</a>
and <a href="applications.html#deploy">redeploy</a>.
and <a href="applications.html#deploying-applications">redeploy</a>.
Read more in <a href="/en/operations-selfhosted/admin-procedures.html">procedures</a>.
</p>

Expand Down
2 changes: 1 addition & 1 deletion en/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -95,7 +95,7 @@ No enforced limit, except resource usage (memory).

### Can a document have lists (key value pairs)?
E.g. a product is offered in a list of stores with a quantity per store.
Use [multivalue fields](schemas.html#field) (array of struct) or [parent child](parent-child.html).
Use [multivalue fields](/en/searching-multi-valued-fields.html) (array of struct) or [parent child](parent-child.html).
Which one to chose depends on use case, see discussion in the latter link.

### Does a whole document need to be updated and re-indexed?
Expand Down
2 changes: 1 addition & 1 deletion en/getting-started.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,7 @@
<strong>Recommendation</strong>
<p>
Learn how to use Vespa for content recommendation/personalization in the
<a href="tutorials/news-1-getting-started.html">News Search and Recommendation</a> tutorial set.
<a href="tutorials/news-1-deploy-an-application.html">News Search and Recommendation</a> tutorial set.
</p>

<strong>ML Model Serving</strong>
Expand Down
4 changes: 2 additions & 2 deletions en/page-templates.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,7 @@ <h2 id="getting-started">Getting Started</h2>
<li>Add the searcher
<a href="https://javadoc.io/doc/com.yahoo.vespa/container-search/latest/com/yahoo/search/pagetemplates/PageTemplateSearcher.html">com.yahoo.search.pagetemplates.PageTemplateSearcher</a>
to the default <a href="reference/services-search.html">search chain</a> in <em>services.xml</em>.</li>
<li><a href="applications.html#deploy">deploy</a>
<li><a href="applications.html#deploying-applications">deploy</a>
the application package.</li>
<li>Add these query parameters: <code>page.id=[comma-separated list of page id's]</code>
and <code>presentation.format=<a href="reference/page-result-format.html">page</a></code>.</li>
Expand Down Expand Up @@ -301,7 +301,7 @@ <h3 id="deploying-a-resolver">Deploying a Resolver</h3>
</pre>
<p>
With this, the application is
<a href="applications.html#deploy">deployed</a> as usual.
<a href="applications.html#deploying-applications">deployed</a> as usual.
</p>


Expand Down
4 changes: 2 additions & 2 deletions en/parent-child.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -90,12 +90,12 @@ <h2 id="parent-documents">Parent documents</h2>

<h2 id="multivalue-fields">Multivalue fields</h2>
<p>
A document can have <a href="schemas.html#field">fields</a> that are arrays or maps of struct.
A document can have <a href="schemas.html#document-fields">fields</a> that are arrays or maps of struct.
Structs and documents are similar - a set of field name/value pairs.
One-to-many mappings can therefore be implemented this way, as an alternative to using parent/child,
when each document has a set of properties that belongs to that document.
</p><p>
Refer to <a href="schemas.html#field">multivalue fields</a> for more information.
Refer to <a href="/en/searching-multi-valued-fields.html">multivalue fields</a> for more information.
</p>


Expand Down
2 changes: 1 addition & 1 deletion en/partial-updates.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -189,7 +189,7 @@ <h2 id="write-pipeline">Write pipeline</h2>
More details in <a href="attributes.html">attributes</a>.
</p>
<p>
Updating <a href="schemas.html#field">multivalue</a> attributes (arrays, maps, sets, tensors)
Updating <a href="/en/searching-multi-valued-fields.html">multivalue</a> attributes (arrays, maps, sets, tensors)
means reading the current value, making the update and writing it back:
</p>
<ul>
Expand Down
4 changes: 2 additions & 2 deletions en/performance/feature-tuning.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,7 +76,7 @@ <h2 id="when-to-use-fast-search-for-attribute-fields">When to use fast-search fo
</ul>
<p>
Changing fast-search aspect of the attribute is a
<a href="../reference/schema-reference.html#modifying-schemas">live change</a>
<a href="/en/reference/schema-reference.html#modifying-schemas">live change</a>
which does not require any re-feeding, so testing the performance with and without is low effort.
Adding or removing <em>fast-search</em> requires restart.
</p>
Expand All @@ -96,7 +96,7 @@ <h2 id="tuning-query-performance-for-lexical-search">Tuning query performance fo
Lexical search (or keyword-based search) is a method that matches query terms as they appear in indexed documents.
It relies on the lexical representation of words rather than their meaning, and is one of the two retrieval methods used in
<a href="../tutorials/hybrid-search.html">hybrid search</a>.
Lexical search in Vespa is done by querying string (text) <a href="../schemas.html#indexing">index</a> fields,
Lexical search in Vespa is done by querying string (text) <a href="../schemas.html#document-fields">index</a> fields,
typically using the <a href="../using-wand-with-vespa.html#weakand">weakAnd</a> query operator with <a href="../reference/bm25.html">BM25</a> ranking.
</p>
<p>
Expand Down
10 changes: 5 additions & 5 deletions en/performance/sizing-search.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,11 +16,11 @@
Vespa is used to implement many use cases, and this document is relevant for all of them:
</p>
<ul>
<li>Serving a <a href="../nativerank.html">text ranking</a> use case
or a <a href="../tutorials/news-1-getting-started.html">recommendation</a> use case</li>
<li>Serving a machine learned model, e.g., a <a href="../tensorflow.html">Tensorflow</a>,
<a href="../onnx.html">ONNX</a>, <a href="../xgboost.html">XGBoost</a>, or
<a href="../lightgbm.html">LightGBM</a> model</li>
<li>Serving a <a href="/en/nativerank.html">text ranking</a> use case
or a <a href="/en/tutorials/news-1-deploy-an-application.html">recommendation</a> use case</li>
<li>Serving a machine learned model, e.g., a <a href="/en/tensorflow.html">Tensorflow</a>,
<a href="/en/onnx.html">ONNX</a>, <a href="../xgboost.html">XGBoost</a>, or
<a href="/en/lightgbm.html">LightGBM</a> model</li>
</ul>
<p>
With Vespa, it is possible to do benchmarking on a few nodes
Expand Down
7 changes: 3 additions & 4 deletions en/query-api.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -134,8 +134,8 @@ <h3 id="using-a-fieldset">Using a fieldset</h3>
q=panda
</pre>
<p>
<code>myindex</code> is here a <a href="schemas.html#field">field</a>
or <a href="/en/schemas.html#fieldset">fieldset</a> in the schema.
<code>myindex</code> is here a <a href="schemas.html#document-fields">field</a>
or <a href="/en/reference/schema-reference.html#fieldset">fieldset</a> in the schema.
With userQuery(), use <a href="/en/reference/query-api-reference.html#model.defaultindex">model.defaultIndex</a>:
</p>
<pre>
Expand Down Expand Up @@ -375,8 +375,7 @@ <h3 id="query-processing-dispatch">Query processing and dispatch</h3>
</li>
<li>
<p>
The query is sent from the container to
the <a href="schemas.html#content-cluster-mapping">content cluster</a> -
The query is sent from the container to the <em>content cluster</em> -
see <a href="federation.html">federation</a> for more details.
An application can have multiple content clusters - Vespa searches in all by default.
<a href="federation.html">Federation</a> controls how to query the clusters,
Expand Down
5 changes: 4 additions & 1 deletion en/query-language.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,10 @@ <h2 id="live-query-examples">Live query examples</h2>
<p><a class="yql-x">select * from doc where title contains "ranking"</a></p>
<hr/>

<p>Filtering: Find all documents with <code>ranking</code> in the <code>default</code> <a href="schemas.html#fieldset">fieldset</a>.</p>
<p>
Filtering: Find all documents with <code>ranking</code> in the <code>default</code>
<a href="/en/reference/schema-reference.html#fieldset">fieldset</a>.
</p>
<p><a class="yql-x">select * from doc where default contains "ranking"</a></p>
<hr/>

Expand Down
2 changes: 1 addition & 1 deletion en/query-profiles.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,7 @@ <h2 id="using-a-query-profile">Using a Query Profile</h2>
e.g. <em>MyProfile.xml</em> (replace any <code>/</code> in the name by <code>_</code>)</li>
<li>Put this in the directory <em>search/query-profiles</em> in
the <a href="applications.html">application package</a> root</li>
<li><a href="applications.html#deploy">Redeploy</a> the application package</li>
<li><a href="applications.html#deploying-applications">Redeploy</a> the application package</li>
</ol>
<p>
Any number of query profile files may be added to this directory.
Expand Down
2 changes: 1 addition & 1 deletion en/ranking-expressions-features.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,7 @@ <h2 id="rank-features">Rank features</h2>
The primitive values used in ranking expressions
are called <a href="reference/rank-features.html">rank features</a>.
Rank features can be <a href="tensor-user-guide.html">tensors</a>,
<a href="schemas.html#field">multivalue fields</a> or scalars, and one of:
<a href="/en/searching-multi-valued-fields.html">multivalue fields</a> or scalars, and one of:
</p>
<ul>
<li>Constants set in the application package</li>
Expand Down
2 changes: 1 addition & 1 deletion en/ranking.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@

<p><i>Ranking</i> in Vespa is the computation that is done on matching documents during query execution.
These are specified as <a href="ranking-expressions-features.html">ranking functions</a> in
<a href="#rank-profile">rank profiles</a> in the schema.</p>
<em>rank profiles</em> in the schema.</p>

<p>The special function named <code>first-phase</code> will determine the initial <i>rank</i> of the matches,
such that the top k can be selected as response to a query:</p>
Expand Down
5 changes: 2 additions & 3 deletions en/reference/application-packages-reference.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,8 +72,7 @@
<td>Machine-learned models in the application package.
Refer to <a href="../stateless-model-evaluation.html">stateless model evaluation</a>,
<a href="../tensorflow.html">Tensorflow</a>, <a href="../onnx.html">Onnx</a>,
<a href="../xgboost.html">XGBoost</a>, and <a href="../lightgbm.html">LightGBM</a>, also see
<a href="../application-packages.html#deploying-remote-models">deploying remote models</a>
<a href="../xgboost.html">XGBoost</a>, and <a href="../lightgbm.html">LightGBM</a>.
</td>
</tr>
<tr>
Expand Down Expand Up @@ -189,7 +188,7 @@ <h2 id="deploy">Deploy</h2>
<a href="validation-overrides.html">validation overrides</a>
</li><li>
Distributes constant tensors and bundles with <a href="../jdisc/container-components.html">components</a>
to nodes using <a href="../application-packages.html#file-distribution">file distribution</a>.
to nodes using <a href="/en/deployment.html#file-distribution">file distribution</a>.
Files are downloaded to <em>$VESPA_HOME/var/db/vespa/filedistribution</em>,
URL download starts downloading to <em>$VESPA_HOME/var/db/vespa/download</em>
</li>
Expand Down
2 changes: 1 addition & 1 deletion en/reference/config-rest-api-v2.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@
</p>
<p>
The API is available after an application has been
<a href="../applications.html#deploy">deployed and activated</a>.
<a href="/en/applications.html#deploying-applications">deployed and activated</a>.
</p>


Expand Down
4 changes: 2 additions & 2 deletions en/reference/deploy-rest-api-v2.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@
</ul>
<p>
The response format is JSON. Examples are found in the <a href="#use-cases">use-cases</a>.
Also see the <a href="../application-packages.html#deploy">deploy guide</a>.
Also see the <a href="/en/applications.html#deploying-applications">deploy guide</a>.
</p>
{% include note.html content='To build a multi-application system, use one or three config server(s) per application.
Best practise is using a <a href="/en/operations-selfhosted/docker-containers.html">containerized</a> architecture,
Expand Down Expand Up @@ -1111,6 +1111,6 @@ <h3 id="rollback">Rollback</h3>
working version by passing the corresponding session-id in the
<em>from</em> argument, see <a href="#create-session">creating a session</a>
</p>
<p>Also see <a href="/en/application-packages.html#rollback">rollback</a>.</p>
<p>Also see <a href="/en/deployment.html#rollback">rollback</a>.</p>

<!-- TODO: Need multiple instances to support this. -->
7 changes: 3 additions & 4 deletions en/reference/embedding-reference.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,10 +16,9 @@ <h2 id="model-config-reference">Model config reference</h2>
<li>Otherwise, if a <code>url</code> is specified, it is used</li>
<li>Otherwise, <code>path</code> is used.</li>
</ul>
<p>
When using <code>path</code>, the model files must be supplied in the
Vespa <a href="../application-packages.html#deploying-remote-models">application package</a>.
</p>
<p>When using <code>path</code>, the model files must be supplied in the application package.</p>



<h2 id="huggingface-embedder">Huggingface Embedder</h2>
<p>
Expand Down
6 changes: 3 additions & 3 deletions en/reference/grouping-syntax.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,10 @@


<p>
Read the <a href="../grouping.html">Vespa grouping guide</a> first, for examples and an introduction to grouping -
Read the <a href="/en/grouping.html">Vespa grouping guide</a> first, for examples and an introduction to grouping -
this is the Vespa grouping reference.
</p><p>
Also note that using a <a href="../schemas.html#field">multivalued</a> attribute
Also note that using a <a href="/en/searching-multi-valued-fields.html">multivalued</a> attribute
(such as an array of doubles) in a grouping expression affects performance.
Such operations can hit a memory bandwidth bottleneck,
particularly if the set of hits to be processed is large, as more data is evaluated.
Expand Down Expand Up @@ -61,7 +61,7 @@ <h2 id="group">Group</h2>

<h3 id="multivalue-attributes">Multivalue attributes</h3>
<p>
A <a href="../schemas.html#field">multivalue</a> attribute is a
A <a href="/en/searching-multi-valued-fields.html">multivalue</a> attribute is a
<a href="schema-reference.html#weightedset">weighted set</a>,
<a href="schema-reference.html#array">array</a> or
<a href="schema-reference.html#map">map</a>. <!-- ToDo: check if more. link to schema -->
Expand Down
4 changes: 2 additions & 2 deletions en/reference/indexing-language-reference.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -593,7 +593,7 @@ <h3 id="other-expressions">Other expressions</h3>
<p id="join">
Creates a single string by concatenating the string representation of
each array element of the execution value.
This function is useful or indexing data from a <a href="../schemas.html#field">multivalue</a> field
This function is useful or indexing data from a <a href="/en/searching-multi-valued-fields.html">multivalue</a> field
into a singlevalue field.
</p>
</td>
Expand Down Expand Up @@ -700,7 +700,7 @@ <h3 id="other-expressions">Other expressions</h3>
<td>
<p id="split">
Splits the string representation of the execution value into a string array using the given regex pattern.
This function is useful for creating <a href="../schemas.html#field">multivalue</a>
This function is useful for creating <a href="/en/searching-multi-valued-fields.html">multivalue</a>
fields such as an integer array out of a string of comma-separated numbers.
</p>
</td>
Expand Down
8 changes: 3 additions & 5 deletions en/reference/query-api-reference.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -455,8 +455,7 @@ <h2 id="query-model">Query Model Parameters</h2>
<td>
<p id="model.restrict">
A comma-delimited list of document type (schema) names, defaulting to all schemas if not set.
See <a href="../schemas.html#multiple-schemas">multiple schemas</a> and
<a href="../federation.html">federation</a>.
See <a href="../federation.html">federation</a>.
</p>
<p>
Use <a href="#model.sources">model.sources</a> to restrict to content cluster names or other source names.
Expand Down Expand Up @@ -504,9 +503,8 @@ <h2 id="query-model">Query Model Parameters</h2>
<p id="model.sources">
A comma-separated list of content cluster names or other source names,
defaulting to all sources/clusters if not set.
The names of the sources to query, e.g. one or more content clusters and/or federated sources -
see <a href="../schemas.html#content-cluster-mapping">content cluster mapping</a>.
Also see <a href="../federation.html">federation</a>.
The names of the sources to query, e.g., one or more content clusters and/or federated sources -
see <a href="/en/federation.html">federation</a>.
</p>
<p>
Use <a href="#model.restrict">model.restrict</a> to only search a subset of the schemas in a cluster.
Expand Down
10 changes: 5 additions & 5 deletions en/reference/query-language-reference.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@

<h2 id="select">select</h2>
<p>
<em>select</em> is the list of <a href="../schemas.html#indexing">summary fields</a> requested
<em>select</em> is the list of <a href="/en/document-summaries.html#selecting-summary-fields-in-yql">summary fields</a> requested
(a field with the <code>summary</code> index attribute).
Vespa will hide other fields in the matching documents.
</p>
Expand Down Expand Up @@ -185,7 +185,7 @@ <h2 id="where">where</h2>
</table>
<p>
The matched field must be an
<a href="../schemas.html#indexing">indexed field or attribute</a>.
<a href="../schemas.html#document-fields">indexed field or attribute</a>.
</p><p>
Fields inside structs are referenced using dot notation -
e.g <code>mystruct.mystructfield</code>.
Expand Down Expand Up @@ -726,8 +726,8 @@ <h2 id="where">where</h2>
<thead></thead><tbody>
<tr>
<th>Field type</th>
<td>Singlevalue or <a href="../schemas.html#multivalue-field">multivalue</a>
<a href="../schemas.html#indexing">attribute or index field</a>
<td>Singlevalue or <a href="/en/searching-multi-valued-fields.html">multivalue</a>
<a href="/en/schemas.html#document-fields">attribute or index field</a>
with basic type <a href="schema-reference.html#byte">byte</a>, <a href="schema-reference.html#int">int</a>,
<a href="schema-reference.html#long">long</a> or <a href="schema-reference.html#string">string</a>. String fields must have <code>match:word</code> or <code>match:exact</code>.
</td>
Expand Down Expand Up @@ -847,7 +847,7 @@ <h2 id="where">where</h2>
<thead></thead><tbody>
<tr>
<th>Field type</th>
<td>Singlevalue or <a href="../schemas.html#field">multivalue</a> attribute or index field.
<td>Singlevalue or <a href="/en/searching-multi-valued-fields.html">multivalue</a> attribute or index field.
(Note: Most use cases operates on a single value field).</td>
</tr><tr>
<th>Query model</th>
Expand Down
Loading