jffwang
/
hetu-core
0
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

fix some uncorrect links

This commit is contained in:
tushengxia 2021-06-08 20:23:20 +08:00
parent 5ef125c618
commit 41606bdc5c
4 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
hetu-docs/en/connector/hive.md
View File

@ -730,7 +730,7 @@ DROP SCHEMA hive.web
* **For AARCH64:**
- Use [vacuum operation unify](../vacuum.md) to merge the multiple files created by many file writes in each partition such that scheduling splits becomes faster during read.
- Use [vacuum operation unify](../sql/vacuum.md) to merge the multiple files created by many file writes in each partition such that scheduling splits becomes faster during read.
```sql
VACUUM TABLE catalog_sales FULL UNIFY;

2
hetu-docs/en/language/types.md
View File

@ -208,7 +208,7 @@ Network Address
### `IPADDRESS`
> An IP address that can represent either an IPv4 or IPv6 address. Internally, the type is a pure IPv6 address. Support for IPv4 is handled using the *IPv4-mapped IPv6 address* range ([RFC 4291#section-2.5.5.2](https://tools.ietf.org/html/rfc4291.html#section-2.5.5.2)). When creating an `IPADDRESS`, IPv4 addresses will be mapped into that range. When formatting an `IPADDRESS`, any address within the mapped range will be formatted as an IPv4 address. Other addresses will be formatted as IPv6 using the canonical format defined in [RFC 5929](https://tools.ietf.org/html/rfc5952.html ).
> An IP address that can represent either an IPv4 or IPv6 address. Internally, the type is a pure IPv6 address. Support for IPv4 is handled using the *IPv4-mapped IPv6 address* range ([RFC 4291#section-2.5.5.2](https://tools.ietf.org/html/rfc4291.html#section-2.5.5.2)). When creating an `IPADDRESS`, IPv4 addresses will be mapped into that range. When formatting an `IPADDRESS`, any address within the mapped range will be formatted as an IPv4 address. Other addresses will be formatted as IPv6 using the canonical format defined in [RFC 5952](https://tools.ietf.org/html/rfc5952.html ).
>
> Examples: `IPADDRESS '10.0.0.1'`, `IPADDRESS '2001:db8::1'`

2
hetu-docs/zh/connector/hive.md
View File

@ -670,7 +670,7 @@ DROP SCHEMA hive.web
* **对于AArch64：**
- 使用[vacuum操作unify](../vacuum.md)合并每个分区中由多个文件写入创建的多个文件，这样在读取期间调度拆分会更快。
- 使用[vacuum操作unify](../sql/vacuum.md)合并每个分区中由多个文件写入创建的多个文件，这样在读取期间调度拆分会更快。
```sql
VACUUM TABLE catalog_sales FULL UNIFY;

6
hetu-docs/zh/language/types.md
View File

@ -205,7 +205,7 @@ openLooKeng有一组内置的数据类型，如下所述。可能通过插件提
### `IPADDRESS`
> 可表示IPv4地址或IPv6地址。对内为纯IPv6地址。可通过*IPv4-mapped IPv6 address* range ([RFC 4291#section-2.5.5.2](https://tools.ietf.org/html/rfc4291.md#section-2.5.5.2 ))来支持对IPv4地址的处理。在创建`IPADDRESS`时，IPv4地址将映射到指定的范围。格式化`IPADDRESS`时，在映射范围内的任何地址都会被格式化为IPv4地址。其他地址将使用[RFC 5929](https://tools.ietf.org/html/rfc5952.md)中定义的规范格式格式化为IPv6地址。
> 可表示IPv4地址或IPv6地址。对内为纯IPv6地址。可通过*IPv4-mapped IPv6 address* range ([RFC 4291#section-2.5.5.2](https://tools.ietf.org/html/rfc4291.html#section-2.5.5.2 ))来支持对IPv4地址的处理。在创建`IPADDRESS`时，IPv4地址将映射到指定的范围。格式化`IPADDRESS`时，在映射范围内的任何地址都会被格式化为IPv4地址。其他地址将使用[RFC 5952](https://tools.ietf.org/html/rfc5952.html) 中定义的规范格式格式化为IPv6地址。
>
> 例如: `IPADDRESS '10.0.0.1'`, `IPADDRESS '2001:db8::1'`
@ -214,14 +214,14 @@ UUID
### `UUID`
> 此类型表示UUID（通用唯一标识符），也称为GUID（全局唯一标识符），使用[RFC 4122](https://tools.ietf.org/html/rfc4122.md)中定义的格式。
> 此类型表示UUID（通用唯一标识符），也称为GUID（全局唯一标识符），使用[RFC 4122](https://tools.ietf.org/html/rfc4122.html) 中定义的格式。
>
> 例如: `UUID '12151fd2-7586-11e9-8f9e-2a86e4085a59'`
HyperLogLog
-----------
计算近似的非重复计数比使用[HyperLogLog](https://en.wikipedia.org/wiki/HyperLogLogLog)数据草图进行精确计数成本低得多。
计算近似的非重复计数比使用[HyperLogLog](https://en.wikipedia.org/wiki/HyperLogLog) 数据草图进行精确计数成本低得多。
请参见 [HyperLogLog 函数](../functions/hyperloglog.md)。
### `HyperLogLog`