Merge branch 'main' into akulov

.github/workflows/gh-pages.yml

@@ -8,36 +8,36 @@ on:
 
 jobs:
   deploy:
-    runs-on: ubuntu-20.04
+    runs-on: ubuntu-22.04
     steps:
       - name: Git checkout
-        uses: actions/checkout@v2
+        uses: actions/checkout@v4
         with:
           submodules: true  # Fetch Hugo themes (true OR recursive)
           fetch-depth: 0    # Fetch all history for .GitInfo and .Lastmod
           ref: main
 
       - name: Setup Hugo
-        uses: peaceiris/actions-hugo@v2
+        uses: peaceiris/actions-hugo@v3
         with:
           hugo-version: '0.128.2'
           extended: true
 
       - name: Cache Hugo modules
-        uses: actions/cache@v2
+        uses: actions/cache@v4
         with:
           path: /tmp/hugo_cache
           key: ${{ runner.os }}-hugomod-${{ hashFiles('**/go.sum') }}
           restore-keys: |
             ${{ runner.os }}-hugomod-
 
       - name: Setup Node
-        uses: actions/setup-node@v3
+        uses: actions/setup-node@v4
         with:
-          node-version: '14'
+          node-version: '20'
 
       - name: Cache dependencies
-        uses: actions/cache@v2
+        uses: actions/cache@v4
         with:
           path: ~/.npm
           key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
@@ -51,7 +51,7 @@ jobs:
         # run: hugo --gc
 
       - name: Deploy
-        uses: peaceiris/actions-gh-pages@v3
+        uses: peaceiris/actions-gh-pages@v4
         if: github.ref == 'refs/heads/main'
         with:
           github_token: ${{ secrets.GITHUB_TOKEN }}

config.toml

@@ -54,8 +54,8 @@ anchor = "smart"
 
 [languages]
 [languages.en]
-title = "Altinity® Knowledge Base"
-description = "Altinity® Knowledge Base for ClickHouse®"
+title = "Altinity Knowledge Base for ClickHouse®"
+description = "Altinity Knowledge Base for ClickHouse®"
 languageName = "English"
 # Weight used for sorting.
 weight = 1
@@ -76,7 +76,7 @@ time_format_blog = "2006.01.02"
 
 [params]
 # copyright = " Altinity Inc."
-copyright = " Altinity Inc. Altinity®, Altinity.Cloud®, and Altinity Stable® are registered trademarks of Altinity, Inc. ClickHouse® is a registered trademark of ClickHouse, Inc.; Altinity is not affiliated with or associated with ClickHouse, Inc."
+copyright = " Altinity Inc. Altinity®, Altinity.Cloud®, and Altinity Stable® are registered trademarks of Altinity, Inc. ClickHouse® is a registered trademark of ClickHouse, Inc.; Altinity is not affiliated with or associated with ClickHouse, Inc. Kafka, Kubernetes, MySQL, and PostgreSQL are trademarks and property of their respective owners."
 privacy_policy = "https://altinity.com/privacy-policy/"
 favicon = "/favicon.ico"
 

content/en/_index.md

@@ -1,6 +1,6 @@
 ---
-title: "Altinity® Knowledge Base"
-linkTitle: "Altinity® Knowledge Base"
+title: "Altinity Knowledge Base for ClickHouse®"
+linkTitle: "Altinity Knowledge Base for ClickHouse®"
 description: "Up-to-date ClickHouse® knowledge base for every ClickHouse user."
 keywords:
 - ClickHouse Knowledge Base
