This is an automated email from the ASF dual-hosted git repository.
dkuzmenko pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/hive-site.git
The following commit(s) were added to refs/heads/main by this push:
new b5e656d HIVE-29135: Rename regular to Type-Native to make it more
intuitive and understandable. (#72)
b5e656d is described below
commit b5e656dc031c6e2cc670096c256d4541381f7cad
Author: kokila-19 <[email protected]>
AuthorDate: Mon Nov 3 14:37:08 2025 +0530
HIVE-29135: Rename regular to Type-Native to make it more intuitive and
understandable. (#72)
---
content/docs/latest/language/languagemanual.md | 2 +-
content/docs/latest/language/writeordering.md | 25 +++++--------------------
2 files changed, 6 insertions(+), 21 deletions(-)
diff --git a/content/docs/latest/language/languagemanual.md
b/content/docs/latest/language/languagemanual.md
index 1509246..e835762 100644
--- a/content/docs/latest/language/languagemanual.md
+++ b/content/docs/latest/language/languagemanual.md
@@ -24,7 +24,7 @@ This is the Hive Language Manual. For other Hive
documentation, see the Hive w
* Data Definition Statements
+ [DDL Statements]({{< ref "languagemanual-ddl" >}})
- [Bucketed Tables]({{< ref "languagemanual-ddl-bucketedtables"
>}})
- - [Write Ordering (Regular & Z-Order)]({{< ref "writeordering"
>}})
+ - [Write Ordering (Type-Native & Z-Order)]({{< ref
"writeordering" >}})
+ [Statistics (Analyze and Describe)]({{< ref "statsdev" >}})
+ [Indexes]({{< ref "languagemanual-indexing" >}})
+ [Archiving]({{< ref "languagemanual-archiving" >}})
diff --git a/content/docs/latest/language/writeordering.md
b/content/docs/latest/language/writeordering.md
index 76b399c..f8aed99 100644
--- a/content/docs/latest/language/writeordering.md
+++ b/content/docs/latest/language/writeordering.md
@@ -12,12 +12,12 @@ Write ordering controls the physical layout of data within
table files. Unlike `
Write ordering is supported for Iceberg tables and can be specified during
table creation.
Hive supports two write ordering strategies:
-* **Regular Ordering**: Sort by one or more columns in a specified order
+* **Type-Native Ordering**: Sort by one or more columns in a specified order
* **Z-Ordering**: Multi-dimensional clustering using space-filling curves
---
-## Regular Column Ordering
+## Type-Native Column Ordering
### Version
@@ -72,7 +72,7 @@ STORED BY ICEBERG;
### Use Cases
-Regular ordering is most effective for:
+Type-Native ordering is most effective for:
* Time-series data with temporal access patterns
* Range queries on sorted columns
@@ -100,9 +100,7 @@ STORED BY ICEBERG
[STORED AS file_format];
```
-### Examples
-
-Two columns:
+### Example
```sql
CREATE TABLE user_events (
@@ -116,19 +114,6 @@ STORED BY ICEBERG
STORED AS ORC;
```
-Multiple columns:
-
-```sql
-CREATE TABLE analytics (
- customer_id INT,
- activity_date DATE,
- country STRING,
- product_id INT
-)
-WRITE ORDERED BY ZORDER(customer_id, activity_date, country)
-STORED BY ICEBERG;
-```
-
### Table Properties Method
Z-ordering can alternatively be specified using table properties.
@@ -166,6 +151,6 @@ Z-order is most effective for:
* Write ordering only applies to Iceberg tables
* Write operations incur ordering overhead:
- * Regular ordering: Sort cost
+ * Type-Native ordering: Sort cost
* Z-order: Sort cost plus z-value computation
* Column selection should be based on query workload analysis
