kudu-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ale...@apache.org
Subject [kudu] 01/02: docs: correct invalid link about schema_design
Date Thu, 22 Aug 2019 01:34:11 GMT
This is an automated email from the ASF dual-hosted git repository.

alexey pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/kudu.git

commit 98b6faae52c2bc787443f242e238a2e43d57ad81
Author: Xiaokai Wang <xiaokai.wang@live.com>
AuthorDate: Sat Aug 17 00:13:02 2019 +0800

    docs: correct invalid link about schema_design
    
    Change-Id: I41e8671f518bb898dd357dc5024a7d8ab335b401
    Reviewed-on: http://gerrit.cloudera.org:8080/14028
    Tested-by: Kudu Jenkins
    Reviewed-by: Grant Henke <granthenke@apache.org>
---
 docs/index.adoc                   | 4 ++--
 docs/known_issues.adoc            | 2 +-
 docs/kudu_impala_integration.adoc | 4 ++--
 docs/prior_release_notes.adoc     | 4 ++--
 4 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/docs/index.adoc b/docs/index.adoc
index 7a301ec..f693b6e 100644
--- a/docs/index.adoc
+++ b/docs/index.adoc
@@ -82,7 +82,7 @@ Flexible Partitioning::
   pre-split tables by hash or range into a predefined number of tablets, in order
   to distribute writes and queries evenly across your cluster. You can partition by
   any number of primary key columns, by any number of hashes, and an optional list of
-  split rows. See link:schema_design.html[Schema Design].
+  split rows. See <<schema_design.adoc#schema_design,Schema Design>>.
 Parallel Scan::
   To achieve the highest possible performance on modern hardware, the Kudu client
   used by Impala parallelizes scans across multiple tablets.
@@ -112,7 +112,7 @@ pattern-based compression can be orders of magnitude more efficient than
 compressing mixed data types, which are used in row-based solutions. Combined
 with the efficiencies of reading data from columns, compression allows you to
 fulfill your query while reading even fewer blocks from disk. See
-link:schema_design.html#encoding[Data Compression]
+<<schema_design.adoc#encoding,Data Compression>>
 
 .Table
 
diff --git a/docs/known_issues.adoc b/docs/known_issues.adoc
index 2c9d9bf..083654b 100644
--- a/docs/known_issues.adoc
+++ b/docs/known_issues.adoc
@@ -90,7 +90,7 @@
 * Tables must be manually pre-split into tablets using simple or compound primary
   keys. Automatic splitting is not yet possible. Range partitions may be added
   or dropped after a table has been created. See
-  link:schema_design.html[Schema Design] for more information.
+  <<schema_design.adoc#schema_design,Schema Design>> for more information.
 
 * Data in existing tables cannot currently be automatically repartitioned. As a workaround,
   create a new table with the new partitioning and insert the contents of the old
diff --git a/docs/kudu_impala_integration.adoc b/docs/kudu_impala_integration.adoc
index fe69cb5..6a5e49c 100755
--- a/docs/kudu_impala_integration.adoc
+++ b/docs/kudu_impala_integration.adoc
@@ -288,7 +288,7 @@ key columns. Each tablet is served by at least one tablet server. Ideally,
a tab
 should be split into tablets that are distributed across a number of tablet servers
 to maximize parallel operations. The details of the partitioning schema you use
 will depend entirely on the type of data you store and how you access it. For a full
-discussion of schema design in Kudu, see link:schema_design.html[Schema Design].
+discussion of schema design in Kudu, see <<schema_design.adoc#schema_design,Schema
Design>>.
 
 Kudu currently has no mechanism for splitting or merging tablets after the table has
 been created. You must provide a partition schema for your table when you create it.
@@ -497,7 +497,7 @@ which address scenarios like the following:
   need to be added or removed, such as the introduction or elimination of a product
   type.
 
-See link:schema_design.html[Schema Design] for the caveats of non-covering partitions.
+See <<schema_design.adoc#schema_design,Schema Design>> for the caveats of non-covering
partitions.
 
 This example creates a tablet per year (5 tablets total), for storing log data.
 The table only accepts data from 2012 to 2016. Keys outside of these
diff --git a/docs/prior_release_notes.adoc b/docs/prior_release_notes.adoc
index 16fda00..34d3d56 100644
--- a/docs/prior_release_notes.adoc
+++ b/docs/prior_release_notes.adoc
@@ -902,7 +902,7 @@ Apache Kudu 1.7.1 is a bug-fix release which fixes critical issues in
Kudu 1.7.0
   calculations where the imprecise representation and rounding behavior of float and
   double make those types impractical. The decimal type is also useful for integers
   larger than int64 and cases with fractional values in a primary key.
-  See link:schema_design.html#decimal[Decimal Type] for more details.
+  See <<schema_design.adoc#decimal,Decimal Type>> for more details.
 
 * The strategy Kudu uses for automatically healing tablets which have lost a
   replica due to server or disk failures has been improved. The new re-replication
@@ -2620,7 +2620,7 @@ changes between 0.8.0 and 0.9.0</a>+++.
 
 - Default table partitioning has been removed. All tables must now be created
   with explicit partitioning. Existing tables are unaffected. See the
-  link:schema_design.html#no_default_partitioning[schema design guide] for more
+  <<schema_design.adoc#no_default_partitioning,schema design guide>> for more
   details.
 
 [[rn_0.9.0_new_features]]


Mime
View raw message