@@ -21,11 +21,17 @@ The [Altinity Knowledge Base is licensed under Apache 2.0](https://github.com/Al
 For more detailed information about Altinity services support, see the following:
 
 * [Altinity](https://altinity.com/): Providers of Altinity.Cloud, providing SOC-2 certified support for ClickHouse.
-* [Altinity ClickHouse Documentation](https://docs.altinity.com): Detailed guides on installing and connecting ClickHouse software to other services.
+* [Altinity.com Documentation](https://docs.altinity.com): Detailed guides on working with: 
+  * [Altinity.Cloud](https://docs.altinity.com/altinitycloud/)
+  * [Altinity.Cloud Anywhere](https://docs.altinity.com/altinitycloudanywhere/)
+  * [The Altinity Cloud Manager](https://docs.altinity.com/altinitycloud/quickstartguide/clusterviewexplore/)
+  * [The Altinity Kubernetes Operator for ClickHouse](https://docs.altinity.com/releasenotes/altinity-kubernetes-operator-release-notes/)
+  * [The Altinity Sink Connector for ClickHouse](https://docs.altinity.com/releasenotes/altinity-sink-connector-release-notes/) and
+  * [Altinity Backup for ClickHouse](https://docs.altinity.com/releasenotes/altinity-backup-release-notes/) 
 * [Altinity Blog](https://altinity.com/blog/): Blog posts about ClickHouse the database and Altinity services.
 
 The following sites are also useful references regarding ClickHouse:
 
-* [ClickHouse.com documentation](https://clickhouse.com/docs/en/): From Yandex, the creators of ClickHouse
+* [ClickHouse.com documentation](https://clickhouse.com/docs/en/): Official documentation from ClickHouse Inc.
 * [ClickHouse at Stackoverflow](https://stackoverflow.com/questions/tagged/clickhouse): Community driven responses to questions regarding ClickHouse
 * [Google groups (Usenet) yes we remember it](https://groups.google.com/g/clickhouse): The grandparent of all modern discussion boards.

content/en/altinity-kb-dictionaries/_index.md

@@ -6,11 +6,11 @@ keywords:
 - clickhouse arrays
 - postgresql dictionary
 description: >
-    All you need to know about creating and using ClickHouse dictionaries.
+    All you need to know about creating and using ClickHouse® dictionaries.
 weight: 11
 ---
 
-For more information on ClickHouse Dictionaries, see
+For more information on ClickHouse® Dictionaries, see
 
 the presentation [https://github.com/ClickHouse/clickhouse-presentations/blob/master/meetup34/clickhouse_integration.pdf](https://github.com/ClickHouse/clickhouse-presentations/blob/master/meetup34/clickhouse_integration.pdf), slides 82-95, video https://youtu.be/728Yywcd5ys?t=10642
 
@@ -21,6 +21,6 @@ https://altinity.com/blog/2020/5/19/clickhouse-dictionaries-reloaded
 And some videos:
 https://www.youtube.com/watch?v=FsVrFbcyb84
 
-Also there 3rd party articles on the same subj.
+Also there are 3rd party articles on the same subj.
 https://prog.world/how-to-create-and-use-dictionaries-in-clickhouse/
 

content/en/altinity-kb-dictionaries/dictionaries-and-arrays.md

@@ -4,7 +4,7 @@ linkTitle: "Dictionaries & arrays"
 description: >
     Dictionaries & arrays
 ---
-## Dictionary with Clickhouse table as a source
+## Dictionary with ClickHouse® table as a source
 
 ### Test data
 

content/en/altinity-kb-dictionaries/mysql8-source-for-dictionaries.md

@@ -6,7 +6,7 @@ description: >
 ---
 #### Authorization
 
-MySQL8 used default authorization plugin `caching_sha2_password`. Unfortunately, `libmysql` which currently used (21.4-) in clickhouse is not.
+MySQL8 used default authorization plugin `caching_sha2_password`. Unfortunately, `libmysql` which currently used (21.4-) in ClickHouse® is not.
 
 You can fix it during create custom user with `mysql_native_password` authentication plugin.
 

content/en/altinity-kb-dictionaries/partial-updates.md

@@ -4,7 +4,7 @@ linkTitle: "Partial updates"
 description: >
     Partial updates
 ---
-Clickhouse is able to fetch from a source only updated rows. You need to define `update_field` section.
+ClickHouse® is able to fetch from a source only updated rows. You need to define `update_field` section.
 
 As an example, We have a table in an external source MySQL, PG, HTTP, ... defined with the following code sample:
 
@@ -36,4 +36,4 @@ LIFETIME(MIN 30 MAX 30)
 
 A dictionary with **update_field** `updated_at` will fetch only updated rows. A dictionary saves the current time (now) time of the last successful update and queries the source `where updated_at >= previous_update - 1` (shift = 1 sec.).
 
-In case of HTTP source Clickhouse will send get requests with **update_field** as an URL parameter `&updated_at=2020-01-01%2000:01:01`
+In case of HTTP source ClickHouse will send get requests with **update_field** as an URL parameter `&updated_at=2020-01-01%2000:01:01`

content/en/altinity-kb-dictionaries/security-named-collections.md

@@ -6,7 +6,7 @@ description: >
 ---
 
 
-## Dictionary with Clickhouse table as a source with named collections
+## Dictionary with ClickHouse® table as a source with named collections
 
 ### Data for connecting to external sources can be stored in named collections
 

content/en/altinity-kb-functions/array-like-memory-usage.md

@@ -7,7 +7,7 @@ description: >
 
 ## arrayMap-like functions memory usage calculation.
 
-In order to calculate arrayMap or similar array* functions ClickHouse temporarily does arrayJoin-like operation, which in certain conditions can lead to huge memory usage for big arrays.
+In order to calculate arrayMap or similar array* functions ClickHouse® temporarily does arrayJoin-like operation, which in certain conditions can lead to huge memory usage for big arrays.
 
 So for example, you have 2 columns:
 

content/en/altinity-kb-functions/assumenotnull-and-friends.md

@@ -89,7 +89,7 @@ Code: 36, e.displayText() = DB::Exception: Unexpected value 0 in enum, Stack tra
 ```
 
 {{% alert title="Info" color="info" %}}
-Null values in ClickHouse are stored in a separate dictionary: is this value Null. And for faster dispatch of functions there is no check on Null value while function execution, so functions like plus can modify internal column value (which has default value). In normal conditions it’s not a problem because on read attempt, ClickHouse first would check the Null dictionary and return value from column itself for non-Nulls only. And `assumeNotNull` function just ignores this Null dictionary. So it would return only column values, and in certain cases it’s possible to have unexpected results.
+Null values in ClickHouse® are stored in a separate dictionary: is this value Null. And for faster dispatch of functions there is no check on Null value while function execution, so functions like plus can modify internal column value (which has default value). In normal conditions it’s not a problem because on read attempt, ClickHouse first would check the Null dictionary and return value from column itself for non-Nulls only. And `assumeNotNull` function just ignores this Null dictionary. So it would return only column values, and in certain cases it’s possible to have unexpected results.
 {{% /alert %}}
 
 If it's possible to have Null values, it's better to use `ifNull` function instead.

content/en/altinity-kb-functions/how-to-encode-decode-quantiletdigest-state.md

@@ -3,7 +3,7 @@ title: "How to encode/decode quantileTDigest states from/to list of centroids"
 linkTitle: "Encoding and Decoding of quantileTDigest states"
 weight: 100
 description: >-
-     A way to export or import quantileTDigest states from/into ClickHouse.
+     A way to export or import quantileTDigest states from/into ClickHouse®
 ---
 
 ## quantileTDigestState

content/en/altinity-kb-functions/kurt_skew_statistics.md

@@ -1,5 +1,6 @@
 ---
-title: "kurt & skew statistical functions in ClickHouse"
+title: "kurt & skew statistical functions in ClickHouse®
+"
 linkTitle: "kurt & skew"
 weight: 100
 description: >-