id stringlengths 36 36 | document stringlengths 3 3k | metadata stringlengths 23 69 | embeddings listlengths 384 384 |
|---|---|---|---|
60fea322-bf4c-4a49-b9fa-2dc0585d3891 | |IPv6 |✔ |✔ |
|Object |✗ |✔ |
|Point |✔ |✔ |
|Nothing |✔ |✔ |
|MultiPolygon |✔ ... | {"source_file": "index.md"} | [
-0.008404366672039032,
0.020577218383550644,
-0.061440855264663696,
-0.02818080596625805,
-0.05130193009972572,
-0.01634921506047249,
-0.08616439998149872,
0.05550788715481758,
-0.008716101758182049,
-0.03697163611650467,
-0.0010163107654079795,
-0.01093334425240755,
-0.038041695952415466,
... |
683663bc-ae0f-4c30-8181-56996dded885 | ClickHouse Data Types
:::note
- AggregatedFunction - :warning: does not support
SELECT * FROM table ...
- Decimal -
SET output_format_decimal_trailing_zeros=1
in 21.9+ for consistency
- Enum - can be treated as both string and integer
- UInt64 - mapped to
long
in client-v1
:::
Features {#features}
Table of... | {"source_file": "index.md"} | [
-0.03514324501156807,
0.026939602568745613,
-0.056934963911771774,
0.06714755296707153,
-0.03455270454287529,
-0.015689672902226448,
-0.01073669083416462,
-0.018312273547053337,
0.020091090351343155,
-0.008307615295052528,
0.044653888791799545,
-0.09449347108602524,
0.09736808389425278,
-0... |
004a0293-905e-4993-b157-689ff299fda8 | ```
Configuring logging {#configuring-logging}
This is going to depend on the logging framework you are using. For example, if you are using
Logback
, you could configure logging in a file called
logback.xml
:
```xml title="logback.xml"
[%d{yyyy-MM-dd HH:mm:ss}] [%level] [%thread] %logger{36} - %msg%n
... | {"source_file": "index.md"} | [
0.01869801990687847,
0.03615571931004524,
-0.053874045610427856,
0.017838383093476295,
0.0016178456135094166,
-0.028991933912038803,
-0.006104946136474609,
0.03515171632170677,
0.056949928402900696,
0.019018283113837242,
0.038277506828308105,
-0.0103018032386899,
0.009172886610031128,
0.02... |
b9bea760-270b-42c7-90f2-4cabd6b15702 | sidebar_label: 'R2DBC Driver'
sidebar_position: 5
keywords: ['clickhouse', 'java', 'driver', 'integrate', 'r2dbc']
description: 'ClickHouse R2DBC Driver'
slug: /integrations/java/r2dbc
title: 'R2DBC driver'
doc_type: 'reference'
import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';
import CodeBlock ... | {"source_file": "r2dbc.md"} | [
-0.028124088421463966,
-0.05027095600962639,
-0.08337748795747757,
0.035315681248903275,
0.0072505418211221695,
0.026471110060811043,
0.041224535554647446,
0.04600473493337631,
-0.13515706360340118,
-0.07424328476190567,
0.009161802008748055,
-0.03857674449682236,
0.015559909865260124,
-0.... |
65b1d332-99ec-48dd-86d5-78822983d563 | slug: /integrations/s3/performance
sidebar_position: 2
sidebar_label: 'Optimizing for performance'
title: 'Optimizing for S3 Insert and Read Performance'
description: 'Optimizing the performance of S3 read and insert'
doc_type: 'guide'
keywords: ['s3', 'performance', 'optimization', 'object storage', 'data loading']
... | {"source_file": "performance.md"} | [
0.001134472549892962,
-0.0009356016525998712,
-0.06998753547668457,
0.017270460724830627,
0.03734198585152626,
-0.04272099584341049,
-0.011076747439801693,
0.05845081806182861,
-0.03786936029791832,
0.01504618488252163,
0.021931802853941917,
0.020203517749905586,
0.13620969653129578,
-0.07... |
b6776f1c-8e2d-4377-a5c6-c540682c21dc | ```bash
① Pull and parse the next portion of data and form an in-memory data block (one per partitioning key) from it.
② Write the block into a new part on storage.
Go to ①
```
In ①, the size depends on the insert block size, which can be controlled with two settings:
min_insert_block_size_rows
(default:
1... | {"source_file": "performance.md"} | [
-0.004419524688273668,
-0.030117949470877647,
-0.054742954671382904,
-0.01571212150156498,
-0.009702260605990887,
-0.07800404727458954,
0.0014407889684662223,
0.04250666871666908,
0.008842004463076591,
0.021812403574585915,
0.0598100945353508,
0.048210110515356064,
0.059120167046785355,
-0... |
31b561ea-5292-4735-9c42-4d3c1f92c488 | Table functions like s3 allow specifying sets of to-be-loaded-file names via glob patterns. When a glob pattern matches multiple existing files, ClickHouse can parallelize reads across and within these files and insert the data in parallel into a table by utilizing parallel running insert threads (per server):
Unt... | {"source_file": "performance.md"} | [
-0.041198767721652985,
-0.06372052431106567,
-0.08596455305814743,
-0.0142155010253191,
-0.010343728587031364,
-0.08907061815261841,
-0.0252086091786623,
-0.00860315840691328,
0.03380344808101654,
0.0836101844906807,
0.03614584729075432,
0.028988802805542946,
0.05365462228655815,
-0.094706... |
5c35358e-5bcc-413b-b6b2-acd58f49d742 | possible level of
insert parallelism
throughput of
background part merges
and, therefore, the overall ingest throughput.
Region locality {#region-locality}
Ensure your buckets are located in the same region as your ClickHouse instances. This simple optimization can dramatically improve throughput performanc... | {"source_file": "performance.md"} | [
-0.009065316990017891,
-0.05202711001038551,
-0.10578922927379608,
-0.08021888881921768,
0.013640687800943851,
-0.05239797756075859,
-0.04945869743824005,
-0.007210900075733662,
0.06339135020971298,
0.0065217399969697,
-0.008054039441049099,
0.008669252507388592,
-0.0005648824153468013,
-0... |
1d47750d-3777-485a-ac9c-728f0665b0d7 | This dataset consists of 189 Parquet files, with one for every month between July 2008 and March 2024.
Note that we use Parquet for performance, per our
recommendations above
, executing all queries on a ClickHouse Cluster located in the same region as the bucket. This cluster has 3 nodes, each with 32GiB of RAM an... | {"source_file": "performance.md"} | [
0.016644593328237534,
-0.046858612447977066,
-0.03561006113886833,
-0.032135091722011566,
-0.044961944222450256,
-0.07946301996707916,
0.03816918283700943,
-0.02620096132159233,
-0.018240660429000854,
0.04284770041704178,
0.056543633341789246,
-0.0391431525349617,
0.062449563294649124,
-0.... |
af75af57-f660-4856-bcd6-1a59ade1b84a | Usually, the default value of
max_threads
is sufficient, i.e., the number of cores. If the amount of memory used for a query is high, and this needs to be reduced, or the
LIMIT
on results is low, this value can be set lower. Users with plenty of memory may wish to experiment with increasing this value for possible ... | {"source_file": "performance.md"} | [
-0.035720836371183395,
-0.08284108340740204,
-0.10992590337991714,
-0.048167988657951355,
-0.010691949166357517,
-0.023367779329419136,
-0.05627286434173584,
0.01654588058590889,
0.03317577391862869,
0.021880825981497765,
0.014407621696591377,
0.06972677260637283,
0.013721299357712269,
-0.... |
976e49cb-09ab-4680-9b0f-01ae48da40fe | 5 rows in set. Elapsed: 1.505 sec. Processed 59.82 million rows, 24.03 GB (39.76 million rows/s., 15.97 GB/s.)
Peak memory usage: 178.58 MiB.
SETTINGS max_threads = 32
5 rows in set. Elapsed: 0.779 sec. Processed 59.82 million rows, 24.03 GB (76.81 million rows/s., 30.86 GB/s.)
Peak memory usage: 369.20 MiB.
SETT... | {"source_file": "performance.md"} | [
0.042195625603199005,
-0.017169974744319916,
-0.08547463268041611,
-0.010996241122484207,
-0.05974531173706055,
-0.05291253700852394,
-0.020351724699139595,
0.06389506906270981,
-0.053071342408657074,
0.026431478559970856,
-0.05931099131703377,
0.02470978908240795,
0.012210115790367126,
-0... |
de1e3fff-b62f-4037-b563-2efbe28168a2 | Using this formula with our earlier Stack Overflow example.
max_insert_threads=4
(8 cores per node)
peak_memory_usage_in_bytes
- 32 GiB (100% of node resources) or
34359738368
bytes.
min_insert_block_size_bytes
=
34359738368/(3*4) = 2863311530
```sql
INSERT INTO posts SELECT *
FROM s3('https://dataset... | {"source_file": "performance.md"} | [
-0.0117736691609025,
-0.05683232098817825,
-0.07924345880746841,
-0.022465592250227928,
-0.029737599194049835,
-0.09013700485229492,
-0.042228106409311295,
0.018285155296325684,
-0.003744180081412196,
0.03267880156636238,
-0.027940116822719574,
0.009924606420099735,
0.04183391109108925,
-0... |
62ae8259-08a8-48b2-86c6-9b9265d152ed | Utilizing a cluster for S3 reads requires using the
s3Cluster
function as described in
Utilizing Clusters
. This allows reads to be distributed across nodes.
The server that initially receives the insert query first resolves the glob pattern and then dispatches the processing of each matching file dynamically to... | {"source_file": "performance.md"} | [
-0.020085280761122704,
-0.09439072012901306,
-0.07787491381168365,
0.01679171249270439,
-0.017623024061322212,
-0.06025161221623421,
-0.029444735497236252,
-0.05541566386818886,
0.04522686079144478,
0.05436248332262039,
0.007812952622771263,
-0.004106317646801472,
0.09291170537471771,
-0.0... |
3626f682-98db-4738-972e-440571cc6f5d | 0 rows in set. Elapsed: 54.571 sec. Processed 59.82 million rows, 24.03 GB (1.10 million rows/s., 440.38 MB/s.)
Peak memory usage: 11.75 GiB.
```
As expected, this reduces insert performance by 3x.
Further tuning {#further-tuning}
Disable de-duplication {#disable-de-duplication}
Insert operations can sometimes ... | {"source_file": "performance.md"} | [
-0.015894724056124687,
-0.031461793929338455,
-0.007208433002233505,
0.0644145980477333,
-0.0803716704249382,
-0.07812124490737915,
0.01305557880550623,
-0.03717678785324097,
0.043720345944166183,
0.057552482932806015,
0.06309132277965546,
0.036871254444122314,
0.0656171515583992,
-0.12008... |
a9883f0b-f145-4e5e-84cd-3e69baead2b1 | ```sql
SELECT *
FROM s3Cluster('default', 'https://datasets-documentation.s3.eu-west-3.amazonaws.com/stackoverflow/parquet/posts/by_month/*.parquet')
SETTINGS parallel_distributed_insert_select = 2, min_insert_block_size_rows = 0, max_insert_threads = 4, min_insert_block_size_bytes = 2863311530, insert_deduplicate = 0,... | {"source_file": "performance.md"} | [
-0.05678914114832878,
-0.062413908541202545,
-0.08236684650182724,
-0.04214351624250412,
-0.03885519877076149,
-0.094223253428936,
-0.02923487313091755,
0.01284624170511961,
0.02008640393614769,
0.043259695172309875,
0.03294752165675163,
-0.0075724124908447266,
0.01784839667379856,
-0.1099... |
78114c18-01b3-4d9f-91ea-4441ebddeb3d | slug: /integrations/s3
sidebar_position: 1
sidebar_label: 'Integrating S3 with ClickHouse'
title: 'Integrating S3 with ClickHouse'
description: 'Page describing how to integrate S3 with ClickHouse'
keywords: ['Amazon S3', 'object storage', 'cloud storage', 'data lake', 'S3 integration']
doc_type: 'guide'
integration:
... | {"source_file": "index.md"} | [
0.015872633084654808,
0.007390670012682676,
-0.031268294900655746,
-0.04987509921193123,
0.07029746472835541,
-0.017587600275874138,
0.016771553084254265,
0.019366279244422913,
-0.03034220077097416,
0.004964344669133425,
0.026967164129018784,
-0.047476157546043396,
0.12768538296222687,
-0.... |
ecbd5c9c-dd1d-4fab-b143-de7b0bf8d938 | ```sql
DESCRIBE TABLE s3('https://datasets-documentation.s3.eu-west-3.amazonaws.com/nyc-taxi/trips_*.gz', 'TabSeparatedWithNames') SETTINGS describe_compact_output=1
┌─name──────────────────┬─type───────────────┐
│ trip_id │ Nullable(Int64) │
│ vendor_id │ Nullable(Int64) │
│ pickup_da... | {"source_file": "index.md"} | [
0.06331528723239899,
-0.0611739307641983,
-0.07324850559234619,
0.059414222836494446,
0.01884089596569538,
0.007783122360706329,
0.03839096799492836,
-0.024630675092339516,
-0.06667210906744003,
0.04588032513856888,
0.06603235751390457,
-0.05353935435414314,
0.004030691925436258,
-0.045776... |
f4a5cf76-7efd-47a4-8fbd-aa186902bc3c | sql
CREATE TABLE trips
(
`trip_id` UInt32,
`vendor_id` Enum8('1' = 1, '2' = 2, '3' = 3, '4' = 4, 'CMT' = 5, 'VTS' = 6, 'DDS' = 7, 'B02512' = 10, 'B02598' = 11, 'B02617' = 12, 'B02682' = 13, 'B02764' = 14, '' = 15),
`pickup_date` Date,
`pickup_datetime` DateTime,
`dropoff_date` Date,
`dropoff_dat... | {"source_file": "index.md"} | [
0.05478036776185036,
-0.014967425726354122,
-0.0390169695019722,
0.0376826673746109,
-0.06296306103467941,
-0.015843145549297333,
0.040226712822914124,
0.044907987117767334,
-0.03883081674575806,
0.06348885595798492,
0.10021739453077316,
-0.1203337088227272,
-0.0009971016552299261,
-0.0162... |
382901c0-0da3-4096-840c-c6237268e4b3 | Queries additionally support
virtual columns
, like
_path
and
_file
, that provide information regarding the bucket path and filename respectively. For example:
sql
SELECT _path, _file, trip_id
FROM s3('https://datasets-documentation.s3.eu-west-3.amazonaws.com/nyc-taxi/trips_0.gz', 'TabSeparatedWithNames')
LIMIT... | {"source_file": "index.md"} | [
0.03781596198678017,
-0.060264214873313904,
-0.0555591806769371,
0.01599602773785591,
0.03193839639425278,
-0.05327046662569046,
0.044283781200647354,
-0.022716926410794258,
0.0042019193060696125,
0.03440723940730095,
0.006710818037390709,
-0.030168116092681885,
0.015948833897709846,
-0.02... |
1e7b31d3-d985-49d4-88e5-d2384b9da5e1 | Remote Insert using ClickHouse Local {#remote-insert-using-clickhouse-local}
If network security policies prevent your ClickHouse cluster from making outbound connections, you can potentially insert S3 data using
clickhouse-local
. In the example below, we read from an S3 bucket and insert into ClickHouse using the ... | {"source_file": "index.md"} | [
0.040470559149980545,
-0.07656191289424896,
-0.12665845453739166,
0.01158574502915144,
-0.03781726956367493,
-0.0024969533551484346,
-0.021218128502368927,
-0.036352671682834625,
-0.012206957675516605,
0.028111733496189117,
-0.0014011544408276677,
-0.02753368578851223,
0.09790357947349548,
... |
5caca38c-a993-478d-86cf-643e26f27012 | Utilizing clusters {#utilizing-clusters}
The above functions are all limited to execution on a single node. Read speeds will scale linearly with CPU cores until other resources (typically network) are saturated, allowing users to vertically scale. However, this approach has its limitations. While users can alleviate ... | {"source_file": "index.md"} | [
-0.014459977857768536,
-0.062473833560943604,
-0.07247725874185562,
0.06749258190393448,
0.01459625456482172,
-0.08191614598035812,
-0.027151724323630333,
-0.0053045558743178844,
-0.01669655553996563,
0.02751643769443035,
-0.017759356647729874,
-0.00003853158341371454,
0.07945019751787186,
... |
38126c39-4c69-44bf-bea8-443fc0ab85a2 | Inserts will occur against the initiator node. This means that while reads will occur on each node, the resulting rows will be routed to the initiator for distribution. In high throughput scenarios, this may prove a bottleneck. To address this, set the parameter
parallel_distributed_insert_select
for the
s3cluster
... | {"source_file": "index.md"} | [
-0.030624259263277054,
-0.08253741264343262,
-0.09936565160751343,
0.014082199893891811,
-0.027263334020972252,
-0.07531314343214035,
-0.04823102056980133,
-0.02580287866294384,
0.016793807968497276,
0.028636347502470016,
-0.012642218731343746,
-0.017079954966902733,
0.11795669049024582,
-... |
0f88e52b-0e58-4296-8b0f-13a0a9a19c38 | sql
CREATE TABLE trips_raw
(
`trip_id` UInt32,
`vendor_id` Enum8('1' = 1, '2' = 2, '3' = 3, '4' = 4, 'CMT' = 5, 'VTS' = 6, 'DDS' = 7, 'B02512' = 10, 'B02598' = 11, 'B02617' = 12, 'B02682' = 13, 'B02764' = 14, '' = 15),
`pickup_date` Date,
`pickup_datetime` DateTime,... | {"source_file": "index.md"} | [
0.055880725383758545,
-0.010203063488006592,
-0.038123175501823425,
0.03788571059703827,
-0.056968506425619125,
-0.019468845799565315,
0.028072964400053024,
0.0459333173930645,
-0.03585420921444893,
0.0658552423119545,
0.10307788848876953,
-0.1284516453742981,
0.0003522765473462641,
-0.020... |
b9b99c06-a9ca-4544-a4f1-9d1148b22b01 | Inserting data {#inserting-data}
The
S3
table engine supports parallel reads. Writes are only supported if the table definition does not contain glob patterns. The above table, therefore, would block writes.
To demonstrate writes, create a table that points to a writable S3 bucket:
sql
CREATE TABLE trips_dest
(... | {"source_file": "index.md"} | [
-0.04676879197359085,
-0.06421243399381638,
-0.009038520976901054,
0.053167924284935,
-0.0381409116089344,
-0.04318975657224655,
0.0016355665866285563,
-0.006143076810985804,
-0.00277648470364511,
0.0545237734913826,
0.015849221497774124,
-0.036133747547864914,
0.03856785222887993,
-0.0542... |
d6b84772-9dfd-49a3-a15f-7f680453a749 | ALTER queries are not supported
SAMPLE operations are not supported
There is no notion of indexes, i.e. primary or skip.
Managing credentials {#managing-credentials}
In the previous examples, we have passed credentials in the
s3
function or
S3
table definition. While this may be acceptable for occasional ... | {"source_file": "index.md"} | [
-0.0018485257169231772,
-0.0020264333579689264,
-0.11343731731176376,
0.00045150131336413324,
-0.04903480038046837,
-0.025698192417621613,
-0.007034748326987028,
-0.05640041083097458,
0.029040301218628883,
0.027423573657870293,
0.031645193696022034,
-0.05094745382666588,
0.10563431680202484,... |
efe997b1-561b-49cb-8427-7b8093e31bea | For how to optimize reading and inserting using the S3 function, see the
dedicated performance guide
.
S3 storage tuning {#s3-storage-tuning}
Internally, the ClickHouse merge tree uses two primary storage formats:
Wide
and
Compact
. While the current implementation uses the default behavior of ClickHouse (contr... | {"source_file": "index.md"} | [
-0.019911497831344604,
-0.06367578357458115,
-0.08125962316989899,
0.015117575414478779,
0.03159867599606514,
-0.04343724623322487,
-0.0657539814710617,
0.02890453301370144,
0.004013873171061277,
0.020589925348758698,
0.003381956834346056,
0.060113128274679184,
0.05184704810380936,
-0.0696... |
305aa0cd-af44-485c-a066-252876f8ae74 | your_access_key_id
your_secret_access_key
/var/lib/clickhouse/disks/s3/
cache
s3
/var/lib/clickhouse/disks/s3_cache/
10Gi
...
```
A complete list of settings relevant to this disk declaration can be found
here
. Note that credentials can be managed here using the same approach... | {"source_file": "index.md"} | [
-0.0314062237739563,
-0.049286093562841415,
-0.10375025123357773,
-0.032707881182432175,
-0.0505891777575016,
-0.020024526864290237,
0.06381255388259888,
0.0036986477207392454,
0.02398429624736309,
0.06536940485239029,
0.010653002187609673,
0.0033239726908504963,
0.11807973682880402,
-0.04... |
ca0485ae-d278-4216-adb8-0c33e5ea79d1 | sql
SELECT passenger_count, avg(tip_amount) AS avg_tip, avg(total_amount) AS avg_amount FROM trips_s3 GROUP BY passenger_count;
Modifying a table {#modifying-a-table}
Occasionally users may need to modify the storage policy of a specific table. Whilst this is possible, it comes with limitations. The new target poli... | {"source_file": "index.md"} | [
0.06756274402141571,
-0.04630566015839577,
-0.011778108775615692,
0.043162260204553604,
-0.03096972405910492,
0.011458054184913635,
0.05660272762179375,
-0.021923307329416275,
-0.025290032848715782,
0.04268858954310417,
0.1064310222864151,
-0.052261851727962494,
0.12105214595794678,
-0.032... |
18709ba3-27ca-4e97-bab4-f06c7c0acb12 | Reads on S3 are asynchronous by default. This behavior is determined by setting
remote_filesystem_read_method
, set to the value
threadpool
by default. When serving a request, ClickHouse reads granules in stripes. Each of these stripes potentially contain many columns. A thread will read the columns for their granul... | {"source_file": "index.md"} | [
0.016697494313120842,
-0.06818220764398575,
-0.14049546420574188,
-0.010753168724477291,
-0.013400426134467125,
-0.06767261028289795,
-0.03849248215556145,
-0.006009120959788561,
0.0787605494260788,
0.05824493616819382,
-0.009419292211532593,
0.0886620506644249,
0.00555848004296422,
-0.092... |
3916e68c-8292-4ca9-b86b-e760b69ef651 | The configuration shown above is for ClickHouse version 22.8 or higher, if you are using an older version please see the
storing data
docs.
For more information about using S3:
Integrations Guide:
S3 Backed MergeTree
:::
Update the owner of the file to the
clickhouse
user and group
bash
chown clickhouse:cl... | {"source_file": "index.md"} | [
0.017308993265032768,
-0.11887895315885544,
-0.08667565882205963,
-0.038906343281269073,
-0.04200239107012749,
0.006059219129383564,
0.014626402407884598,
-0.03723280504345894,
0.008274937979876995,
0.05461946874856949,
0.05116885527968407,
0.020876454189419746,
0.10955307632684708,
-0.063... |
aecb3eb2-4735-4381-b796-7e6087e0493d | Deploy ClickHouse {#deploy-clickhouse}
Deploy ClickHouse on two hosts, in the sample configurations these are named
chnode1
,
chnode2
.
Place
chnode1
in one AWS region, and
chnode2
in a second.
Deploy ClickHouse Keeper {#deploy-clickhouse-keeper}
Deploy ClickHouse Keeper on three hosts, in the sample conf... | {"source_file": "index.md"} | [
0.045890457928180695,
-0.06533447653055191,
-0.04160638898611069,
-0.0616028793156147,
0.013873878866434097,
-0.06808814406394958,
0.028142403811216354,
-0.1115696132183075,
-0.016529886052012444,
0.05200740322470665,
0.025372352451086044,
-0.10554572939872742,
0.09558316320180893,
-0.0551... |
98ef33bf-3308-4d87-b4fe-f73fb9102ea1 | server_id
indicates the ID to be assigned to the host where the configuration files is used. In the example below, the
server_id
is
3
, and if you look further down in the file in the
<raft_configuration>
section, you will see that server 3 has the hostname
keepernode3
. This is how the ClickHouse Keeper proce... | {"source_file": "index.md"} | [
-0.0068646809086203575,
-0.015175621025264263,
-0.09718988835811615,
-0.034382414072752,
0.0378170870244503,
-0.10796960443258286,
0.061201080679893494,
-0.08168456703424454,
0.05824695900082588,
0.018620328977704048,
0.04791347309947014,
0.030603397637605667,
0.07195787876844406,
-0.02419... |
c5f97ce8-2401-4866-a6e2-e631f850b24a | xml title="/etc/clickhouse-server/config.d/macros.xml"
<clickhouse>
<distributed_ddl>
<path>/clickhouse/task_queue/ddl</path>
</distributed_ddl>
<macros>
<cluster>cluster_1S_2R</cluster>
<shard>1</shard>
<replica>replica_1</replica>
</macros>
</clickhouse>
:::note
Th... | {"source_file": "index.md"} | [
-0.001708306255750358,
-0.09967100620269775,
-0.03650985658168793,
-0.04966038092970848,
0.027069998905062675,
-0.03566223755478859,
-0.035032179206609726,
-0.08377476781606674,
0.023152528330683708,
0.036148712038993835,
0.03877847641706467,
0.0012187790125608444,
0.10980721563100815,
-0.... |
aa37ab2e-17dc-42a7-8413-944277d93e44 | bash
sudo systemctl enable clickhouse-keeper
sudo systemctl start clickhouse-keeper
sudo systemctl status clickhouse-keeper
Check ClickHouse Keeper status {#check-clickhouse-keeper-status}
Send commands to the ClickHouse Keeper with
netcat
. For example,
mntr
returns the state of the ClickHouse Keeper cluster. ... | {"source_file": "index.md"} | [
0.01141019631177187,
-0.01797967217862606,
-0.09789907187223434,
-0.017868928611278534,
0.043619245290756226,
-0.07216215878725052,
0.018498580902814865,
-0.05755414441227913,
-0.04188352823257446,
0.07016335427761078,
0.021111799404025078,
-0.052889592945575714,
0.06981032341718674,
-0.04... |
06ca1d39-2976-4ebc-8313-68406a1739de | Understand the use of the macros defined earlier
The macros
shard
, and
replica
were
defined earlier
, and in the highlighted line below you can see where the values are substituted on each ClickHouse node. Additionally, the value
uuid
is used;
uuid
is not defined in the macros as it is generated by the sy... | {"source_file": "index.md"} | [
0.01696496456861496,
-0.010503619909286499,
-0.019679764285683632,
0.08095870912075043,
-0.034373823553323746,
-0.013280916027724743,
0.08104463666677475,
0.024604231119155884,
-0.021128611639142036,
0.020644310861825943,
0.05985771864652634,
-0.07401207089424133,
0.04180535674095154,
-0.0... |
9db0a7c2-7575-4082-8986-f885e996daec | 1 row in set. Elapsed: 0.009 sec.
```
Check the size of data on the local disk. From above, the size on disk for the millions of rows stored is 36.42 MiB. This should be on S3, and not the local disk. The query above also tells us where on local disk data and metadata is stored. Check the local data:
respons... | {"source_file": "index.md"} | [
-0.024822663515806198,
-0.04242565482854843,
-0.09525734931230545,
0.003283452009782195,
0.060624174773693085,
-0.05101938173174858,
-0.03578254580497742,
-0.05242651328444481,
0.05008507892489433,
0.07029645889997482,
0.023026026785373688,
-0.001650211401283741,
0.10435553640127182,
-0.07... |
9895848a-2ba0-4e55-b381-46f52626536a | Backups {#backups}
It is possible to store a backup on the disk we created above:
``` sql
BACKUP TABLE t TO Disk('s3_express', 't.zip')
┌─id───────────────────────────────────┬─status─────────┐
│ c61f65ac-0d76-4390-8317-504a30ba7595 │ BACKUP_CREATED │
└──────────────────────────────────────┴────────────────┘
```
... | {"source_file": "index.md"} | [
-0.09902329742908478,
-0.05379851907491684,
-0.07781081646680832,
0.05399532988667488,
0.03529315069317818,
0.01860906183719635,
0.034793782979249954,
0.014784798957407475,
-0.007460394874215126,
0.07573127001523972,
0.010007449425756931,
0.04128633067011833,
0.1286901831626892,
-0.0376574... |
1bad7593-f187-41e9-a71d-eeefec229194 | sidebar_label: 'Azure Synapse'
slug: /integrations/azure-synapse
description: 'Introduction to Azure Synapse with ClickHouse'
keywords: ['clickhouse', 'azure synapse', 'azure', 'synapse', 'microsoft', 'azure spark', 'data']
title: 'Integrating Azure Synapse with ClickHouse'
doc_type: 'guide'
import TOCInline from '... | {"source_file": "index.md"} | [
-0.06322115659713745,
-0.07888983190059662,
-0.03495771437883377,
0.08227387070655823,
0.03274975344538689,
0.003523959079757333,
0.10061003267765045,
-0.021327616646885872,
-0.04126721993088722,
0.06470050662755966,
0.014587628655135632,
0.02433004602789879,
0.0711878165602684,
-0.0137210... |
6f89153c-9a5a-4911-9142-c736fe09c3dd | Make sure it will be in the first cell as follows:
Please visit the
ClickHouse Spark configurations page
for additional settings.
:::info
When working with ClickHouse Cloud Please make sure to set the
required Spark settings
.
:::
Setup verification {#setup-verification}
To verify that the dependencies an... | {"source_file": "index.md"} | [
0.007146070711314678,
-0.10668660700321198,
0.008160402998328209,
0.0008100806153379381,
-0.012838169001042843,
-0.041100457310676575,
0.025906072929501534,
-0.06385369598865509,
0.031065942719578743,
0.033458828926086426,
-0.0021682411897927523,
-0.00797728355973959,
-0.032122839242219925,
... |
2da893aa-0268-43ea-812f-a9c7471de631 | sidebar_label: 'Amazon Glue'
sidebar_position: 1
slug: /integrations/glue
description: 'Integrate ClickHouse and Amazon Glue'
keywords: ['clickhouse', 'amazon', 'aws', 'glue', 'migrating', 'data', 'spark']
title: 'Integrating Amazon Glue with ClickHouse and Spark'
doc_type: 'guide'
import Image from '@theme/IdealIm... | {"source_file": "index.md"} | [
-0.028107671067118645,
-0.027733201161026955,
-0.03441591560840607,
0.01760045811533928,
0.04924991726875305,
0.008617687970399857,
0.04090264439582825,
0.028401561081409454,
-0.07636748254299164,
0.015794947743415833,
0.09203961491584778,
0.0408962108194828,
0.06528247147798538,
-0.025427... |
fdad6bce-b8ba-4449-acdb-b9450185e901 | Examples {#example}
```java
import com.amazonaws.services.glue.GlueContext
import com.amazonaws.services.glue.util.GlueArgParser
import com.amazonaws.services.glue.util.Job
import com.clickhouseScala.Native.NativeSparkRead.spark
import org.apache.spark.sql.SparkSession
import scala.collection.JavaConverters.
i... | {"source_file": "index.md"} | [
-0.01766929030418396,
-0.09260059893131256,
-0.01117345504462719,
0.0026598055846989155,
-0.03531274572014809,
-0.0165999922901392,
0.04662603512406349,
-0.04391257464885712,
-0.07057148963212967,
-0.050394147634506226,
-0.00624499237164855,
-0.029318824410438538,
-0.0072359442710876465,
-... |
192494ec-fe52-4b28-b334-861410dc2422 | @params: [JOB_NAME]
args = getResolvedOptions(sys.argv, ['JOB_NAME'])
sc = SparkContext()
glueContext = GlueContext(sc)
logger = glueContext.get_logger()
spark = glueContext.spark_session
job = Job(glueContext)
job.init(args['JOB_NAME'], args)
spark.conf.set("spark.sql.catalog.clickhouse", "com.clickhouse.spark.C... | {"source_file": "index.md"} | [
-0.024127546697854996,
-0.10180345922708511,
-0.04519842192530632,
0.0017192888772115111,
-0.028015581890940666,
-0.05324435234069824,
0.1141531690955162,
-0.028651252388954163,
-0.12961512804031372,
-0.06135951355099678,
-0.00818453636020422,
-0.022430524230003357,
-0.001711785327643156,
... |
c4addbf8-1e49-42fd-89f1-a411dbfa3681 | slug: /integrations/clickpipes/secure-kinesis
sidebar_label: 'Kinesis Role-Based Access'
title: 'Kinesis Role-Based Access'
description: 'This article demonstrates how ClickPipes customers can leverage role-based access to authenticate with Amazon Kinesis and access their data streams securely.'
doc_type: 'guide'
keywo... | {"source_file": "secure-kinesis.md"} | [
-0.048599690198898315,
0.03605234622955322,
-0.05228080600500107,
-0.07834146171808243,
0.027764111757278442,
-0.018408216536045074,
0.07503955066204071,
0.025241674855351448,
0.02761978469789028,
0.004243857692927122,
0.019607698544859886,
0.03630100563168526,
0.08432299643754959,
-0.0347... |
6d129a68-a252-4f0c-9b58-e65c467bdb9e | json
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"kinesis:DescribeStream",
"kinesis:GetShardIterator",
"kinesis:GetRecords",
"kinesis:ListShards",
"kinesis:RegisterStreamConsumer",
"kin... | {"source_file": "secure-kinesis.md"} | [
-0.05954039841890335,
0.0665617361664772,
0.01540422160178423,
-0.039942603558301926,
0.018621528521180153,
0.010134067386388779,
0.01070514414459467,
-0.021997682750225067,
0.02797202579677105,
-0.008062331937253475,
0.021699562668800354,
-0.059524111449718475,
0.004974666051566601,
0.034... |
8771c328-b87a-4bd2-b92f-dfa7a1674892 | sidebar_label: 'AWS PrivateLink for ClickPipes'
description: 'Establish a secure connection between ClickPipes and a data source using AWS PrivateLink.'
slug: /integrations/clickpipes/aws-privatelink
title: 'AWS PrivateLink for ClickPipes'
doc_type: 'guide'
keywords: ['aws privatelink', 'ClickPipes security', 'vpc endp... | {"source_file": "aws-privatelink.md"} | [
-0.07024497538805008,
0.03797748684883118,
-0.09252719581127167,
0.00723047461360693,
0.05539313331246376,
-0.025597725063562393,
0.07996948063373566,
0.05647630617022514,
-0.027674967423081398,
0.0008507882594130933,
0.0699164867401123,
-0.04461425170302391,
0.08608148247003555,
-0.041503... |
3f8c46a7-61f5-4f5a-ab5a-2f78b3171c04 | Resource-Gateway is the point that receives traffic for specified resources in your VPC.
You can create a Resource-Gateway from the
AWS console
or with the following command:
bash
aws vpc-lattice create-resource-gateway \
--vpc-identifier <VPC_ID> \
--subnet-ids <SUBNET_IDS> \
--security-group-ids <SG... | {"source_file": "aws-privatelink.md"} | [
-0.012118922546505928,
-0.03539285063743591,
-0.09631060808897018,
0.040651675313711166,
0.03498246893286705,
0.017613032832741737,
0.08057399094104767,
-0.06673175096511841,
0.050778742879629135,
0.02036456950008869,
-0.06823252141475677,
-0.028184156864881516,
0.06041138991713524,
0.0182... |
532492b8-0de4-405d-baa1-606464675de9 | For more details on PrivateLink with VPC resource, see
AWS documentation
.
MSK multi-VPC connectivity {#msk-multi-vpc}
The
Multi-VPC connectivity
is a built-in feature of AWS MSK that allows you to connect multiple VPCs to a single MSK cluster.
Private DNS support is out of the box and does not require any addit... | {"source_file": "aws-privatelink.md"} | [
-0.08282767236232758,
-0.0448426753282547,
-0.05875227600336075,
0.03946591913700104,
0.015845656394958496,
0.08694595098495483,
-0.036294933408498764,
-0.006411103531718254,
0.0437290258705616,
0.01565873809158802,
-0.04512189328670502,
-0.05647877976298332,
0.03730669245123863,
-0.022378... |
ade6488e-69eb-4621-9148-0829068fa5e5 | Click on
Create
and wait for the reverse private endpoint to be ready.
If you are creating a new endpoint, it will take some time to set up the endpoint.
The page will refresh automatically once the endpoint is ready.
VPC endpoint service might require accepting the connection request in your AWS console.
... | {"source_file": "aws-privatelink.md"} | [
-0.0685780867934227,
-0.05911081284284592,
-0.04730496555566788,
-0.0038697486743330956,
-0.06320413202047348,
0.026053884997963905,
-0.04588231444358826,
-0.04534061625599861,
0.08867637813091278,
0.08490289747714996,
-0.003804972628131509,
-0.03995930776000023,
-0.00006749379099346697,
-... |
68e467a4-687a-48d6-96dd-69627260a0c5 | sidebar_label: 'Introduction'
description: 'Seamlessly connect your external data sources to ClickHouse Cloud.'
slug: /integrations/clickpipes
title: 'Integrating with ClickHouse Cloud'
doc_type: 'guide'
keywords: ['ClickPipes', 'data ingestion platform', 'streaming data', 'integration platform', 'ClickHouse Cloud']
... | {"source_file": "index.md"} | [
-0.01602867618203163,
-0.0025161830708384514,
-0.07842697203159332,
-0.005566952750086784,
0.03298851102590561,
-0.026588037610054016,
-0.01027577742934227,
0.0038128907326608896,
0.005342146847397089,
0.05932556465268135,
0.004007462877780199,
-0.04885541647672653,
0.006290022749453783,
-... |
c5c61d5d-7a26-4d50-9243-2313c0636c12 | | Name | Logo |Type| Status | Description |
|--------------------------------------... | {"source_file": "index.md"} | [
-0.0023011094890534878,
0.08496814221143723,
-0.015909554436802864,
0.003183495718985796,
-0.03347279876470566,
0.0332457609474659,
0.024602554738521576,
-0.0024384886492043734,
0.014942298643290997,
-0.04490828514099121,
0.019827865064144135,
-0.013515936210751534,
0.003529396140947938,
-... |
54b9e88d-3eac-4310-abc3-39ed2bf59267 | |
Postgres
|
|DBMS| Stable | Configure ClickPipes and start ingesting data from Postgres into ClickHouse Cloud. |
|
MySQL
|
|DBMS| Public Beta | Configure ClickPipes and start ingesting data from MySQL into ClickHouse Cloud. |
|
... | {"source_file": "index.md"} | [
0.0610540509223938,
-0.06997683644294739,
-0.07221432775259018,
0.026136605069041252,
-0.05259745940566063,
-0.024358537048101425,
0.017107727006077766,
-0.007142254617065191,
-0.055363502353429794,
0.051110927015542984,
-0.014374601654708385,
0.004518364556133747,
-0.014481360092759132,
-... |
14d9dd24-be70-4e97-aa5c-874c4144738a | More connectors will get added to ClickPipes, you can find out more by
contacting us
.
List of Static IPs {#list-of-static-ips}
The following are the static NAT IPs (separated by region) that ClickPipes uses to connect to your external services. Add your related instance region IPs to your IP allow list to allow t... | {"source_file": "index.md"} | [
0.002074645832180977,
-0.09304314851760864,
-0.030366308987140656,
-0.11124023050069809,
-0.029088299721479416,
-0.0002374998148297891,
-0.0037464573979377747,
-0.07661928236484528,
0.016055794432759285,
0.042883943766355515,
-0.016623618081212044,
0.008610249496996403,
-0.00636881310492754,... |
e4ab3143-6bba-4ac5-8432-396c94259b5c | Adjusting ClickHouse settings {#adjusting-clickhouse-settings}
ClickHouse Cloud provides sensible defaults for most of the use cases. However, if you need to adjust some ClickHouse settings for the ClickPipes destination tables, a dedicated role for ClickPipes is the most flexible solution.
Steps:
1. create a custom ... | {"source_file": "index.md"} | [
0.045539651066064835,
-0.04778781533241272,
-0.03168172761797905,
0.0071301767602562904,
-0.11358106136322021,
0.02147815190255642,
0.035486575216054916,
0.026581309735774994,
-0.05520322918891907,
0.04518330469727516,
-0.009569770656526089,
-0.06765013188123703,
0.019955968484282494,
0.01... |
5d0a7f8c-2ad0-4791-b3cb-48e66dd791f4 | Error reporting {#error-reporting}
ClickPipes will store errors in two separate tables depending on the type of error encountered during the ingestion process.
Record Errors {#record-errors}
ClickPipes will create a table next to your destination table with the postfix
<destination_table_name>_clickpipes_error
.... | {"source_file": "index.md"} | [
-0.017667310312390327,
-0.042209744453430176,
-0.04052445665001869,
0.024753274396061897,
-0.02201310358941555,
-0.042476553469896317,
0.034949637949466705,
0.02971816062927246,
0.0032523691188544035,
-0.01132469717413187,
-0.02940717712044716,
0.015512604266405106,
0.09869881719350815,
-0... |
5d8a80fe-72da-4d60-a339-2b4a5e7d7810 | sidebar_label: 'ClickPipes for Amazon Kinesis'
description: 'Seamlessly connect your Amazon Kinesis data sources to ClickHouse Cloud.'
slug: /integrations/clickpipes/kinesis
title: 'Integrating Amazon Kinesis with ClickHouse Cloud'
doc_type: 'guide'
integration:
- support_level: 'core'
- category: 'clickpipes'
keyw... | {"source_file": "kinesis.md"} | [
-0.019925571978092194,
-0.007701018359512091,
-0.026187989860773087,
-0.07804466784000397,
0.03368698060512543,
0.0016887221718207002,
0.01943003199994564,
0.03783450275659561,
-0.030729319900274277,
0.00835167896002531,
0.05436643958091736,
-0.05775955319404602,
0.054609011858701706,
-0.0... |
49ff5938-a3cf-4013-b4a5-2aa30bd371e7 | In the next step, you can select whether you want to ingest data into a new ClickHouse table or reuse an existing one. Follow the instructions in the screen to modify your table name, schema, and settings. You can see a real-time preview of your changes in the sample table at the top.
You can also customize the a... | {"source_file": "kinesis.md"} | [
0.052270520478487015,
-0.10128866881132126,
-0.10432609170675278,
0.028461024165153503,
-0.057224709540605545,
-0.03659283369779587,
0.05894862860441208,
-0.0074569969438016415,
-0.10091226547956467,
0.02463790588080883,
0.01846383512020111,
-0.10445856302976608,
0.05573863536119461,
-0.01... |
80454871-0844-4d96-adbe-46d9ffad0e0a | JSON type support {#json-type-support}
JSON fields that are always a JSON object can be assigned to a JSON destination column. You will have to manually change the destination
column to the desired JSON type, including any fixed or skipped paths.
Kinesis virtual columns {#kinesis-virtual-columns}
The following ... | {"source_file": "kinesis.md"} | [
0.028279049322009087,
-0.0060568926855921745,
-0.05876586586236954,
-0.042186129838228226,
-0.02087518945336342,
0.007423992734402418,
-0.06729382276535034,
0.03504649177193642,
0.00963850598782301,
0.03624911233782768,
0.044127341359853745,
-0.04280361905694008,
-0.012091526761651039,
0.0... |
08bfc044-7681-4f61-8c61-1531d509f35d | ClickPipes provides high-availability with an availability zone distributed architecture.
This requires scaling to at least two consumers.
Regardless number of running consumers, fault tolerance is available by design.
If a consumer or its underlying infrastructure fails,
the ClickPipe will automatically restart the ... | {"source_file": "kinesis.md"} | [
-0.003757153172045946,
-0.05346239358186722,
-0.053561389446258545,
-0.08034518361091614,
0.0009707316639833152,
0.004489259794354439,
-0.00006516816938528791,
-0.01212323922663927,
0.0041707721538841724,
0.03352038934826851,
-0.02183232456445694,
0.0008629861404187977,
0.02753058448433876,
... |
fa28bd0f-a845-4def-a6f9-0b31e4b9ebf5 | slug: /integrations/clickpipes/secure-rds
sidebar_label: 'AWS IAM DB Authentication (RDS/Aurora)'
title: 'AWS IAM DB Authentication (RDS/Aurora)'
description: 'This article demonstrates how ClickPipes customers can leverage role-based access to authenticate with Amazon RDS/Aurora and access their database securely.'
do... | {"source_file": "secure-rds.md"} | [
-0.03294898569583893,
0.00270683947019279,
-0.1235264465212822,
-0.02743079513311386,
-0.04103899002075195,
-0.03547709062695503,
0.07292696088552475,
-0.022852523252367973,
-0.0010043452493846416,
0.0306253544986248,
-0.02475023828446865,
0.015788253396749496,
0.09533143043518066,
-0.0189... |
c09a60f4-0398-441d-bffe-f169f7e5217e | Follow the rest of the steps in the
PostgreSQL source setup guide
to configure your RDS instance for ClickPipes.
MySQL / MariaDB {#setting-up-the-database-user-mysql}
Connect to your RDS/Aurora instance and create a new database user with the following command:
sql
CREATE USER 'clickpipes_iam_user' I... | {"source_file": "secure-rds.md"} | [
0.01957061141729355,
-0.07751242816448212,
-0.07375897467136383,
-0.006454617250710726,
-0.1310502141714096,
0.030380750074982643,
0.04868858680129051,
0.009632417932152748,
-0.01696654222905636,
0.041698239743709564,
-0.04556842893362045,
-0.05752778798341751,
0.0455716997385025,
0.002942... |
5df65166-7012-4ed3-8654-a7e8afd852a4 | sidebar_label: 'Spark JDBC'
sidebar_position: 3
slug: /integrations/apache-spark/spark-jdbc
description: 'Introduction to Apache Spark with ClickHouse'
keywords: ['clickhouse', 'Apache Spark', 'jdbc', 'migrating', 'data']
title: 'Spark JDBC'
doc_type: 'guide'
import Tabs from '@theme/Tabs';
import TabItem from '@th... | {"source_file": "spark-jdbc.md"} | [
-0.018169673159718513,
-0.03515166416764259,
-0.04797391593456268,
0.0021835055667907,
-0.03778291121125221,
0.035414207726716995,
0.07985860854387283,
0.035493385046720505,
-0.10458015650510788,
-0.060569439083337784,
-0.008554324507713318,
0.025770023465156555,
-0.002853120444342494,
-0.... |
f4679059-1d17-4567-97df-1ef0e32f87ab | val df1: Dataset[Row] = spark.read.
jdbc(jdbcURL, s"($query)", connectionProperties)
df1.show()
//---------------------------------------------------------------------------------------------------
// Load the table from ClickHouse using load method
//--------------------------------------------------------... | {"source_file": "spark-jdbc.md"} | [
0.02020365372300148,
-0.07552370429039001,
-0.05971699580550194,
-0.0022065159864723682,
-0.056339334696531296,
-0.02132423035800457,
0.03974746912717819,
-0.00791400671005249,
-0.05146854743361473,
-0.04652232676744461,
-0.015555666759610176,
-0.029980238527059555,
-0.02899828925728798,
-... |
ffed9ceb-a767-4bb5-8450-6d75e643cf22 | df.write()
.mode(SaveMode.Append)
.jdbc(jdbcUrl, "example_table", jdbcProperties);
//---------------------------------------------------------------------------------------------------
// Write the df to ClickHouse using the save method
//--------------------------------------------... | {"source_file": "spark-jdbc.md"} | [
0.06588252633810043,
-0.08601310104131699,
-0.0963679850101471,
0.03167347237467766,
-0.0029046994168311357,
-0.006444786675274372,
-0.01755131594836712,
-0.010691928677260876,
-0.03046325407922268,
0.0751401036977768,
0.045387957245111465,
0.003744145156815648,
-0.0254853293299675,
-0.116... |
73838ff0-36b4-42f4-963f-79c3d5080a9b | }
```
```python
from pyspark.sql import SparkSession
from pyspark.sql import Row
jar_files = [
"jars/clickhouse-jdbc-X.X.X-SNAPSHOT-all.jar"
]
Initialize Spark session with JARs
spark = SparkSession.builder \
.appName("example") \
.master("local") \
.config("spark.jars", ",".join(jar_files))... | {"source_file": "spark-jdbc.md"} | [
0.006144715938717127,
-0.02493959292769432,
-0.033664505928754807,
-0.0381767563521862,
-0.009895369410514832,
-0.00454673869535327,
0.061197374016046524,
0.03985253721475601,
-0.04309697449207306,
0.00022331280342768878,
0.007164272479712963,
0.01564701646566391,
-0.03313741087913513,
-0.... |
bb40029d-4460-40a8-a3b7-be1fa00d4d40 | sidebar_label: 'Integrating Apache Spark with ClickHouse'
sidebar_position: 1
slug: /integrations/apache-spark
description: 'Introduction to Apache Spark with ClickHouse'
keywords: ['clickhouse', 'Apache Spark', 'migrating', 'data']
title: 'Integrating Apache Spark with ClickHouse'
doc_type: 'guide'
integration:
- su... | {"source_file": "index.md"} | [
-0.060478344559669495,
-0.08737332373857498,
-0.028488436713814735,
0.01598322205245495,
0.004176905378699303,
-0.001008995226584375,
0.03402914106845856,
-0.008922520093619823,
-0.12088850140571594,
-0.05145736783742905,
0.028758924454450607,
-0.012030680663883686,
0.0020187224727123976,
... |
6a6680c0-b4fa-4b0d-a124-ca2fed6e5818 | sidebar_label: 'Spark Native Connector'
sidebar_position: 2
slug: /integrations/apache-spark/spark-native-connector
description: 'Introduction to Apache Spark with ClickHouse'
keywords: ['clickhouse', 'Apache Spark', 'migrating', 'data']
title: 'Spark Connector'
doc_type: 'guide'
import Tabs from '@theme/Tabs';
imp... | {"source_file": "spark-native-connector.md"} | [
-0.02634325809776783,
-0.12487467378377914,
-0.038452792912721634,
0.016042428091168404,
0.013150216080248356,
-0.00022268184693530202,
0.039063189178705215,
0.01651417650282383,
-0.06722905486822128,
-0.01276389230042696,
0.02093014493584633,
0.03282379359006882,
-0.02005622163414955,
-0.... |
733dcd63-98f2-4b6f-9da6-67ad79b70379 | Import as a Dependency {#import-as-a-dependency}
maven
<dependency>
<groupId>com.clickhouse.spark</groupId>
<artifactId>clickhouse-spark-runtime-{{ spark_binary_version }}_{{ scala_binary_version }}</artifactId>
<version>{{ stable_version }}</version>
</dependency>
<dependency>
<groupId>com.clickhouse</gr... | {"source_file": "spark-native-connector.md"} | [
-0.03726492449641228,
-0.007611290086060762,
-0.03348604589700699,
-0.07803358882665634,
0.025659797713160515,
-0.024867448955774307,
-0.02588704600930214,
-0.061846766620874405,
-0.08529379218816757,
-0.05053872615098953,
-0.005923587363213301,
-0.06085629016160965,
-0.016537301242351532,
... |
b12e32ee-d07d-49fa-9a8a-039b216a64c2 | :::important
It's essential to include the
clickhouse-jdbc JAR
with the "all" classifier,
as the connector relies on
clickhouse-http
and
clickhouse-client
— both of which are bundled
in clickhouse-jdbc:all.
Alternatively, you can add
clickhouse-client JAR
and
clickhouse-http
individually if you
prefer not to ... | {"source_file": "spark-native-connector.md"} | [
-0.015418869443237782,
-0.10787084698677063,
-0.03294406458735466,
-0.005618101917207241,
-0.029166636988520622,
0.001388657372444868,
-0.01121821254491806,
-0.03645603731274605,
-0.06859876960515976,
-0.021811045706272125,
-0.01497447956353426,
-0.044516950845718384,
-0.04542076215147972,
... |
f65a2427-3aca-4a1d-a456-e5ac1288a063 | spark.sql.catalog.clickhouse2 com.clickhouse.spark.ClickHouseCatalog
spark.sql.catalog.clickhouse2.host 10.0.0.2
spark.sql.catalog.clickhouse2.protocol https
spark.sql.catalog.clickhouse2.http_port 8443
spark.sql.catalog.clickhouse2.user default
spark.sql.catalog.clickhouse... | {"source_file": "spark-native-connector.md"} | [
0.006784528493881226,
-0.10410551726818085,
-0.05876794457435608,
0.010928669944405556,
-0.06372544914484024,
-0.018307771533727646,
0.023183472454547882,
-0.09006168693304062,
-0.025681260973215103,
-0.050500694662332535,
0.01452060416340828,
-0.01576344482600689,
0.039438072592020035,
-0... |
830dfc67-6649-41d2-b48a-3429ea559ffd | val df = spark.sql("select * from clickhouse.default.example_table")
df.show()
spark.stop()
}
```
```python
from pyspark.sql import SparkSession
packages = [
"com.clickhouse.spark:clickhouse-spark-runtime-3.4_2.12:0.8.0",
"com.clickhouse:clickhouse-client:0.7.0",
"com.clickhouse:clickhouse-http-... | {"source_file": "spark-native-connector.md"} | [
0.05787458270788193,
-0.11853189766407013,
-0.016164084896445274,
-0.009831958450376987,
0.037645697593688965,
-0.04554164782166481,
0.06911156326532364,
-0.027616165578365326,
-0.04907021299004555,
-0.012549815699458122,
-0.002599631668999791,
-0.019944684579968452,
-0.04002811387181282,
... |
c9115156-e76e-4400-9a9c-11a1e30ce5ea | // Create a DataFrame
Dataset<Row> df = spark.createDataFrame(data, schema);
df.writeTo("clickhouse.default.example_table").append();
spark.stop();
}
```
```java
object NativeSparkWrite extends App {
// Create a Spark session
val spark: SparkSession = SparkSession.builder
.appName("exampl... | {"source_file": "spark-native-connector.md"} | [
0.0659298375248909,
-0.09813607484102249,
-0.04485435411334038,
-0.04244364798069,
-0.010769369080662727,
-0.022898007184267044,
0.033730339258909225,
0.00972127728164196,
-0.06364089995622635,
0.045289959758520126,
0.0016965094255283475,
-0.022961273789405823,
-0.03395967558026314,
-0.032... |
a0a2c7a3-1a4c-4962-9481-e57e809795a9 | ```
DDL operations {#ddl-operations}
You can perform DDL operations on your ClickHouse instance using Spark SQL, with all changes immediately persisted in
ClickHouse.
Spark SQL allows you to write queries exactly as you would in ClickHouse,
so you can directly execute commands such as CREATE TABLE, TRUNCATE, an... | {"source_file": "spark-native-connector.md"} | [
-0.02485782653093338,
-0.07581445574760437,
0.0005597694544121623,
0.03254486620426178,
-0.06513481587171555,
-0.05986679345369339,
0.0545123890042305,
0.012599274516105652,
-0.062272559851408005,
0.005999444052577019,
0.026362217962741852,
0.06472893804311752,
-0.020189456641674042,
-0.06... |
4b0d462c-3edc-4c15-a431-e89b3c957ede | | Key | Default | Description ... | {"source_file": "spark-native-connector.md"} | [
0.015752343460917473,
0.03157888725399971,
-0.004919787868857384,
-0.0158375333994627,
-0.06898266077041626,
0.050967585295438766,
0.029756667092442513,
0.02758653461933136,
0.03812377154827118,
-0.025610225275158882,
0.04441751167178154,
-0.02769470028579235,
0.014969959855079651,
-0.0901... |
45856be1-f870-4b3c-b740-7ab9912250a2 | | spark.clickhouse.read.fixedStringAs | binary | Read ClickHouse FixedString type as the specified Spark data type. Supported types: binary, string ... | {"source_file": "spark-native-connector.md"} | [
0.031618498265743256,
-0.06817595660686493,
0.013811304233968258,
0.016102170571684837,
-0.026198329403996468,
-0.015927787870168686,
0.014420588500797749,
0.043163832277059555,
-0.060709964483976364,
-0.0072141592390835285,
-0.036659903824329376,
-0.036857325583696365,
-0.058800555765628815... |
99d0f4f7-4d27-4763-b5b3-55bdbf2e80ad | true
. | 0.8.0 |
| spark.clickhouse.write.batchSize | 10000 | The number of records per batch on writing to ... | {"source_file": "spark-native-connector.md"} | [
0.018389815464615822,
-0.0718998983502388,
-0.08262894302606583,
0.0835363045334816,
0.013632051646709442,
-0.010205219499766827,
-0.0710124596953392,
0.002970486879348755,
-0.0744614526629448,
0.09777438640594482,
-0.0030133421532809734,
-0.006191257853060961,
0.0196533240377903,
-0.05082... |
484f036c-6a13-4fb2-8321-93e1d6aff6d1 | | spark.clickhouse.write.localSortByKey | true | If
true
, do local sort by sort keys before writing. ... | {"source_file": "spark-native-connector.md"} | [
0.014417137019336224,
-0.10144346207380295,
0.06599543988704681,
0.04203072190284729,
-0.05648491904139519,
-0.018701253458857536,
0.005111473146826029,
0.011465701274573803,
-0.07397148758172989,
0.058108069002628326,
-0.0053176977671682835,
0.02509349212050438,
-0.02396329864859581,
-0.0... |
57ea8e82-6323-47fb-ab53-880f49e677fc | | spark.clickhouse.write.repartitionStrictly | false | If
true
, Spark will strictly distribute incoming records across partitions to satisfy the required distribution before passing the records to the data source table on write. Otherwise, Spark may apply certa... | {"source_file": "spark-native-connector.md"} | [
-0.03572213649749756,
-0.08406948298215866,
0.04079164192080498,
0.0691332072019577,
-0.03890250623226166,
-0.06110619008541107,
-0.008938063867390156,
-0.009609891101717949,
-0.03839624300599098,
0.017402375116944313,
0.00481803435832262,
0.03639668971300125,
0.03314678743481636,
-0.05813... |
3472aa97-1fba-43ba-bfdf-f07f681009d0 | Supported data types {#supported-data-types}
This section outlines the mapping of data types between Spark and ClickHouse. The tables below provide quick references
for converting data types when reading from ClickHouse into Spark and when inserting data from Spark into ClickHouse.
Reading data from ClickHouse into... | {"source_file": "spark-native-connector.md"} | [
0.0337538979947567,
-0.10748542845249176,
-0.013553120195865631,
-0.007650289218872786,
-0.01107072550803423,
-0.0006622944492846727,
0.03258722648024559,
-0.014491112902760506,
-0.12581899762153625,
-0.06450659781694412,
-0.008646025322377682,
0.001591842737980187,
-0.057787492871284485,
... |
0795a309-3cf3-4a7b-bc81-e59bab401599 | | ClickHouse Data Type | Spark Data Type | Supported | Is Primitive | Notes |
|-------------------------------------------------------------------|--------------------------------|-----------|--------------|--------... | {"source_file": "spark-native-connector.md"} | [
0.019312487915158272,
-0.04964930936694145,
-0.01643877476453781,
0.03274054825305939,
-0.016642292961478233,
-0.030555889010429382,
0.052441105246543884,
-0.023427467793226242,
-0.10839159041643143,
-0.0272944625467062,
0.07710326462984085,
-0.057858675718307495,
-0.036669325083494186,
-0... |
a4e26c99-0e54-4e19-9a13-a2f18eec87b0 | |
Decimal64
|
DecimalType(18, scale)
| ✅ | Yes | |
|
Decimal128
|
DecimalType(38, scale)
| ✅ | Yes | ... | {"source_file": "spark-native-connector.md"} | [
0.07051412761211395,
0.0459701344370842,
-0.055052194744348526,
0.0339241661131382,
-0.09619738161563873,
-0.009610974229872227,
-0.03884709253907204,
0.029314912855625153,
-0.06186201795935631,
-0.036370839923620224,
0.020661065354943275,
-0.13274434208869934,
0.03192310407757759,
-0.0326... |
3de071a3-2a4e-4c99-af44-dde1a600cc39 | Ring
| | ❌ | | |
|
IntervalQuarter
| | ❌ | | ... | {"source_file": "spark-native-connector.md"} | [
-0.03511848673224449,
0.041003599762916565,
-0.013328829780220985,
0.014328674413263798,
-0.11055466532707214,
0.076032355427742,
-0.02447531372308731,
0.032965533435344696,
-0.03679872676730156,
-0.07608035206794739,
-0.027966530993580818,
-0.07006364315748215,
0.029546838253736496,
-0.04... |
2e6fc07c-fb33-4df8-b777-f9f644bb8784 | Inserting data from Spark into ClickHouse {#inserting-data-from-spark-into-clickhouse}
| Spark Data Type | ClickHouse Data Type | Supported | Is Primitive | Notes |
|-------------------------------------|----------------------|-----------|--------------|-----------... | {"source_file": "spark-native-connector.md"} | [
0.03305266797542572,
-0.06296952813863754,
-0.04923165962100029,
0.042481016367673874,
-0.0442766509950161,
-0.036253008991479874,
0.031803689897060394,
0.011262220330536366,
-0.1091647520661354,
-0.015752797946333885,
0.08224699646234512,
-0.06810194998979568,
-0.023242689669132233,
-0.01... |
98396e8c-5d3e-4f3b-a759-e1616f8d6ef2 | sidebar_label: 'dlt'
keywords: ['clickhouse', 'dlt', 'connect', 'integrate', 'etl', 'data integration']
description: 'Load data into Clickhouse using dlt integration'
title: 'Connect dlt to ClickHouse'
slug: /integrations/data-ingestion/etl-tools/dlt-and-clickhouse
doc_type: 'guide'
import PartnerBadge from '@theme... | {"source_file": "dlt-and-clickhouse.md"} | [
-0.046753864735364914,
-0.012834373861551285,
-0.0059033907018601894,
0.018434733152389526,
-0.05494590848684311,
-0.015502091497182846,
0.02550385147333145,
0.012780386954545975,
-0.12150419503450394,
-0.035427026450634,
0.018378568813204765,
-0.0007622052216902375,
0.06277987360954285,
-... |
fb29dc54-2102-44b6-abb4-f8ddd170e0f7 | Add credentials {#3-add-credentials}
Next, set up the ClickHouse credentials in the
.dlt/secrets.toml
file as shown below:
```bash
[destination.clickhouse.credentials]
database = "dlt" # The database name you created
username = "dlt" # ClickHouse username, default i... | {"source_file": "dlt-and-clickhouse.md"} | [
-0.030264317989349365,
-0.05596563592553139,
-0.08377280831336975,
-0.08507204800844193,
-0.14437785744667053,
-0.04692566767334938,
0.0220168586820364,
-0.015612803399562836,
-0.05041254684329033,
-0.0024455366656184196,
0.013956340029835701,
-0.07146338373422623,
0.045145146548748016,
-0... |
f6d93774-d603-42e8-99b9-21b372ccb9ba | Append
: This is the default disposition. It will append the data to the existing data in the destination, ignoring the
primary_key
field.
Data loading {#data-loading}
Data is loaded into ClickHouse using the most efficient method depending on the data source:
For local files, the
clickhouse-connect
library... | {"source_file": "dlt-and-clickhouse.md"} | [
0.010738210752606392,
-0.1060907244682312,
-0.04654160887002945,
0.01844271458685398,
-0.0036385285202413797,
-0.019317112863063812,
0.05301939323544502,
-0.03366682678461075,
0.046181291341781616,
0.08497557789087296,
0.07727143913507462,
0.01168252807110548,
0.053786374628543854,
-0.0768... |
254a6a01-923d-4342-9245-395b68d5bb91 | By default, tables are created using the
ReplicatedMergeTree
table engine in ClickHouse. You can specify an alternate table engine using the
table_engine_type
with the clickhouse adapter:
```bash
from dlt.destinations.adapters import clickhouse_adapter
@dlt.resource()
def my_resource():
...
clickhouse_adapt... | {"source_file": "dlt-and-clickhouse.md"} | [
-0.016395429149270058,
-0.12897498905658722,
-0.09535662084817886,
-0.025994960218667984,
-0.034016791731119156,
-0.05618204176425934,
0.005843508988618851,
-0.022487740963697433,
-0.012915315106511116,
0.1079036295413971,
0.029198041185736656,
-0.047470711171627045,
0.12406025826931,
-0.0... |
5f2bab1c-5d52-4d5d-8a63-980e6dba3418 | Note: In addition to the HMAC keys
bashgcp_access_key_id
and
gcp_secret_access_key
), you now need to provide the
client_email
,
project_id
and
private_key
for your service account under
[destination.filesystem.credentials]
. This is because the GCS staging support is now implemented as a temporary workaround ... | {"source_file": "dlt-and-clickhouse.md"} | [
-0.07773090898990631,
-0.07365114986896515,
0.021680256351828575,
-0.09029752016067505,
-0.0010297553380951285,
-0.011347776278853416,
0.06823171675205231,
-0.05491204559803009,
-0.0011111603816971183,
0.07999831438064575,
-0.02355371229350567,
-0.015598585829138756,
0.09487175941467285,
-... |
7ea8faf5-5feb-4068-aaf8-4edff956ac98 | sidebar_label: 'Vector'
sidebar_position: 220
slug: /integrations/vector
description: 'How to tail a log file into ClickHouse using Vector'
title: 'Integrating Vector with ClickHouse'
show_related_blogs: true
doc_type: 'guide'
integration:
- support_level: 'partner'
- category: 'data_ingestion'
- website: 'https:... | {"source_file": "vector-to-clickhouse.md"} | [
0.003029594663530588,
0.05034947767853737,
-0.0384594202041626,
-0.017037156969308853,
0.06577462702989578,
-0.09513276815414429,
0.03042558953166008,
0.045747388154268265,
-0.04033791273832321,
0.009218087419867516,
0.01069839671254158,
0.0034536488819867373,
0.05055464431643486,
-0.00251... |
788fc051-18ee-450f-b4fb-5fb06d6c34b7 | Be sure to restart Nginx if you had to modify
nginx.conf
.
Generate some log events in the access log by visiting pages on your web server.
Logs in the
combined
format look as follows:
bash
192.168.208.1 - - [12/Oct/2021:03:31:44 +0000] "GET / HTTP/1.1" 200 615 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS ... | {"source_file": "vector-to-clickhouse.md"} | [
0.011131249368190765,
0.02329825982451439,
-0.02231859602034092,
-0.058869779109954834,
0.04210224375128746,
-0.10962424427270889,
-0.02763269655406475,
-0.07376282662153244,
0.05581395700573921,
-0.009536675177514553,
-0.036952756345272064,
0.030391905456781387,
0.00011037637159461156,
0.... |
cc986b37-a368-4165-b89c-580eb2b4dbb5 | sql title="Query"
SELECT splitByWhitespace('192.168.208.1 - - [12/Oct/2021:15:32:43 +0000] "GET / HTTP/1.1" 304 0 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/93.0.4577.63 Safari/537.36"')
text title="Response"
["192.168.208.1","-","-","[12/Oct/2021:15:32:43","+00... | {"source_file": "vector-to-clickhouse.md"} | [
-0.008556390181183815,
-0.002297996310517192,
0.042552780359983444,
0.0356750413775444,
-0.02154877595603466,
-0.08663090318441391,
0.03138631582260132,
-0.0698942095041275,
-0.009072075597941875,
-0.03558596596121788,
0.038761939853429794,
-0.04216606914997101,
0.04253998398780823,
-0.094... |
a5d1930b-d12f-4dce-8472-765b21416950 | sql
CREATE MATERIALIZED VIEW nginxdb.access_logs_view
(
RemoteAddr String,
Client String,
RemoteUser String,
TimeLocal DateTime,
RequestMethod String,
Request String,
HttpVersion String,
Status Int32,
BytesSent Int64,
UserAgent String
)
ENGINE = MergeTree()
ORDER BY RemoteAddr
POPULATE AS
WITH
spl... | {"source_file": "vector-to-clickhouse.md"} | [
0.022296437993645668,
0.0016324277967214584,
0.016942592337727547,
0.01138066966086626,
-0.0806623324751854,
-0.0169107336550951,
0.00763298524543643,
0.016482025384902954,
-0.018038848415017128,
0.11991938948631287,
-0.041688576340675354,
-0.04612789675593376,
0.00424167700111866,
-0.0153... |
597b8903-07e5-4ca6-afdb-f214e550a63d | sidebar_label: 'NiFi'
sidebar_position: 12
keywords: ['clickhouse', 'NiFi', 'connect', 'integrate', 'etl', 'data integration']
slug: /integrations/nifi
description: 'Stream data into ClickHouse using NiFi data pipelines'
title: 'Connect Apache NiFi to ClickHouse'
doc_type: 'guide'
integration:
- support_level: 'commu... | {"source_file": "nifi-and-clickhouse.md"} | [
0.0030410210601985455,
0.03768576309084892,
-0.04462990164756775,
-0.031125428155064583,
0.018886011093854904,
-0.06952419877052307,
0.03612799197435379,
0.00639612739905715,
-0.08883252739906311,
-0.044106170535087585,
0.028762077912688255,
-0.0390014573931694,
0.08457189053297043,
-0.021... |
fa709e27-2175-4783-8aea-83c4ddb24c19 | In the release version, click on "Show all xx assets" and look for the JAR file containing the keyword "shaded" or "all", for example,
clickhouse-jdbc-0.5.0-all.jar
Place the JAR file in a folder accessible by Apache NiFi and take note of the absolute path
Add
DBCPConnectionPool
Controller Service and configur... | {"source_file": "nifi-and-clickhouse.md"} | [
-0.04331203177571297,
-0.08548363298177719,
-0.052487365901470184,
-0.06490185111761093,
-0.039190974086523056,
0.07615785300731659,
0.03883181884884834,
-0.04052403196692467,
-0.03738091140985489,
-0.0007232907228171825,
-0.015521473251283169,
-0.03323144465684891,
0.050534527748823166,
0... |
3d3c640f-91a8-4327-a8fd-af9925be4959 | Add an
ExecuteSQL
processor, along with the appropriate upstream and downstream processors
Under the "Properties" section of the
ExecuteSQL
processor, input the following values
| Property | Value | Remark ... | {"source_file": "nifi-and-clickhouse.md"} | [
-0.0038681025616824627,
-0.09738507866859436,
-0.10175935178995132,
0.05042660981416702,
-0.14182835817337036,
-0.018781522288918495,
0.06420818716287613,
-0.034286655485630035,
-0.0018749114824458957,
0.031253837049007416,
-0.015602734871208668,
-0.09174858033657074,
0.029824143275618553,
... |
0f9d0580-a113-458b-a7d9-02093ad59dd5 | Input
Output
Under the "Properties" section of the
PutDatabaseRecord
processor, input the following values
| Property | Value | Remark |
| ... | {"source_file": "nifi-and-clickhouse.md"} | [
0.0587029829621315,
0.015739453956484795,
0.0134219229221344,
0.0733509287238121,
-0.12404897063970566,
0.055489327758550644,
0.027116313576698303,
0.05592508614063263,
-0.019576480612158775,
0.03350502625107765,
0.020848555490374565,
-0.061734117567539215,
0.01551116444170475,
-0.05022466... |
41ddb82b-c47e-4c81-be5d-8632be656b04 | sidebar_label: 'BladePipe'
sidebar_position: 20
keywords: ['clickhouse', 'BladePipe', 'connect', 'integrate', 'cdc', 'etl', 'data integration']
slug: /integrations/bladepipe
description: 'Stream data into ClickHouse using BladePipe data pipelines'
title: 'Connect BladePipe to ClickHouse'
doc_type: 'guide'
import Im... | {"source_file": "bladepipe-and-clickhouse.md"} | [
-0.003042469033971429,
0.004820000380277634,
-0.054766520857810974,
-0.019133945927023888,
-0.020021021366119385,
0.00410148361697793,
0.0057081421837210655,
0.060833632946014404,
-0.020627131685614586,
-0.07386364787817001,
0.05856308341026306,
-0.08122167736291885,
0.03057854436337948,
-... |
8de3cfad-b6d3-42fc-8543-04ed9375ac28 | Add MySQL as a source {#3-add-mysql-as-a-source}
In this tutorial, we use a MySQL instance as the source, and explain the process of loading MySQL data to ClickHouse.
:::note
To use MySQL as a source, make sure that the user has the
required permissions
.
:::
In BladePipe, click "DataSource" > "Add DataSour... | {"source_file": "bladepipe-and-clickhouse.md"} | [
0.06576225161552429,
-0.13582338392734528,
-0.0805894061923027,
0.025344697758555412,
-0.12608414888381958,
-0.03878209739923477,
-0.0218205526471138,
0.012235535308718681,
-0.025035947561264038,
0.03787064924836159,
0.04469037801027298,
-0.08856602758169174,
0.09614631533622742,
-0.023130... |
fcd88929-fc54-4ec6-bae3-7a0180319510 | sidebar_label: 'Apache Beam'
slug: /integrations/apache-beam
description: 'Users can ingest data into ClickHouse using Apache Beam'
title: 'Integrating Apache Beam and ClickHouse'
doc_type: 'guide'
integration:
- support_level: 'core'
- category: 'data_ingestion'
keywords: ['apache beam', 'stream processing', 'batc... | {"source_file": "apache-beam.md"} | [
-0.06139872968196869,
-0.042081378400325775,
-0.028182893991470337,
0.007731707766652107,
-0.02937368117272854,
-0.05000075697898865,
0.014450923539698124,
-0.029107633978128433,
-0.1159796193242073,
-0.09235343337059021,
-0.006996147334575653,
0.02230244129896164,
-0.013332552276551723,
-... |
6bd76f78-265e-4756-901e-c1c76e054236 | public class Main {
public static void main(String[] args) {
// Create a Pipeline object.
Pipeline p = Pipeline.create();
Schema SCHEMA =
Schema.builder()
.addField(Schema.Field.of("name", Schema.FieldType.STRING).withNullable(true))
.addField(Schema.Fi... | {"source_file": "apache-beam.md"} | [
0.029922524467110634,
0.016326796263456345,
-0.0885293111205101,
0.006626151502132416,
-0.1113014817237854,
0.007733601611107588,
-0.07189926505088806,
0.09980817884206772,
-0.02910132147371769,
0.00005775822137366049,
-0.018266500905156136,
-0.118467316031456,
-0.007712837308645248,
-0.09... |
898bb0eb-9c81-4026-9826-e9cbe1c8d9f6 | | ClickHouse | Apache Beam | Is Supported | Notes |
|------------------------------------|----------------------------|--------------|----------------... | {"source_file": "apache-beam.md"} | [
0.04052043706178665,
-0.07071799039840698,
-0.08207487314939499,
0.009155241772532463,
-0.06603574007749557,
-0.031102048233151436,
0.013664541766047478,
-0.04617266729474068,
-0.07459436357021332,
-0.006575973238795996,
0.08826403319835663,
-0.057607900351285934,
-0.03633362054824829,
-0.... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.