Merge pull request #4208 from vespa-engine/kkraune/links

update broken links

Author: kkraune

en/cloud/enclave/enclave.md

@@ -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

en/elasticity.html

@@ -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>
 

en/faq.md

@@ -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?

en/getting-started.html

@@ -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>

en/page-templates.html

@@ -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>
@@ -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>
 
 

en/parent-child.html

@@ -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>
 
 

en/partial-updates.html

@@ -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>

en/performance/feature-tuning.html

@@ -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>
@@ -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>

en/performance/sizing-search.html

@@ -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

en/query-api.html

@@ -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>
@@ -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,