From 413eb78af39ee9e91e5d5dec1b722735c9aeb9be Mon Sep 17 00:00:00 2001 From: Dale Mcdiarmid Date: Mon, 30 Dec 2024 15:58:39 +0000 Subject: [PATCH] more tags --- docs/en/integrations/data-ingestion/data-formats/binary.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/en/integrations/data-ingestion/data-formats/binary.md b/docs/en/integrations/data-ingestion/data-formats/binary.md index f9d7868ae55..871697c4088 100644 --- a/docs/en/integrations/data-ingestion/data-formats/binary.md +++ b/docs/en/integrations/data-ingestion/data-formats/binary.md @@ -3,6 +3,8 @@ sidebar_label: Binary and Native slug: /en/integrations/data-formats/binary-native --- +import CloudNotSupportedBadge from '@theme/badges/CloudNotSupportedBadge'; + # Using native and binary formats in ClickHouse ClickHouse supports multiple binary formats, which result in better performance and space efficiency. Binary formats are also safe in character encoding since data is saved in a binary form. @@ -166,6 +168,8 @@ FORMAT MsgPack ## Protocol Buffers + + To work with [Protocol Buffers](/docs/en/interfaces/formats.md/#protobuf) we first need to define a [schema file](assets/schema.proto): ```protobuf @@ -191,6 +195,8 @@ This saves data to the [proto.bin](assets/proto.bin) file. ClickHouse also suppo ## Cap’n Proto + + Another popular binary serialization format supported by ClickHouse is [Cap’n Proto](https://capnproto.org/). Similarly to `Protobuf` format, we have to define a schema file ([schema.capnp](assets/schema.capnp)) in our example: ```