From 5f86b14df7d7331cbb572dd904a33b3a88d753b8 Mon Sep 17 00:00:00 2001 From: Dennis Felsing Date: Wed, 2 Mar 2022 12:43:45 +0100 Subject: [PATCH] [Docs] Fix broken links in docs.yugabyte.com Found with linkchecker: https://wummel.github.io/linkchecker/ Only on latest docs, the others are not allowed based on https://docs.yugabyte.com/robots.txt --- .../ysql/datatypes/type_datetime/conceptual-background.md | 4 ++-- .../type-interval/interval-utilities.md | 2 +- docs/content/latest/develop/docker/run-sample-apps.md | 4 ++-- docs/content/latest/develop/kubernetes/run-sample-apps.md | 4 ++-- docs/content/latest/explore/indexes-constraints/gin.md | 2 +- .../latest/explore/indexes-constraints/primary-key-ysql.md | 2 +- .../multi-region-deployments/row-level-geo-partitioning.md | 2 +- .../latest/explore/observability/grafana-dashboard/macos.md | 2 +- .../observability/prometheus-integration/kubernetes.md | 4 ++-- .../ysql-language-features/advanced-features/savepoints.md | 6 +++--- .../going-beyond-sql/follower-reads-ycql.md | 2 +- docs/content/latest/integrations/apache-spark/scala.md | 2 +- docs/content/latest/integrations/hasura/hasura-1.md | 4 ++-- docs/content/latest/integrations/liquibase.md | 4 ++-- docs/content/latest/releases/earlier-releases/v2.2.0.md | 2 +- docs/content/latest/releases/earlier-releases/v2.3.1.md | 2 +- .../latest/secure/tls-encryption/tls-authentication.md | 2 +- docs/content/latest/yedis/quick-start/binary/test-yedis.md | 2 +- .../latest/yugabyte-cloud/cloud-connect/connect/ysql.md | 2 +- .../yugabyte-cloud/cloud-examples/create-databases-ycql.md | 4 ++-- .../yugabyte-cloud/cloud-examples/create-databases.md | 2 +- .../cloud-examples/spring-boot/spring-boot-app.md | 2 +- .../cloud-examples/spring-boot/spring-boot-gke.md | 2 +- .../yugabyte-platform/manage-deployments/remove-nodes.md | 2 +- .../latest/yugabyte-platform/overview/configure/gcp.md | 2 +- 25 files changed, 34 insertions(+), 34 deletions(-) diff --git a/docs/content/latest/api/ysql/datatypes/type_datetime/conceptual-background.md b/docs/content/latest/api/ysql/datatypes/type_datetime/conceptual-background.md index 2c1fae73c5ba..4fcc2c5c9931 100644 --- a/docs/content/latest/api/ysql/datatypes/type_datetime/conceptual-background.md +++ b/docs/content/latest/api/ysql/datatypes/type_datetime/conceptual-background.md @@ -12,7 +12,7 @@ isTocNested: true showAsideToc: true --- -The following subsections provide the conceptual background for the accounts of the _date-time_ data types that the table shown in the [Synopsis](../intro/#synopsis) lists and for the operations that the _date-time_ operators and built-in SQL functions perform. +The following subsections provide the conceptual background for the accounts of the _date-time_ data types that the table shown in the [Synopsis](../#synopsis) lists and for the operations that the _date-time_ operators and built-in SQL functions perform. - [Absolute time and the UTC Time Standard](#absolute-time-and-the-utc-time-standard) - [Wall-clock-time and local time](#wall-clock-time-and-local-time) @@ -73,7 +73,7 @@ It quietly succeeds and produces the obvious result. (The _::text_ typecast of a 4713-01-01 00:00:00 BC | 294276-01-01 00:00:00 ``` -The values, _4713 BC_ and _294276_ AD, are given in the [table](../intro/#synopsis) in the _"Introduction"_ section to the present _date-time_ data types major section. +The values, _4713 BC_ and _294276_ AD, are given in the [table](../#synopsis) in the _"Introduction"_ section to the present _date-time_ data types major section. ## Wall-clock-time and local time diff --git a/docs/content/latest/api/ysql/datatypes/type_datetime/date-time-data-types-semantics/type-interval/interval-utilities.md b/docs/content/latest/api/ysql/datatypes/type_datetime/date-time-data-types-semantics/type-interval/interval-utilities.md index 412df5f23e24..12cc799d3723 100644 --- a/docs/content/latest/api/ysql/datatypes/type_datetime/date-time-data-types-semantics/type-interval/interval-utilities.md +++ b/docs/content/latest/api/ysql/datatypes/type_datetime/date-time-data-types-semantics/type-interval/interval-utilities.md @@ -67,7 +67,7 @@ Here's an example of such a _text_ literal: PostgreSQL defines two fundamentally different data type families for representing real numbers and for supporting arithmetic using their values. Of course, YSQL inherits this regime. -The PostgreSQL documentation uses the terms [Arbitrary Precision Numbers](https://www.postgresql.org/docs/11/datatype-numeric.html#DATATYPE-NUMERIC-DECIMAL) and [Floating-Point Numbers](https://www.postgresql.org/docs/11/datatype-numeric.html#DATATYPE-FLOAT) for these two kinds of data type. The first kind is exemplified by the data type _numeric_. And the second kind is exemplified by _double precision_. There are other variants in each class. But the entire _[date_time](../../../type_datetime/)_ section uses only these two (and uses only the unconstraint _numeric_ variant). Moreover, it uses _numeric_ only under duress. For example, you can easily round a _numeric_ value to some desired number of decimal places like this: +The PostgreSQL documentation uses the terms [Arbitrary Precision Numbers](https://www.postgresql.org/docs/11/datatype-numeric.html#DATATYPE-NUMERIC-DECIMAL) and [Floating-Point Numbers](https://www.postgresql.org/docs/11/datatype-numeric.html#DATATYPE-FLOAT) for these two kinds of data type. The first kind is exemplified by the data type _numeric_. And the second kind is exemplified by _double precision_. There are other variants in each class. But the entire _[date_time](../../../)_ section uses only these two (and uses only the unconstraint _numeric_ variant). Moreover, it uses _numeric_ only under duress. For example, you can easily round a _numeric_ value to some desired number of decimal places like this: ```plpgsql select round(12.3456789::numeric, 3::int); diff --git a/docs/content/latest/develop/docker/run-sample-apps.md b/docs/content/latest/develop/docker/run-sample-apps.md index bbd83e52debe..e634ad56e0ea 100644 --- a/docs/content/latest/develop/docker/run-sample-apps.md +++ b/docs/content/latest/develop/docker/run-sample-apps.md @@ -34,8 +34,8 @@ Now you can observe the effects of the read/write operations generated by the lo ## 5. Review Yugastore architecture and code -Details of Yugastore architecture are documented [here](../../develop/realworld-apps/ecommerce-app/). Source code is available in the [Yugastore GitHub repo](https://github.com/yugabyte/yugastore). +Details of Yugastore architecture are documented [here](../../../realworld-apps/ecommerce-app/). Source code is available in the [Yugastore GitHub repo](https://github.com/yugabyte/yugastore). ## 6. Run IoT Fleet Management app -After running Yugastore, Yugabyte recommends running the [IoT Fleet Management](../realworld-apps/iot-spark-kafka-ksql/) app. This app is built on top of YugabyteDB as the database (using the YCQL API), Confluent Kafka as the message broker, KSQL or Apache Spark Streaming for real-time analytics and Spring Boot as the application framework. +After running Yugastore, Yugabyte recommends running the [IoT Fleet Management](../../../realworld-apps/iot-spark-kafka-ksql/) app. This app is built on top of YugabyteDB as the database (using the YCQL API), Confluent Kafka as the message broker, KSQL or Apache Spark Streaming for real-time analytics and Spring Boot as the application framework. diff --git a/docs/content/latest/develop/kubernetes/run-sample-apps.md b/docs/content/latest/develop/kubernetes/run-sample-apps.md index b8fdda0ddee1..a2199677584b 100644 --- a/docs/content/latest/develop/kubernetes/run-sample-apps.md +++ b/docs/content/latest/develop/kubernetes/run-sample-apps.md @@ -85,8 +85,8 @@ The above output is the Admin UI URL and visiting the Tablet Servers page there ## 5. Review Yugastore architecture and code -Details of Yugastore architecture are documented [here](../realworld-apps/ecommerce-app/). Source code is available in the [Yugastore GitHub repo](https://github.com/yugabyte/yugastore). +Details of Yugastore architecture are documented [here](../../../realworld-apps/ecommerce-app/). Source code is available in the [Yugastore GitHub repo](https://github.com/yugabyte/yugastore). ## 6. Run IoT Fleet Management app -After running Yugastore, Yugabyte recommends running the [IoT Fleet Management](../realworld-apps/iot-spark-kafka-ksql/) app. This app is built on top of YugabyteDB as the database (using the YCQL API), Confluent Kafka as the message broker, KSQL or Apache Spark Streaming for real-time analytics and Spring Boot as the application framework. +After running Yugastore, Yugabyte recommends running the [IoT Fleet Management](../../../realworld-apps/iot-spark-kafka-ksql/) app. This app is built on top of YugabyteDB as the database (using the YCQL API), Confluent Kafka as the message broker, KSQL or Apache Spark Streaming for real-time analytics and Spring Boot as the application framework. diff --git a/docs/content/latest/explore/indexes-constraints/gin.md b/docs/content/latest/explore/indexes-constraints/gin.md index 33fcd1fa68eb..b8e15318a1f6 100644 --- a/docs/content/latest/explore/indexes-constraints/gin.md +++ b/docs/content/latest/explore/indexes-constraints/gin.md @@ -16,7 +16,7 @@ showAsideToc: true