id stringlengths 36 36 | document stringlengths 3 3k | metadata stringlengths 23 69 | embeddings listlengths 384 384 |
|---|---|---|---|
2701a404-240c-40d5-bd27-3cc719b3b87a | 3 rows in set. Elapsed: 0.002 sec.
```
Verify that tables created on the cluster are created on both nodes {#verify-that-tables-created-on-the-cluster-are-created-on-both-nodes}
sql
-- highlight-next-line
create table trips on cluster 'cluster_1S_2R' (
`trip_id` UInt32,
`pickup_date` Date,
`pickup_datetime` Date... | {"source_file": "index.md"} | [
0.007757487706840038,
-0.0011249907547608018,
-0.009624301455914974,
0.04120983928442001,
-0.02400621771812439,
-0.05081600323319435,
0.0220231581479311,
-0.007576657924801111,
-0.040802787989377975,
0.0347956120967865,
0.08350909501314163,
-0.1581423133611679,
0.04771886765956879,
-0.0825... |
a9cb0d33-b275-40c3-aa4f-cac6b9b516a9 | 1 row in set. Elapsed: 0.002 sec.
```
Verify in Google Cloud console {#verify-in-google-cloud-console}
Looking at the buckets you will see that a folder was created in each bucket with the name that was used in the
storage.xml
configuration file. Expand the folders and you will see many files, representing the d... | {"source_file": "index.md"} | [
-0.03162876516580582,
-0.012474101036787033,
-0.01634831167757511,
-0.0350191593170166,
0.0697677806019783,
-0.05141915753483772,
0.040906455367803574,
-0.022474979981780052,
0.09457005560398102,
0.04673769325017929,
0.09320531040430069,
-0.018808888271450996,
0.1133706122636795,
-0.078245... |
fb25cc8d-1586-43ce-9f22-91d23c6f2839 | title: 'Pausing and Resuming a MongoDB ClickPipe'
description: 'Pausing and Resuming a MongoDB ClickPipe'
sidebar_label: 'Pause table'
slug: /integrations/clickpipes/mongodb/pause_and_resume
doc_type: 'guide'
keywords: ['clickpipes', 'mongodb', 'cdc', 'data ingestion', 'real-time sync']
import Image from '@theme/Id... | {"source_file": "pause_and_resume.md"} | [
-0.04746651649475098,
-0.024791786447167397,
-0.05438533052802086,
0.0456552729010582,
0.018195968121290207,
0.015097037889063358,
-0.002050067763775587,
-0.017724817618727684,
-0.07220213115215302,
0.00449224142357707,
-0.03877826780080795,
0.0033015485387295485,
-0.08330746740102768,
-0.... |
05956a3a-5a66-419a-a0d9-7c02f2ad293a | sidebar_label: 'Lifecycle of a MongoDB ClickPipe'
description: 'Various pipe statuses and their meanings'
slug: /integrations/clickpipes/mongodb/lifecycle
title: 'Lifecycle of a MongoDB ClickPipe'
doc_type: 'guide'
keywords: ['clickpipes', 'mongodb', 'cdc', 'data ingestion', 'real-time sync']
Lifecycle of a MongoDB... | {"source_file": "lifecycle.md"} | [
-0.041107773780822754,
-0.0016853299457579851,
-0.02458510547876358,
0.02646023966372013,
0.014353848062455654,
-0.0918227881193161,
-0.0068057505413889885,
-0.0017431052401661873,
0.004558353219181299,
0.006204589270055294,
-0.004471713211387396,
-0.008496597409248352,
-0.04333343356847763,... |
916097e7-4a99-434d-b22f-c4543c48d0ea | Modifying {#modifying}
:::note
This state is coming soon. If you're using our
OpenAPI
, consider adding support for it now to ensure your integration continues working when it's released.
:::
Currently, this indicates the pipe is in the process of removing tables.
Resync {#resync}
:::note
This state is coming so... | {"source_file": "lifecycle.md"} | [
-0.02199043333530426,
0.013243435882031918,
0.016959795728325844,
0.03290228918194771,
0.0045092301443219185,
-0.10363936424255371,
-0.06875810027122498,
0.02169446088373661,
0.0057298303581774235,
-0.017965691164135933,
-0.005108298733830452,
-0.008274088613688946,
0.04224623367190361,
-0... |
0c6746f2-e814-4e2e-8303-4207f45ac564 | title: 'Resyncing Specific Tables'
description: 'Resyncing specific tables in a MongoDB ClickPipe'
slug: /integrations/clickpipes/mongodb/table_resync
sidebar_label: 'Resync table'
doc_type: 'guide'
keywords: ['clickpipes', 'mongodb', 'cdc', 'data ingestion', 'real-time sync']
Resyncing specific tables {#resync-tab... | {"source_file": "table_resync.md"} | [
-0.02208808995783329,
-0.023120209574699402,
0.016165336593985558,
0.038960233330726624,
0.0019312306540086865,
-0.08184171468019485,
-0.05109109729528427,
-0.035904549062252045,
-0.026360386982560158,
0.022160954773426056,
-0.04507708176970482,
0.005252881441265345,
-0.02389252372086048,
... |
36ea5b84-ebdf-47c5-a1a3-602c20dac616 | title: 'Adding specific tables to a ClickPipe'
description: 'Describes the steps needed to add specific tables to a ClickPipe.'
sidebar_label: 'Add table'
slug: /integrations/clickpipes/mongodb/add_table
show_title: false
doc_type: 'guide'
keywords: ['clickpipes', 'mongodb', 'cdc', 'data ingestion', 'real-time sync']
... | {"source_file": "add_table.md"} | [
0.02349075861275196,
-0.043812096118927,
-0.05173391476273537,
0.042787425220012665,
-0.02011977508664131,
-0.034451425075531006,
0.01101994514465332,
0.05521714687347412,
-0.04124929755926132,
0.032654836773872375,
-0.008202028460800648,
-0.06487420946359634,
0.009911440312862396,
0.00133... |
26169fcf-6d18-4b9b-a7b9-be136ef0c12d | title: 'Supported data types'
slug: /integrations/clickpipes/mongodb/datatypes
description: 'Page describing MongoDB ClickPipe datatype mapping from MongoDB to ClickHouse'
doc_type: 'reference'
keywords: ['clickpipes', 'mongodb', 'cdc', 'data ingestion', 'real-time sync']
MongoDB stores data records as BSON documen... | {"source_file": "datatypes.md"} | [
-0.03653349354863167,
-0.02223583683371544,
-0.06546589732170105,
0.06493407487869263,
-0.052156154066324234,
-0.0165437962859869,
-0.05584677308797836,
0.01587536185979843,
-0.026720669120550156,
-0.04760574549436569,
-0.02257165126502514,
-0.004559987690299749,
-0.05117025971412659,
0.05... |
d338d7a0-a4b2-4dd6-922a-4ae6209d4fcc | title: 'Resyncing a Database ClickPipe'
description: 'Doc for resyncing a database ClickPipe'
slug: /integrations/clickpipes/mongodb/resync
sidebar_label: 'Resync ClickPipe'
doc_type: 'guide'
keywords: ['clickpipes', 'mongodb', 'cdc', 'data ingestion', 'real-time sync']
import resync_button from '@site/static/image... | {"source_file": "resync.md"} | [
-0.08422785252332687,
-0.043938662856817245,
-0.019909778609871864,
0.06445016711950302,
0.06792579591274261,
-0.10438989847898483,
0.009205883368849754,
-0.01307111606001854,
0.025376975536346436,
0.019227320328354836,
-0.0230509452521801,
0.0606912299990654,
-0.0031343623995780945,
-0.08... |
5a2fd5db-4ed0-4946-848f-b8abd8a944c8 | title: 'Removing specific tables from a ClickPipe'
description: 'Removing specific tables from a ClickPipe'
sidebar_label: 'Remove table'
slug: /integrations/clickpipes/mongodb/removing_tables
doc_type: 'guide'
keywords: ['clickpipes', 'mongodb', 'cdc', 'data ingestion', 'real-time sync']
import Image from '@theme/... | {"source_file": "remove_table.md"} | [
0.011208103969693184,
0.06278381496667862,
0.012016214430332184,
0.024692477658391,
0.041437841951847076,
-0.1035080999135971,
0.035511311143636703,
-0.04843711480498314,
-0.002111609559506178,
0.03201867267489433,
-0.013533093966543674,
0.011760929599404335,
0.029515113681554794,
-0.00579... |
7b05a715-5159-4f1f-a1ca-08e1a428c88b | title: 'Working with JSON in ClickHouse'
sidebar_label: 'Working with JSON'
slug: /integrations/clickpipes/mongodb/quickstart
description: 'Common patterns for working with JSON data replicated from MongoDB to ClickHouse via ClickPipes'
doc_type: 'guide'
keywords: ['clickpipes', 'mongodb', 'cdc', 'data ingestion', 'rea... | {"source_file": "quickstart.md"} | [
-0.08295239508152008,
0.04813949391245842,
0.036030493676662445,
0.03915201127529144,
-0.06931330263614655,
-0.04572930186986923,
-0.060068514198064804,
-0.03397006541490555,
0.019166234880685806,
-0.05470122769474983,
0.04888443648815155,
-0.011200056411325932,
-0.02363906241953373,
0.000... |
c6868b69-6fd5-46b3-851b-ce29d8099f10 | sql
SELECT * FROM t1 FINAL;
Handling deletes {#handling-deletes}
Deletes from MongoDB are propagated as new rows marked as deleted using the
_peerdb_is_deleted
column. You typically want to filter these out in your queries:
sql
SELECT * FROM t1 FINAL WHERE _peerdb_is_deleted = 0;
You can also create a row-lev... | {"source_file": "quickstart.md"} | [
-0.05141005665063858,
0.06640836596488953,
0.0669005736708641,
0.039620935916900635,
0.004025165922939777,
-0.06767840683460236,
0.015364016406238079,
-0.034035567194223404,
0.03126472607254982,
0.05976060777902603,
0.01709855906665325,
0.026117052882909775,
-0.014059695415198803,
0.000313... |
4aae399d-c76b-4c76-b55e-2ae76aa48547 | sql
SELECT sum(doc.shipping.cost) AS shipping_cost FROM t1;
-- DB::Exception: Illegal type Dynamic of argument for aggregate function sum. (ILLEGAL_TYPE_OF_ARGUMENT)
To use aggregation functions, cast the field to the appropriate type with the
CAST
function or
::
syntax:
sql title="Query"
SELECT sum(doc.shippin... | {"source_file": "quickstart.md"} | [
-0.034219589084386826,
0.004914211109280586,
-0.015911836177110672,
0.1150016039609909,
-0.08665592223405838,
0.0009923665784299374,
0.04532254859805107,
0.07159660756587982,
-0.019856229424476624,
-0.013551984913647175,
-0.0025325806345790625,
-0.07532578706741333,
0.0007977411733008921,
... |
080eb6f7-c514-4dd9-be43-69b090caab14 | ``sql
CREATE TABLE flattened_t1 (
_id
String,
order_id
String,
customer_id
Int64,
status
String,
total_amount
Decimal(18, 2),
order_date
DateTime64(3),
shipping_info
JSON,
items` Dynamic
)
ENGINE = ReplacingMergeTree()
PRIMARY KEY _id
ORDER BY _id;
CREATE MATERIALIZED VIEW rmv REFRESH EVERY 1 HOUR TO flattened_t1 AS
... | {"source_file": "quickstart.md"} | [
-0.006345268804579973,
-0.0012876152759417892,
0.03310776129364967,
0.0750221386551857,
-0.11944848299026489,
-0.005077729467302561,
0.011981762945652008,
0.058974891901016235,
-0.06079471856355667,
0.026186686009168625,
0.037663474678993225,
-0.044125109910964966,
0.035340745002031326,
-0... |
f9dcd259-b24c-40fb-8178-1eb2568dcb4a | sidebar_label: 'FAQ'
description: 'Frequently asked questions about ClickPipes for MongoDB.'
slug: /integrations/clickpipes/mongodb/faq
sidebar_position: 2
title: 'ClickPipes for MongoDB FAQ'
doc_type: 'reference'
keywords: ['clickpipes', 'mongodb', 'cdc', 'data ingestion', 'real-time sync']
ClickPipes for MongoDB ... | {"source_file": "faq.md"} | [
0.02195761539041996,
0.06896297633647919,
0.010444042272865772,
0.03695934638381004,
-0.017550582066178322,
-0.019253592938184738,
0.03013281710445881,
0.0225811954587698,
-0.043879393488168716,
-0.06357799470424652,
-0.03577835485339165,
-0.05048007890582085,
-0.03513554856181145,
0.01388... |
c5a69af4-8c3c-429e-bd20-1ab0a8deceab | How does MongoDB CDC Connector handle transactions? {#how-does-mongodb-cdc-connector-handle-transactions}
Each document change within a transaction is processed individually to ClickHouse. Changes are applied in the order they appear in the oplog; and only committed changes are replicated to ClickHouse. If a MongoDB ... | {"source_file": "faq.md"} | [
-0.042170386761426926,
-0.011148987337946892,
0.014416049234569073,
0.05518389865756035,
0.032673511654138565,
-0.06413564831018448,
-0.07500254362821579,
-0.022943908348679543,
0.1027398630976677,
0.06283457577228546,
0.009337973780930042,
0.0943211242556572,
-0.047402359545230865,
0.0212... |
fcd0b0da-1939-4883-bc3e-a33542a19a98 | sidebar_label: 'Ingesting Data from MongoDB to ClickHouse'
description: 'Describes how to seamlessly connect your MongoDB to ClickHouse Cloud.'
slug: /integrations/clickpipes/mongodb
title: 'Ingesting data from MongoDB to ClickHouse (using CDC)'
doc_type: 'guide'
keywords: ['clickpipes', 'mongodb', 'cdc', 'data ingesti... | {"source_file": "index.md"} | [
0.00011955732043134049,
0.019645826891064644,
-0.04389380291104317,
0.03594658523797989,
0.0135352723300457,
-0.039978332817554474,
0.01864863932132721,
0.040351685136556625,
-0.0638895258307457,
0.0026567892637103796,
0.02394571155309677,
-0.05057338997721672,
-0.00861448422074318,
-0.000... |
4d5844fc-f602-4b6e-a60a-779a87d53f4f | Once the connection details are filled in, click
Next
.
Configure advanced settings {#advanced-settings}
You can configure the advanced settings if needed. A brief description of each setting is provided below:
Sync interval
: This is the interval at which ClickPipes will poll the source database for changes. ... | {"source_file": "index.md"} | [
-0.019094906747341156,
-0.050528544932603836,
-0.09397456049919128,
0.003478369442746043,
-0.08572852611541748,
-0.06673944741487503,
-0.05451888591051102,
-0.03134476765990257,
-0.020927945151925087,
0.052233997732400894,
-0.014962837100028992,
-0.03506872430443764,
0.03911779448390007,
-... |
d5e2b77e-e971-485c-a197-d3085b1d343f | title: 'Controlling the Syncing of a MongoDB ClickPipe'
description: 'Doc for controllling the sync a MongoDB ClickPipe'
slug: /integrations/clickpipes/mongodb/sync_control
sidebar_label: 'Controlling syncs'
doc_type: 'guide'
keywords: ['clickpipes', 'mongodb', 'cdc', 'data ingestion', 'real-time sync']
import edit... | {"source_file": "controlling_sync.md"} | [
-0.026905620470643044,
-0.019101472571492195,
-0.07087460905313492,
0.06487582623958588,
-0.04375484213232994,
-0.009759563952684402,
-0.024412354454398155,
0.011258474551141262,
-0.051927436143159866,
0.048053111881017685,
-0.026709292083978653,
-0.0077065336517989635,
-0.031455740332603455... |
b5208d66-b9a9-4960-806b-fd6f0f21c942 | This will open a flyout with the sync settings, where you can change the sync interval and pull batch size:
Monitoring sync control behaviour {#monitoring}
You can see how long each batch takes in the
CDC Syncs
table in the
Metrics
tab of the ClickPipe. Note that the duration here includes push time and also ... | {"source_file": "controlling_sync.md"} | [
0.043662428855895996,
-0.043097011744976044,
-0.0564122200012207,
0.009613648056983948,
-0.012086136266589165,
-0.012476942501962185,
-0.04981831833720207,
-0.02765718102455139,
0.003400817047804594,
0.003038879716768861,
0.03913873806595802,
-0.004420088604092598,
-0.10040156543254852,
-0... |
3f2f8199-c1a6-4b34-ba7f-d86b189ca8ed | title: 'Pausing and Resuming a Postgres ClickPipe'
description: 'Pausing and Resuming a Postgres ClickPipe'
sidebar_label: 'Pause table'
slug: /integrations/clickpipes/postgres/pause_and_resume
doc_type: 'guide'
keywords: ['clickpipes', 'postgresql', 'cdc', 'data ingestion', 'real-time sync']
import Image from '@th... | {"source_file": "pause_and_resume.md"} | [
-0.058163341134786606,
-0.05943167209625244,
-0.060722716152668,
0.029973730444908142,
-0.019372228533029556,
0.033315811306238174,
0.021492086350917816,
-0.020490482449531555,
-0.07818444818258286,
-0.01462484896183014,
-0.016852030530571938,
0.028748665004968643,
-0.0704699456691742,
-0.... |
28d859ff-95f6-4f24-a9f5-be6f6129c612 | sidebar_label: 'Lifecycle of a Postgres ClickPipe'
description: 'Various pipe statuses and their meanings'
slug: /integrations/clickpipes/postgres/lifecycle
title: 'Lifecycle of a Postgres ClickPipe'
doc_type: 'guide'
keywords: ['clickpipes', 'postgresql', 'cdc', 'data ingestion', 'real-time sync']
Lifecycle of a P... | {"source_file": "lifecycle.md"} | [
-0.056828271597623825,
-0.04325595125555992,
-0.026335425674915314,
-0.0052124690264463425,
-0.0394839309155941,
-0.06259335577487946,
0.011613426730036736,
-0.02124142460525036,
-0.0014897782821208239,
-0.006548273377120495,
0.015224345028400421,
0.022124355658888817,
-0.04208317771553993,
... |
9243b6dd-20d8-4401-8880-9ba2b0f62af5 | Pausing {#pausing}
:::note
This state is coming soon. If you're using our
OpenAPI
, consider adding support for it now to ensure your integration continues working when it's released.
:::
When you click on the Pause button, the pipe enters the
Pausing
state. This is a transient state where we are in the process of... | {"source_file": "lifecycle.md"} | [
-0.001806991291232407,
-0.010660860687494278,
-0.0171977411955595,
0.007635333575308323,
0.054602596908807755,
-0.09076477587223053,
-0.06132722273468971,
0.017927302047610283,
0.05875764414668083,
0.05014177784323692,
0.0396098867058754,
-0.03216424584388733,
-0.04395679384469986,
-0.0232... |
ed61b12d-f644-4cb4-90d5-03e3278ccb82 | title: 'Handling TOAST Columns'
description: 'Learn how to handle TOAST columns when replicating data from PostgreSQL to ClickHouse.'
slug: /integrations/clickpipes/postgres/toast
doc_type: 'guide'
keywords: ['clickpipes', 'postgresql', 'cdc', 'data ingestion', 'real-time sync']
When replicating data from PostgreSQ... | {"source_file": "toast.md"} | [
0.02589688077569008,
-0.021862687543034554,
-0.08601004630327225,
-0.011565367691218853,
-0.06961178034543991,
-0.07442788034677505,
-0.006918173748999834,
-0.044254545122385025,
0.0026126911398023367,
0.006336736958473921,
-0.006861481349915266,
0.0751216784119606,
-0.04050719365477562,
-... |
677d9495-a7d5-4a51-bcdd-914e6c760d3f | You can set the
REPLICA IDENTITY
to
FULL
using the following SQL command:
sql
ALTER TABLE your_table_name REPLICA IDENTITY FULL;
Refer to
this blog post
for performance considerations when setting
REPLICA IDENTITY FULL
.
Replication behavior when REPLICA IDENTITY FULL is not set {#replication-behavior-when... | {"source_file": "toast.md"} | [
-0.014787557534873486,
-0.059560343623161316,
-0.06589320302009583,
0.012883014045655727,
-0.054919157177209854,
-0.07937397807836533,
0.025865651667118073,
-0.11011984944343567,
0.037528421729803085,
0.012061544694006443,
0.02681303396821022,
0.014520479366183281,
0.004975777119398117,
-0... |
80c17989-d3ed-4056-bb7a-ca44a5f7343f | title: 'Resyncing Specific Tables'
description: 'Resyncing specific tables in a Postgres ClickPipe'
slug: /integrations/clickpipes/postgres/table_resync
sidebar_label: 'Resync table'
doc_type: 'guide'
keywords: ['clickpipes', 'postgresql', 'cdc', 'data ingestion', 'real-time sync']
Resyncing specific tables {#resyn... | {"source_file": "table_resync.md"} | [
-0.03538728132843971,
-0.06296676397323608,
0.02242056280374527,
0.019227448850870132,
-0.04495808854699135,
-0.05649241432547569,
-0.020267238840460777,
-0.05799255892634392,
-0.03493114188313484,
0.0025827731005847454,
-0.028687266632914543,
0.05926428735256195,
-0.03295719623565674,
-0.... |
89088ecb-e14f-4dd1-b851-e16b3ac234f9 | title: 'Adding specific tables to a ClickPipe'
description: 'Describes the steps need to add specific tables to a ClickPipe.'
sidebar_label: 'Add table'
slug: /integrations/clickpipes/postgres/add_table
show_title: false
keywords: ['clickpipes postgres', 'add table', 'table configuration', 'initial load', 'snapshot']
d... | {"source_file": "add_table.md"} | [
0.010596087202429771,
-0.06187945604324341,
-0.053064532577991486,
0.019324244931340218,
-0.045778125524520874,
-0.010564572177827358,
0.03967205807566643,
0.05941331759095192,
-0.05762552097439766,
0.009137052111327648,
0.00811787974089384,
-0.037200480699539185,
0.033042192459106445,
-0.... |
bb3a1f5e-7b63-4a21-b0e0-3f4eb9cca2bd | title: 'Resyncing a Database ClickPipe'
description: 'Doc for resyncing a database ClickPipe'
slug: /integrations/clickpipes/postgres/resync
sidebar_label: 'Resync ClickPipe'
doc_type: 'guide'
keywords: ['clickpipes', 'postgresql', 'cdc', 'data ingestion', 'real-time sync']
import resync_button from '@site/static/i... | {"source_file": "resync.md"} | [
-0.08391247689723969,
-0.06653551012277603,
-0.030047936365008354,
0.05192825198173523,
0.04628542438149452,
-0.08615782111883163,
0.015931908041238785,
-0.022771956399083138,
0.01781846396625042,
0.009800507687032223,
-0.01350573729723692,
0.07244225591421127,
0.016262631863355637,
-0.118... |
41f8f518-9e88-4e54-80e1-e210dcdb838e | title: 'Removing specific tables from a ClickPipe'
description: 'Removing specific tables from a ClickPipe'
sidebar_label: 'Remove Table'
slug: /integrations/clickpipes/postgres/removing_tables
doc_type: 'guide'
keywords: ['clickpipes', 'postgresql', 'cdc', 'data ingestion', 'real-time sync']
import Image from '@th... | {"source_file": "remove_table.md"} | [
0.005404382478445768,
0.04366903752088547,
0.011529171839356422,
0.008249474689364433,
0.017418749630451202,
-0.08577300608158112,
0.06079714000225067,
-0.058187004178762436,
-0.008108598180115223,
0.0204519834369421,
0.0090655367821455,
0.039917584508657455,
0.040837787091732025,
-0.03971... |
78f3945f-ec31-406c-b928-559160ab65ba | sidebar_label: 'Ordering keys'
description: 'How to define custom ordering keys.'
slug: /integrations/clickpipes/postgres/ordering_keys
title: 'Ordering Keys'
doc_type: 'guide'
keywords: ['clickpipes', 'postgresql', 'cdc', 'data ingestion', 'real-time sync']
Ordering Keys (a.k.a. sorting keys) define how data is so... | {"source_file": "ordering_keys.md"} | [
-0.01183223631232977,
-0.036291368305683136,
0.018221300095319748,
-0.04999924823641777,
-0.04699746146798134,
-0.022157948464155197,
-0.028354058042168617,
-0.021617291495203972,
0.02312939427793026,
0.05528932437300682,
0.08148857951164246,
0.08185552060604095,
-0.008317824453115463,
-0.... |
48b247ac-3314-4136-bd90-0c95f64ae271 | For example, in a multi-tenant SaaS application, using (
tenant_id
,
id
) as the ordering key is a good choice. These columns uniquely identify each row, and
tenant_id
remains constant for an
id
even if other columns change. Since deduplication by id aligns with deduplication by (tenant_id, id), it helps avoid dat... | {"source_file": "ordering_keys.md"} | [
-0.06391360610723495,
0.0038519282825291157,
0.028081638738512993,
-0.04935331642627716,
0.000546806026250124,
0.023513374850153923,
-0.07044872641563416,
-0.0717085674405098,
0.10425718128681183,
0.0694977417588234,
0.08017054200172424,
0.10038051009178162,
0.00970055628567934,
-0.0702352... |
3c3da501-79c1-4f38-88ad-9e162ac3ac7a | sidebar_label: 'FAQ'
description: 'Frequently asked questions about ClickPipes for Postgres.'
slug: /integrations/clickpipes/postgres/faq
sidebar_position: 2
title: 'ClickPipes for Postgres FAQ'
keywords: ['postgres faq', 'clickpipes', 'toast columns', 'replication slot', 'publications']
doc_type: 'reference'
impor... | {"source_file": "faq.md"} | [
-0.06775793433189392,
-0.03661055862903595,
-0.005855277180671692,
0.03330513462424278,
0.04510752856731415,
-0.0648966059088707,
0.05732790380716324,
-0.02957909181714058,
0.027472706511616707,
-0.05204000696539879,
-0.009196163155138493,
0.08712757378816605,
0.012138895690441132,
-0.1084... |
756b306a-953b-44a3-adba-f0ee56be4769 | sql
ALTER TABLE your_table_name REPLICA IDENTITY FULL;
REPLICA IDENTITY FULL also enables replication of unchanged TOAST columns. More on that
here
.
Note that using
REPLICA IDENTITY FULL
can have performance implications and also faster WAL growth, especially for tables without a primary key and with frequent ... | {"source_file": "faq.md"} | [
-0.04821695759892464,
-0.07432377338409424,
-0.020849186927080154,
-0.003884576726704836,
-0.029203325510025024,
-0.05627436563372612,
-0.005522212013602257,
-0.030924754217267036,
0.029012367129325867,
0.04894821345806122,
0.0016678585670888424,
0.0006346798036247492,
-0.02602778561413288,
... |
9428493d-d9d9-4ccf-8d88-438e0136220b | For more details, refer to:
ReplacingMergeTree table engine best practices
Postgres-to-ClickHouse CDC internals blog
Can I update primary key columns in PostgreSQL? {#can-i-update-primary-key-columns-in-postgresql}
:::warning
Primary key updates in PostgreSQL cannot be properly replayed in ClickHouse by def... | {"source_file": "faq.md"} | [
-0.05727136880159378,
-0.04380430653691292,
0.016538091003894806,
-0.06330312043428421,
-0.0421798937022686,
-0.05034017190337181,
-0.06020154058933258,
-0.060702092945575714,
0.045055944472551346,
0.07636047154664993,
0.0619405061006546,
0.06885982304811478,
-0.03926066309213638,
-0.14426... |
83d83e75-f147-40f1-b9d2-af45e472b118 | Long-Running Transactions
An open transaction forces Postgres to keep all WAL segments generated since the transaction began, which can dramatically increase slot size.
Set
statement_timeout
and
idle_in_transaction_session_timeout
to reasonable values to prevent transactions from staying open indefinitely:
... | {"source_file": "faq.md"} | [
0.03649510443210602,
-0.018779434263706207,
-0.04263861104846001,
0.06195090338587761,
-0.024673830717802048,
-0.019525546580553055,
-0.0029713648837059736,
-0.01506503764539957,
-0.0036513665691018105,
0.05501265078783035,
-0.024223079904913902,
0.13551387190818787,
-0.10719825327396393,
... |
8be50f72-79db-47fd-9176-02e69ba038fe | How are JSON and JSONB columns replicated from Postgres? {#how-are-json-and-jsonb-columns-replicated-from-postgres}
JSON and JSONB columns are replicated as String type in ClickHouse. Since ClickHouse supports a native
JSON type
, you can create a materialized view over the ClickPipes tables to perform the translati... | {"source_file": "faq.md"} | [
-0.06107069179415703,
-0.10334471613168716,
-0.08003349602222443,
0.005950309801846743,
-0.06683078408241272,
-0.026492493227124214,
-0.07499901950359344,
-0.10163885354995728,
0.026072928681969643,
-0.03558885678648949,
0.027953866869211197,
0.07595208287239075,
-0.053336575627326965,
-0.... |
1788628a-b7eb-4624-802f-a8b0e8729f37 | These adjustments should significantly enhance the performance of the initial load, especially for older Postgres versions. If you are using Postgres 14 or later, these settings are less impactful due to improved support for CTID range scans.
How should I scope my publications when setting up replication? {#how-shoul... | {"source_file": "faq.md"} | [
0.0279981791973114,
-0.015866583213210106,
-0.046134889125823975,
0.03623387590050697,
-0.07135553658008575,
-0.0313662514090538,
-0.048567842692136765,
-0.032126061618328094,
-0.04248741269111633,
0.07385922968387604,
-0.04517596587538719,
0.0769147053360939,
0.021190699189901352,
-0.0467... |
a51a7f27-3399-4444-bf75-739fd4289465 | Recommended
max_slot_wal_keep_size
settings {#recommended-max_slot_wal_keep_size-settings}
At Minimum:
Set
max_slot_wal_keep_size
to retain at least
two days' worth
of WAL data.
For Large Databases (High Transaction Volume):
Retain at least
2-3 times
the peak WAL generation per day.
For Storage-Constr... | {"source_file": "faq.md"} | [
0.036516692489385605,
0.018378043547272682,
-0.048566918820142746,
0.03790441155433655,
-0.041814591735601425,
-0.01616768166422844,
-0.028842763975262642,
0.061391621828079224,
-0.0594518668949604,
0.021482670679688454,
-0.038617804646492004,
0.027834897860884666,
-0.02036627195775509,
-0... |
fde7e031-191a-4d2e-b73b-3514af4e4e78 | In rare cases, we have seen this issue occur even when
max_slot_wal_keep_size
is not configured. This could be due to an intricate and rare bug in PostgreSQL, although the cause remains unclear.
I am seeing out of memory (OOMs) on ClickHouse while my ClickPipe is ingesting data. Can you help? {#i-am-seeing-out-of-m... | {"source_file": "faq.md"} | [
0.02906103990972042,
-0.08955223113298416,
-0.02379164658486843,
0.05937329679727554,
-0.05947836488485336,
-0.06658009439706802,
0.042200714349746704,
-0.017977889627218246,
-0.006201281677931547,
0.008946503512561321,
-0.05688408017158508,
0.07160382717847824,
-0.05878199264407158,
-0.05... |
e073bb81-32a7-46c2-b390-10a29c70b83f | Alternatively, you can create an entirely new pipe if preferred.
Note that if you're working with partitioned tables, make sure to create your publication with the appropriate settings:
sql
CREATE PUBLICATION clickpipes_publication
FOR TABLE <...>, <...>
WITH (publish_via_partition_root = true);
What if I am seei... | {"source_file": "faq.md"} | [
0.048779502511024475,
-0.07545803487300873,
-0.030465535819530487,
-0.0048417337238788605,
-0.07424276322126389,
-0.08078805357217789,
-0.02883772738277912,
0.03606784716248512,
-0.07648597657680511,
0.04664336517453194,
-0.04099040850996971,
-0.05740264058113098,
-0.02326171100139618,
0.0... |
3b2642c8-9948-4631-b56e-0aee7ed31974 | Note that TRUNCATE operations are ignored by ClickPipes and will not be replicated to ClickHouse.
Why can I not replicate my table which has a dot in it? {#replicate-table-dot}
PeerDB has a limitation currently where dots in source table identifiers - aka either schema name or table name - is not supported for repl... | {"source_file": "faq.md"} | [
-0.014200244098901749,
-0.10603231936693192,
-0.011980582028627396,
0.027539357542991638,
-0.07279689610004425,
-0.08738043904304504,
-0.009257028810679913,
-0.053988032042980194,
-0.06315071880817413,
0.07587327063083649,
0.004756862763315439,
0.03442469611763954,
0.02136910893023014,
-0.... |
0ade9104-222c-48c9-b5ce-3e0453681039 | title: 'Schema Changes Propagation Support'
slug: /integrations/clickpipes/postgres/schema-changes
description: 'Page describing schema change types detectable by ClickPipes in the source tables'
doc_type: 'reference'
keywords: ['clickpipes', 'postgresql', 'cdc', 'data ingestion', 'real-time sync']
ClickPipes for P... | {"source_file": "schema-changes.md"} | [
-0.020910030230879784,
-0.08058375120162964,
0.026771726086735725,
-0.013970574364066124,
-0.011276577599346638,
-0.06215612590312958,
-0.011376305483281612,
-0.08550342917442322,
0.013218776322901249,
0.014716509729623795,
0.01866595260798931,
-0.02610013820230961,
-0.026848506182432175,
... |
5ad3c8a7-a26a-49d8-bf22-037c439ed174 | sidebar_label: 'Deduplication strategies'
description: 'Handle duplicates and deleted rows.'
slug: /integrations/clickpipes/postgres/deduplication
title: 'Deduplication strategies (using CDC)'
keywords: ['deduplication', 'postgres', 'clickpipes', 'replacingmergetree', 'final']
doc_type: 'guide'
import clickpipes_in... | {"source_file": "deduplication.md"} | [
-0.1199922263622284,
-0.0365259051322937,
0.00983534473925829,
0.004254783038049936,
-0.016218049451708794,
-0.10013741254806519,
0.0241808220744133,
-0.08012912422418594,
0.07942954450845718,
0.047446444630622864,
0.08597174286842346,
0.07864923030138016,
0.03625127300620079,
-0.115894608... |
07ddd518-c86b-4d90-b782-23d4da338b58 | Step 2
shows three operations on the users table: inserting a new row, updating an existing row, and deleting another row.
Step 3
shows how ClickPipes replicates the INSERT, UPDATE, and DELETE operations to ClickHouse as versioned inserts. The UPDATE appears as a new version of the row with ID 2, while the DELETE a... | {"source_file": "deduplication.md"} | [
-0.0574718713760376,
-0.08107445389032364,
0.04165384918451309,
-0.019442614167928696,
-0.06590733677148819,
-0.0625072717666626,
0.002154087647795677,
-0.08683539927005768,
0.044639952480793,
-0.028500216081738472,
0.07051697373390198,
0.0664636418223381,
0.01052687969058752,
-0.123896121... |
78e38f5c-9131-4cad-bdbb-1e72c4b71c29 | ```sql
-- Per query FINAL setting
SELECT count(*) FROM posts SETTINGS FINAL = 1;
-- Set FINAL for the session
SET final = 1;
SELECT count(*) FROM posts;
```
ROW policy {#row-policy}
An easy way to hide the redundant
_peerdb_is_deleted = 0
filter is to use
ROW policy.
Below is an example that creates a row po... | {"source_file": "deduplication.md"} | [
-0.024515638127923012,
0.015626467764377594,
-0.033146265894174576,
0.057543378323316574,
-0.00337813189253211,
0.06617158651351929,
0.08946450799703598,
-0.11115255206823349,
-0.019520727917551994,
0.04789099469780922,
0.031228654086589813,
0.029842402786016464,
0.12823006510734558,
-0.08... |
6a499f98-deda-484f-8b91-2e17c47270ed | Then, you can query the table
deduplicated_posts
normally.
sql
SELECT
sum(viewcount) AS viewcount,
owneruserid
FROM deduplicated_posts
WHERE owneruserid > 0
GROUP BY owneruserid
ORDER BY viewcount DESC
LIMIT 10; | {"source_file": "deduplication.md"} | [
0.03538154065608978,
-0.050011150538921356,
-0.019285596907138824,
0.03867066279053688,
-0.07921268045902252,
0.012447749264538288,
0.05170631408691406,
-0.04684435948729515,
-0.06342878192663193,
-0.009069324471056461,
0.07313565909862518,
-0.03909824416041374,
0.07595503330230713,
-0.026... |
55befe47-6672-4082-aae8-4cf536e40f5e | sidebar_label: 'Ingesting data from Postgres to ClickHouse'
description: 'Seamlessly connect your Postgres to ClickHouse Cloud.'
slug: /integrations/clickpipes/postgres
title: 'Ingesting Data from Postgres to ClickHouse (using CDC)'
keywords: ['PostgreSQL', 'ClickPipes', 'CDC', 'change data capture', 'database replicat... | {"source_file": "index.md"} | [
-0.00447699474170804,
-0.0018973123515024781,
-0.05840318650007248,
-0.004874411970376968,
-0.04564490541815758,
-0.011610103771090508,
0.05485200509428978,
0.005196088459342718,
-0.06084616109728813,
0.01634136587381363,
0.046213943511247635,
-0.031042544171214104,
-0.016958387568593025,
... |
51a28fa8-4a03-4498-ae1e-2dfb8c42be0f | Creating your ClickPipe {#creating-your-clickpipe}
Make sure you are logged in to your ClickHouse Cloud account. If you don't have an account yet, you can sign up
here
.
In the ClickHouse Cloud console, navigate to your ClickHouse Cloud Service.
Select the
Data Sources
button on the left-side menu and ... | {"source_file": "index.md"} | [
0.029743637889623642,
-0.06853382289409637,
-0.044187143445014954,
-0.038835443556308746,
-0.07125276327133179,
0.03762088343501091,
-0.04470979422330856,
-0.02701256237924099,
0.013724210672080517,
0.061612989753484726,
-0.028369728475809097,
-0.024248460307717323,
-0.0684874951839447,
-0... |
7847f893-f376-414d-8ee2-dce9ef99087d | Pull batch size
: The number of rows to fetch in a single batch. This is a best effort setting and may not be respected in all cases.
Snapshot number of rows per partition
: This is the number of rows that will be fetched in each partition during the initial snapshot. This is useful when you have a large number of ro... | {"source_file": "index.md"} | [
-0.009383060038089752,
-0.08196449279785156,
-0.06613993644714355,
-0.011445620097219944,
-0.07532893121242523,
-0.023012209683656693,
-0.008807148784399033,
-0.0009471401572227478,
-0.0425911508500576,
0.033582624047994614,
-0.029293879866600037,
-0.01042727567255497,
-0.0073200128972530365... |
bdc855c7-3d4d-404d-a86e-8402cd2f60ab | title: 'Scaling DB ClickPipes via OpenAPI'
description: 'Doc for scaling DB ClickPipes via OpenAPI'
slug: /integrations/clickpipes/postgres/scaling
sidebar_label: 'Scaling'
doc_type: 'guide'
keywords: ['clickpipes', 'postgresql', 'cdc', 'data ingestion', 'real-time sync']
:::caution Most users won't need this API
D... | {"source_file": "scaling.md"} | [
-0.008731517009437084,
-0.03885146975517273,
-0.05153493955731392,
0.019877221435308456,
-0.08316070586442947,
-0.08613717555999756,
-0.05533081665635109,
0.06000950559973717,
-0.05923384800553322,
0.012556065805256367,
-0.035962384194135666,
0.004930083639919758,
-0.048884328454732895,
-0... |
871c2410-d415-4d2a-acdb-3730fb906254 | Wait for the configuration to propagate (typically 3-5 minutes). After the scaling is finished, the GET endpoint will reflect the new values:
```bash
curl --silent --user $KEY_ID:$KEY_SECRET \
https://api.clickhouse.cloud/v1/organizations/$ORG_ID/services/$SERVICE_ID/clickpipesCdcScaling \
| jq
example result:
{
... | {"source_file": "scaling.md"} | [
-0.02264202944934368,
0.015367109328508377,
-0.06458163261413574,
0.008708293549716473,
-0.05767332762479782,
-0.05575486272573471,
-0.059992220252752304,
-0.04735976457595825,
0.03656787425279617,
0.023594016209244728,
0.026941297575831413,
-0.010590909980237484,
-0.010113676078617573,
-0... |
58410571-f307-44a0-9cd2-d72a6a20946f | title: 'Postgres Generated Columns: Gotchas and Best Practices'
slug: /integrations/clickpipes/postgres/generated_columns
description: 'Page describing important considerations to keep in mind when using PostgreSQL generated columns in tables that are being replicated'
doc_type: 'guide'
keywords: ['clickpipes', 'postgr... | {"source_file": "postgres_generated_columns.md"} | [
-0.05446808040142059,
-0.053907640278339386,
-0.09773269295692444,
0.010567767545580864,
-0.03798816353082657,
-0.06134990602731705,
-0.09600542485713959,
-0.060071323066949844,
0.016000645235180855,
0.042983878403902054,
0.061600856482982635,
0.017754128202795982,
0.0700286328792572,
-0.1... |
1226fb53-9786-4d46-8cc2-5fc586abce15 | title: 'Controlling the Syncing of a Postgres ClickPipe'
description: 'Doc for controlling the sync a Postgres ClickPipe'
slug: /integrations/clickpipes/postgres/sync_control
sidebar_label: 'Controlling syncs'
keywords: ['sync control', 'postgres', 'clickpipes', 'batch size', 'sync interval']
doc_type: 'guide'
impo... | {"source_file": "controlling_sync.md"} | [
-0.04525536671280861,
-0.05247883126139641,
-0.08465989679098129,
0.046787530183792114,
-0.08296669274568558,
0.008395655080676079,
0.000753877975512296,
0.0020278827287256718,
-0.07216659933328629,
0.018434103578329086,
-0.00029476129566319287,
0.012772591784596443,
-0.015653342008590698,
... |
e20009ed-31a6-42bd-aa2e-1f4818c18e95 | This will open a flyout with the sync settings, where you can change the sync interval and pull batch size:
Tweaking the sync settings to help with replication slot growth {#tweaking}
Let's talk about how to use these settings to handle a large replication slot of a CDC pipe.
The pushing time to ClickHouse does n... | {"source_file": "controlling_sync.md"} | [
0.010992954485118389,
-0.05946028605103493,
-0.058182720094919205,
0.005632924847304821,
-0.04189666360616684,
-0.04943981021642685,
-0.07181517779827118,
-0.012761247344315052,
-0.004587722476571798,
0.03342599794268608,
0.03551929444074631,
0.030399657785892487,
-0.012057427316904068,
-0... |
f6b606b8-af62-4339-b8c7-71e2c9c59051 | sidebar_label: 'Maintenance windows'
description: 'Maintenance windows for ClickPipes for Postgres.'
slug: /integrations/clickpipes/postgres/maintenance
title: 'Maintenance windows for ClickPipes for Postgres'
doc_type: 'reference'
keywords: ['clickpipes', 'postgresql', 'cdc', 'data ingestion', 'real-time sync']
Ma... | {"source_file": "maintenance.md"} | [
-0.01838696375489235,
-0.04558293893933296,
0.019176678732037544,
0.014607179909944534,
-0.048563454300165176,
-0.04133766144514084,
0.005623300094157457,
-0.024874091148376465,
-0.04397520795464516,
-0.028133409097790718,
-0.05723593756556511,
0.06673279404640198,
-0.1124468445777893,
-0.... |
3503911e-705b-47ba-ab56-4b6308a6ce17 | title: 'Parallel Snapshot In The Postgres ClickPipe'
description: 'Doc for explaining parallel snapshot in the Postgres ClickPipe'
slug: /integrations/clickpipes/postgres/parallel_initial_load
sidebar_label: 'How parallel snapshot works'
doc_type: 'guide'
keywords: ['clickpipes', 'postgresql', 'cdc', 'data ingestion', ... | {"source_file": "parallel_initial_load.md"} | [
-0.06156867742538452,
-0.03050893358886242,
-0.05309569835662842,
-0.028958288952708244,
-0.019389014691114426,
-0.07055019587278366,
-0.05537428334355354,
0.002299398882314563,
0.001892138971015811,
0.02307896688580513,
-0.007979001849889755,
0.04904194548726082,
0.0010297308908775449,
-0... |
9abb8e9d-c393-4633-8769-16e527ad95a1 | Snapshot number of tables in parallel {#tables-parallel-pg-snapshot}
Not really related to parallel snapshot, but this setting controls how many tables are processed in parallel during the initial load. The default value is 1. Note that is on top of the parallelism of the partitions, so if you have 4 partitions and 2... | {"source_file": "parallel_initial_load.md"} | [
-0.013193833641707897,
-0.07552597671747208,
-0.03927198424935341,
-0.018181759864091873,
-0.05501387268304825,
-0.038309160619974136,
0.006279671099036932,
-0.016468865796923637,
0.03970899432897568,
-0.011184883303940296,
-0.043786611407995224,
-0.022641655057668686,
0.011669528670608997,
... |
34520884-54fe-4006-8271-73449d4902b8 | sidebar_label: 'Reference'
description: 'Details supported formats, sources, delivery semantics, authentication and experimental features supported by Kafka ClickPipes'
slug: /integrations/clickpipes/kafka/reference
sidebar_position: 1
title: 'Reference'
doc_type: 'reference'
keywords: ['kafka reference', 'clickpipes',... | {"source_file": "03_reference.md"} | [
-0.031879059970378876,
0.025173399597406387,
-0.13789327442646027,
0.009488502517342567,
0.028020376339554787,
0.006341245025396347,
-0.00014160484715830535,
0.019920581951737404,
0.017361287027597427,
0.05435134470462799,
0.0013334564864635468,
-0.04981444031000137,
-0.007235523778945208,
... |
70a31388-fb6b-457b-921f-0ab7316140eb | DateTime, DateTime64 (UTC timezones only)
Enum8/Enum16
UUID
IPv4
IPv6
all ClickHouse LowCardinality types
Map with keys and values using any of the above types (including Nullables)
Tuple and Array with elements using any of the above types (including Nullables, one level depth only)
SimpleAggregateFunc... | {"source_file": "03_reference.md"} | [
0.05196286737918854,
-0.013617996126413345,
-0.07804235070943832,
-0.04669399932026863,
-0.025317851454019547,
-0.01874121092259884,
0.0519331619143486,
0.0019542265217751265,
-0.06412607431411743,
-0.01987752690911293,
-0.035905640572309494,
-0.08408347517251968,
-0.10164033621549606,
-0.... |
09f5b001-b841-4b54-8186-863b252b97e9 | Note that you will have to manually change the destination column to the desired JSON type, including any fixed or skipped paths.
Kafka virtual columns {#kafka-virtual-columns}
The following virtual columns are supported for Kafka compatible streaming data sources. When creating a new destination table virtual col... | {"source_file": "03_reference.md"} | [
0.03824662044644356,
-0.05414115637540817,
-0.09759499877691269,
0.036271438002586365,
-0.01432208064943552,
-0.008248267695307732,
-0.05083658546209335,
0.009645238518714905,
0.004289854317903519,
0.06162256747484207,
-0.0058939531445503235,
-0.14434413611888885,
-0.013966521248221397,
0.... |
fbf1902f-7a3a-49a8-a93b-fadb0aee3da3 | sidebar_label: 'Integrate with a schema registry'
description: 'How to integrate for ClickPipes with a schema registry for schema management'
slug: /integrations/clickpipes/kafka/schema-registries
sidebar_position: 1
title: 'Schema registries for Kafka ClickPipe'
doc_type: 'guide'
keywords: ['schema registries', 'kafka... | {"source_file": "02_schema-registries.md"} | [
-0.04684773087501526,
-0.07413889467716217,
-0.09634710103273392,
-0.0060062408447265625,
-0.0158144049346447,
0.05197853967547417,
0.00906706415116787,
-0.030469078570604324,
-0.045812565833330154,
0.03635401278734207,
0.01475616730749607,
-0.10066264122724533,
-0.050141580402851105,
-0.0... |
091e8386-5a0a-4476-bcbc-8c2d1ccc2889 | If the Avro schema field and the ClickHouse column are incompatible, inserts of that row/message will fail, and the failure will be recorded in the ClickPipes errors table. Note that several implicit conversions are supported (like between numeric types), but not all (for example, an Avro record field can not be insert... | {"source_file": "02_schema-registries.md"} | [
0.04390590637922287,
-0.07502548396587372,
-0.0929255560040474,
-0.03588300943374634,
-0.03562261164188385,
-0.019237162545323372,
-0.018465887755155563,
-0.030037714168429375,
-0.05510633811354637,
-0.01152622140944004,
0.02306355908513069,
-0.08770594000816345,
-0.0017739629838615656,
-0... |
91c14461-321e-4fd0-a378-43bcea3aa8bb | description: 'Landing page with table of contents for the Kafka ClickPipes section'
slug: /integrations/clickpipes/kafka
sidebar_position: 1
title: 'Kafka ClickPipes'
doc_type: 'landing-page'
integration:
- support_level: 'core'
- category: 'clickpipes'
keywords: ['Kafka ClickPipes', 'Apache Kafka', 'streaming inge... | {"source_file": "index.md"} | [
-0.033528074622154236,
-0.09047442674636841,
-0.09957917779684067,
-0.005419920198619366,
-0.027527926489710808,
-0.011612274684011936,
-0.050699517130851746,
0.01823435351252556,
-0.08501787483692169,
0.030551455914974213,
-0.033261530101299286,
-0.05020345002412796,
-0.013544607907533646,
... |
61e1cebb-8fc6-434c-b7b8-cd40f44759dc | sidebar_label: 'Create your first Kafka ClickPipe'
description: 'Step-by-step guide to creating your first Kafka ClickPipe.'
slug: /integrations/clickpipes/kafka/create-your-first-kafka-clickpipe
sidebar_position: 1
title: 'Creating your first Kafka ClickPipe'
doc_type: 'guide'
keywords: ['create kafka clickpipe', 'kaf... | {"source_file": "01_create-kafka-clickpipe.md"} | [
-0.053330034017562866,
-0.009965291246771812,
-0.07022887468338013,
-0.0006794920191168785,
-0.03859823942184448,
-0.03734727203845978,
-0.02468220889568329,
0.07832827419042587,
-0.040273986756801605,
-0.0019153119064867496,
0.03169432282447815,
-0.07066544145345688,
0.021080762147903442,
... |
67d57521-5495-47af-8683-79ee6497ee60 | You can also customize the advanced settings using the controls provided
Configure permissions {#8-configure-permissions}
ClickPipes will create a dedicated user for writing data into a destination table. You can select a role for this internal user using a custom role or one of the predefined role:
-
Full acces... | {"source_file": "01_create-kafka-clickpipe.md"} | [
0.04904400557279587,
-0.1142624095082283,
-0.10975860804319382,
0.022675398737192154,
-0.07653368264436722,
-0.048057086765766144,
0.033051490783691406,
0.010036435909569263,
-0.13279986381530762,
0.04523896798491478,
-0.01039485726505518,
-0.07738062739372253,
0.04320243000984192,
-0.0192... |
dc067ac7-16c3-4034-b28b-d788608bec1b | sidebar_label: 'FAQ'
description: 'Frequently asked questions about ClickPipes for Kafka'
slug: /integrations/clickpipes/kafka/faq
sidebar_position: 1
title: 'Kafka ClickPipes FAQ'
doc_type: 'guide'
keywords: ['kafka faq', 'clickpipes', 'upstash', 'azure event hubs', 'private link']
Kafka ClickPipes FAQ {#faq}
Ge... | {"source_file": "05_faq.md"} | [
-0.1003056988120079,
-0.08232297748327255,
-0.07367527484893799,
-0.005461952183395624,
-0.0027426595333963633,
-0.02339964173734188,
-0.029109766706824303,
0.00848359428346157,
0.05096021294593811,
0.015019507147371769,
-0.023967687040567398,
0.00567206647247076,
0.02295110374689102,
-0.0... |
d6de3e54-1b26-4491-98ff-2220002f351e | Azure Event Hubs {#azure-eventhubs}
Does the Azure Event Hubs ClickPipe work without the Kafka surface?
No. ClickPipes requires the Event Hubs namespace to have the Kafka surface enabled. This is only available in tiers above **basic**. See the [Azure Event Hubs documentation](https://learn.microsoft.com/en-us/az... | {"source_file": "05_faq.md"} | [
-0.008719460107386112,
-0.055929310619831085,
-0.06585418432950974,
0.0012353461934253573,
0.0047346241772174835,
0.050771936774253845,
0.021037176251411438,
-0.0738365575671196,
0.012370511889457703,
0.10395362228155136,
-0.03343517333269119,
-0.06684330850839615,
0.01816967874765396,
0.0... |
d9c75dad-dc3d-45cb-a591-12a286ddcbc3 | sidebar_label: 'Best practices'
description: 'Details best practices to follow when working with Kafka ClickPipes'
slug: /integrations/clickpipes/kafka/best-practices
sidebar_position: 1
title: 'Best practices'
doc_type: 'guide'
keywords: ['kafka best practices', 'clickpipes', 'compression', 'authentication', 'scaling'... | {"source_file": "04_best_practices.md"} | [
-0.06036306917667389,
0.04653467983007431,
-0.049164704978466034,
0.012146658264100552,
-0.025614088401198387,
-0.04636405035853386,
-0.061343155801296234,
0.015751468017697334,
-0.0018215778982266784,
0.027459152042865753,
-0.0410321019589901,
-0.005095204338431358,
-0.012288755737245083,
... |
8ac12382-4ce1-461e-924d-a08b90370a44 | Configuring a trusted relationship {#configuring-a-trusted-relationship}
If you are authenticating to MSK with a IAM role ARN, you will need to add a trusted relationship between your ClickHouse Cloud instance so the role can be assumed.
:::note
Role-based access only works for ClickHouse Cloud instances deployed t... | {"source_file": "04_best_practices.md"} | [
-0.08324730396270752,
0.01653241366147995,
-0.0970943495631218,
0.021262163296341896,
-0.04576358571648598,
-0.018417835235595703,
0.0277661494910717,
-0.06635428965091705,
0.04854559898376465,
0.039640747010707855,
0.029826007783412933,
-0.07799314707517624,
0.0934949666261673,
0.02812271... |
39a1e5dd-a702-4ac7-a63f-c6abe4697e67 | Benchmark details:
We used production ClickHouse Cloud services with enough resources to ensure that throughput was not bottlenecked by the insert processing on the ClickHouse side.
The ClickHouse Cloud service, the Kafka cluster (Confluent Cloud), and the ClickPipe were all running in the same region (
us-east-2... | {"source_file": "04_best_practices.md"} | [
-0.043604809790849686,
-0.02128995582461357,
-0.019578879699110985,
0.029261920601129532,
-0.015890993177890778,
-0.08411732316017151,
-0.1125384271144867,
-0.02971302904188633,
0.02877676859498024,
0.02943098545074463,
-0.03788788989186287,
0.01238353829830885,
0.01568753272294998,
-0.082... |
876036e1-0c60-4381-ba4c-648358809451 | title: 'Pausing and Resuming a MySQL ClickPipe'
description: 'Pausing and Resuming a MySQL ClickPipe'
sidebar_label: 'Pause table'
slug: /integrations/clickpipes/mysql/pause_and_resume
doc_type: 'guide'
keywords: ['clickpipes', 'mysql', 'cdc', 'data ingestion', 'real-time sync']
import Image from '@theme/IdealImage... | {"source_file": "pause_and_resume.md"} | [
-0.039991606026887894,
-0.05928893759846687,
-0.057518936693668365,
0.02582445554435253,
-0.03193289786577225,
0.020144009962677956,
0.04591367766261101,
0.006433498580008745,
-0.08098993450403214,
-0.008104388602077961,
-0.0017257436411455274,
0.011295914649963379,
0.0077559021301567554,
... |
3903484a-af1e-4043-b9de-2bc436992c2a | sidebar_label: 'Lifecycle of a MySQL ClickPipe'
description: 'Various pipe statuses and their meanings'
slug: /integrations/clickpipes/mysql/lifecycle
title: 'Lifecycle of a MySQL ClickPipe'
doc_type: 'guide'
keywords: ['clickpipes', 'mysql', 'cdc', 'data ingestion', 'real-time sync']
Lifecycle of a MySQL ClickPipe... | {"source_file": "lifecycle.md"} | [
-0.015905611217021942,
-0.043762825429439545,
-0.005117814522236586,
0.02320934273302555,
-0.0522749125957489,
-0.043778471648693085,
0.012937117367982864,
0.07324789464473724,
0.028474820777773857,
-0.026484355330467224,
0.016968997195363045,
-0.02376248873770237,
0.05690464749932289,
-0.... |
02e3f327-1768-45ea-91fe-20bf9e0442bf | Modifying {#modifying}
:::note
This state is coming soon. If you're using our
OpenAPI
, consider adding support for it now to ensure your integration continues working when it's released.
:::
Currently, this indicates the pipe is in the process of removing tables.
Resync {#resync}
:::note
This state is coming so... | {"source_file": "lifecycle.md"} | [
-0.02199043333530426,
0.013243435882031918,
0.016959795728325844,
0.03290228918194771,
0.0045092301443219185,
-0.10363936424255371,
-0.06875810027122498,
0.02169446088373661,
0.0057298303581774235,
-0.017965691164135933,
-0.005108298733830452,
-0.008274088613688946,
0.04224623367190361,
-0... |
7e52de03-a41b-47a5-b988-e9e042961c5b | title: 'Resyncing Specific Tables'
description: 'Resyncing specific tables in a MySQL ClickPipe'
slug: /integrations/clickpipes/mysql/table_resync
sidebar_label: 'Resync table'
doc_type: 'guide'
keywords: ['clickpipes', 'mysql', 'cdc', 'data ingestion', 'real-time sync']
Resyncing specific tables {#resync-tables}
... | {"source_file": "table_resync.md"} | [
-0.015283980406820774,
-0.059595879167318344,
0.020489942282438278,
0.012961884960532188,
-0.03859879821538925,
-0.08223039656877518,
-0.01506625022739172,
-0.027955321595072746,
-0.029703952372074127,
0.01482403464615345,
-0.011512836441397667,
0.03355424106121063,
0.08115995675325394,
-0... |
439f6055-eb79-4b55-ab72-a20a1ba0e743 | title: 'Adding specific tables to a ClickPipe'
description: 'Describes the steps need to add specific tables to a ClickPipe.'
sidebar_label: 'Add table'
slug: /integrations/clickpipes/mysql/add_table
show_title: false
doc_type: 'guide'
keywords: ['clickpipes', 'mysql', 'cdc', 'data ingestion', 'real-time sync']
imp... | {"source_file": "add_table.md"} | [
0.020868603140115738,
-0.0652121901512146,
-0.04090891778469086,
0.02463562786579132,
-0.038234103471040726,
-0.019045090302824974,
0.043668750673532486,
0.07374802231788635,
-0.04540511220693588,
0.016640426591038704,
0.023586438968777657,
-0.04709456488490105,
0.06494054943323135,
-0.025... |
697355c7-9676-41ee-b66d-b6b5c2386009 | title: 'Supported data types'
slug: /integrations/clickpipes/mysql/datatypes
description: 'Page describing MySQL ClickPipe datatype mapping from MySQL to ClickHouse'
doc_type: 'reference'
keywords: ['MySQL ClickPipe datatypes', 'MySQL to ClickHouse data types', 'ClickPipe datatype mapping', 'MySQL ClickHouse type conve... | {"source_file": "datatypes.md"} | [
0.03593125566840172,
-0.09149983525276184,
-0.0039770943112671375,
0.019466517493128777,
-0.1039169654250145,
-0.01619536243379116,
0.01666819117963314,
0.003788661677390337,
-0.07467063516378403,
-0.02378532476723194,
0.013444799929857254,
-0.06340904533863068,
0.06151200085878372,
-0.006... |
49ad499a-2585-45e4-9739-5f0eeb5ac135 | title: 'Resyncing a Database ClickPipe'
description: 'Doc for resyncing a database ClickPipe'
slug: /integrations/clickpipes/mysql/resync
sidebar_label: 'Resync ClickPipe'
doc_type: 'guide'
keywords: ['clickpipes', 'mysql', 'cdc', 'data ingestion', 'real-time sync']
import resync_button from '@site/static/images/in... | {"source_file": "resync.md"} | [
-0.08074789494276047,
-0.06567052006721497,
-0.02938106097280979,
0.0472337044775486,
0.04999426752328873,
-0.10046876966953278,
0.019813142716884613,
-0.0037966326344758272,
0.015987785533070564,
0.014747701585292816,
-0.010440277867019176,
0.06192219629883766,
0.049466706812381744,
-0.10... |
95182c4c-2eb6-453c-8374-b2c91b760ff0 | title: 'Removing specific tables from a ClickPipe'
description: 'Removing specific tables from a ClickPipe'
sidebar_label: 'Remove table'
slug: /integrations/clickpipes/mysql/removing_tables
doc_type: 'guide'
keywords: ['clickpipes', 'mysql', 'cdc', 'data ingestion', 'real-time sync']
import Image from '@theme/Idea... | {"source_file": "remove_table.md"} | [
0.007093426771461964,
0.047878414392471313,
0.012357734143733978,
0.006185202393680811,
0.020069800317287445,
-0.10039383172988892,
0.07607848942279816,
-0.038044869899749756,
-0.0071590798906981945,
0.017488012090325356,
0.017678841948509216,
0.03185832127928734,
0.08887598663568497,
-0.0... |
359b3c85-7e1a-459b-9dc9-3f6d872f2743 | sidebar_label: 'FAQ'
description: 'Frequently asked questions about ClickPipes for MySQL.'
slug: /integrations/clickpipes/mysql/faq
sidebar_position: 2
title: 'ClickPipes for MySQL FAQ'
doc_type: 'reference'
keywords: ['MySQL ClickPipes FAQ', 'ClickPipes MySQL troubleshooting', 'MySQL ClickHouse replication', 'ClickPip... | {"source_file": "faq.md"} | [
-0.030577998608350754,
-0.07602846622467041,
-0.025883862748742104,
-0.013467149809002876,
-0.030413148924708366,
-0.0015949108637869358,
0.04427623003721237,
0.023107828572392464,
-0.036183662712574005,
-0.041890427470207214,
-0.011655525304377079,
-0.022250806912779808,
0.10278796404600143... |
2b421900-0ab1-464e-8dae-259009cdd49a | Configure server certificate
- Update your server's SSL certificate to include all connection hostnames and use a trusted Certificate Authority.
Skip certificate verification
- For self-hosted MySQL or MariaDB, whose default configurations provision a self-signed certificate we can't validate (
MySQL
,
MariaDB... | {"source_file": "faq.md"} | [
0.04292002320289612,
-0.034386683255434036,
0.0311242938041687,
0.025033237412571907,
-0.07116126269102097,
-0.0643119364976883,
-0.051251120865345,
-0.019198086112737656,
0.013025941327214241,
-0.0073484270833432674,
-0.005790211260318756,
-0.103640615940094,
0.12272962182760239,
0.107822... |
62aad56a-adfe-47b9-98ff-de4e9a89f175 | title: 'Schema Changes Propagation Support'
slug: /integrations/clickpipes/mysql/schema-changes
description: 'Page describing schema change types detectable by ClickPipes in the source tables'
doc_type: 'reference'
keywords: ['clickpipes', 'mysql', 'cdc', 'data ingestion', 'real-time sync']
ClickPipes for MySQL can... | {"source_file": "schema-changes.md"} | [
-0.011498824693262577,
-0.08431852608919144,
0.03148460388183594,
-0.01764039881527424,
-0.015711085870862007,
-0.07972782850265503,
-0.008777589537203312,
-0.07552272081375122,
0.016315506771206856,
0.016836676746606827,
0.026600992307066917,
-0.07170428335666656,
0.0662127360701561,
-0.0... |
e673311e-db1f-43fb-a8cd-d5dde6d46bd0 | sidebar_label: 'Ingesting Data from MySQL to ClickHouse'
description: 'Describes how to seamlessly connect your MySQL to ClickHouse Cloud.'
slug: /integrations/clickpipes/mysql
title: 'Ingesting data from MySQL to ClickHouse (using CDC)'
doc_type: 'guide'
keywords: ['MySQL', 'ClickPipes', 'CDC', 'change data capture', ... | {"source_file": "index.md"} | [
0.01603030040860176,
-0.001993450103327632,
-0.05177920311689377,
0.000149192608660087,
-0.04050374776124954,
-0.028619779273867607,
0.08905234187841415,
0.052347563207149506,
-0.057927217334508896,
0.00041624141158536077,
0.059583794325590134,
-0.047562532126903534,
0.10448981821537018,
-... |
466f1fc8-2257-4b3f-97ed-095f840a3755 | (Optional) Set up SSH Tunneling {#optional-set-up-ssh-tunneling}
You can specify SSH tunneling details if your source MySQL database is not publicly accessible.
Enable the "Use SSH Tunnelling" toggle.
Fill in the SSH connection details.
To use Key-based authentication, click on "Revoke and generate key ... | {"source_file": "index.md"} | [
0.05140271782875061,
-0.0010830111568793654,
-0.0776137039065361,
-0.008428196422755718,
-0.09804241359233856,
0.038599416613578796,
-0.013747245073318481,
0.018173623830080032,
0.017546387389302254,
0.058653730899095535,
-0.030629020184278488,
-0.07203274965286255,
0.11132024228572845,
0.... |
21d72189-6a01-4b8c-a3b9-28941aa1889c | Finally, please refer to the
"ClickPipes for MySQL FAQ"
page for more information about common issues and how to resolve them.
What's next? {#whats-next}
Once you've set up your ClickPipe to replicate data from MySQL to ClickHouse Cloud, you can focus on how to query and model your data for optimal performance. F... | {"source_file": "index.md"} | [
0.05987619608640671,
-0.08501183241605759,
-0.00273496494628489,
-0.0043556056916713715,
-0.0418374128639698,
-0.09455364942550659,
-0.010919229127466679,
-0.03166233375668526,
-0.01756029576063156,
0.06086401641368866,
0.026203524321317673,
-0.04070764780044556,
0.11813094466924667,
-0.04... |
3249833f-c00b-4c38-b4f9-f03130add606 | title: 'Controlling the Syncing of a MySQL ClickPipe'
description: 'Doc for controllling the sync a MySQL ClickPipe'
slug: /integrations/clickpipes/mysql/sync_control
sidebar_label: 'Controlling syncs'
keywords: ['MySQL ClickPipe', 'ClickPipe sync control', 'MySQL CDC replication', 'ClickHouse MySQL connector', 'databa... | {"source_file": "controlling_sync.md"} | [
-0.024317607283592224,
-0.06771522015333176,
-0.08074220269918442,
0.04588812589645386,
-0.07360856235027313,
-0.010809528641402721,
0.030885016545653343,
0.0037657886277884245,
-0.0691370740532875,
0.03887917101383209,
0.017083365470170975,
-0.008404014632105827,
0.06732063740491867,
-0.0... |
8df9bd60-6197-4b76-b309-c469d82f896f | When editing an existing ClickPipe, you can head over to the
Settings
tab of the pipe, pause the pipe and then click on
Configure
here:
This will open a flyout with the sync settings, where you can change the sync interval and pull batch size:
Monitoring sync control behaviour {#monitoring}
You can see ho... | {"source_file": "controlling_sync.md"} | [
0.040583882480859756,
-0.06147923320531845,
-0.05044243857264519,
-0.005001377779990435,
-0.034734565764665604,
-0.017865626141428947,
-0.06638180464506149,
-0.019202137365937233,
-0.0026980380062013865,
-0.006414158269762993,
0.010900510475039482,
-0.009357364848256111,
-0.09827900677919388... |
819b8af8-6228-4f67-bac5-01d1c6e3392f | title: 'Parallel Snapshot In The MySQL ClickPipe'
description: 'Doc for explaining parallel snapshot in the MySQL ClickPipe'
slug: /integrations/clickpipes/mysql/parallel_initial_load
sidebar_label: 'How parallel snapshot works'
doc_type: 'guide'
keywords: ['clickpipes', 'mysql', 'cdc', 'data ingestion', 'real-time syn... | {"source_file": "parallel_initial_load.md"} | [
-0.04509308934211731,
-0.046076733618974686,
-0.05745523050427437,
-0.029370315372943878,
-0.05031722038984299,
-0.0713401660323143,
-0.00832501333206892,
0.052362680435180664,
-0.010235428810119629,
0.03848229721188545,
0.03642234578728676,
0.010409682057797909,
0.09915044158697128,
-0.09... |
76c1dbb1-4415-4a16-a105-9adddb377611 | Snapshot number of tables in parallel {#tables-parallel-mysql-snapshot}
Not really related to parallel snapshot, but this setting controls how many tables are processed in parallel during the initial load. The default value is 1. Note that is on top of the parallelism of the partitions, so if you have 4 partitions an... | {"source_file": "parallel_initial_load.md"} | [
0.0342167504131794,
-0.09806305915117264,
-0.04721441864967346,
-0.022371400147676468,
-0.039205268025398254,
-0.05429772287607193,
0.015901649370789528,
0.017850739881396294,
0.04096071422100067,
0.01566472463309765,
-0.01619609259068966,
-0.06129875034093857,
0.1105942577123642,
-0.09226... |
e39f90df-10c3-4e97-8383-1582813451ea | sidebar_label: 'Reference'
description: 'Details supported formats, exactly-once semantics, view-support, scaling, limitations, authentication with object storage ClickPipes'
slug: /integrations/clickpipes/object-storage/reference
sidebar_position: 1
title: 'Reference'
doc_type: 'reference'
integration:
- support_lev... | {"source_file": "02_reference.md"} | [
-0.042246926575899124,
-0.0047827851958572865,
-0.11375643312931061,
-0.04251544922590256,
0.07021022588014603,
0.0009188308613374829,
0.018007377162575722,
0.017637092620134354,
-0.0005910840700380504,
0.02556598372757435,
0.002003266243264079,
-0.0021519039291888475,
0.05432240292429924,
... |
f10680b7-7ab6-4192-9f44-8678848d7837 | Materialized views on the target table are also supported. ClickPipes will create staging tables not only for the target table, but also any dependent materialized view.
We do not create staging tables for non-materialized views. This means that if you have a target table with one of more downstream materialized view... | {"source_file": "02_reference.md"} | [
0.0034551143180578947,
-0.0975092276930809,
-0.04858660697937012,
0.0009165217634290457,
-0.058307014405727386,
-0.08611008524894714,
-0.008180387318134308,
-0.010480694472789764,
-0.049597542732954025,
0.026080261915922165,
-0.014016283676028252,
-0.042124923318624496,
-0.03543532267212868,... |
3f2cc947-7d2a-4a3c-8b24-b0b2333aa3b3 | https://datasets-documentation.s3.eu-west-3.amazonaws.com/http/{documents-01,documents-02}.ndjson.gz
:::
Continuous Ingest {#continuous-ingest}
ClickPipes supports continuous ingestion from S3, GCS, Azure Blob Storage, and DigitalOcean Spaces. When enabled, ClickPipes continuously ingests data from the specified pa... | {"source_file": "02_reference.md"} | [
-0.04443880915641785,
-0.048340436071157455,
-0.07608411461114883,
-0.02723694033920765,
0.04771948233246803,
-0.042149439454078674,
0.03908592835068703,
-0.058568648993968964,
0.06489909440279007,
0.03728235885500908,
0.058632273226976395,
0.022078966721892357,
0.0033932477235794067,
-0.0... |
8dc4afa4-c07a-42a0-9241-d3a724a3b336 | sidebar_label: 'Create your first object storage ClickPipe'
description: 'Seamlessly connect your object storage to ClickHouse Cloud.'
slug: /integrations/clickpipes/object-storage
title: 'Creating your first object-storage ClickPipe'
doc_type: 'guide'
integration:
- support_level: 'core'
- category: 'clickpipes'
... | {"source_file": "01_create_clickpipe_for_object_storage.md"} | [
-0.029398206621408463,
-0.012999807484447956,
-0.05147598311305046,
0.00597370183095336,
-0.036042965948581696,
-0.039632607251405716,
0.007475385442376137,
0.0702878087759018,
-0.03910720348358154,
0.027919556945562363,
0.0415322370827198,
-0.07246431708335876,
0.05559423193335533,
-0.011... |
e152e94f-3ebd-41f2-bca6-2c8a06bc5445 | Configure table, schema and settings {#5-configure-table-schema-settings}
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 you... | {"source_file": "01_create_clickpipe_for_object_storage.md"} | [
0.05563914775848389,
-0.04969127103686333,
-0.12167428433895111,
0.03400769084692001,
-0.03148268163204193,
-0.0429537408053875,
0.04701479151844978,
-0.0030875294469296932,
-0.12726855278015137,
0.03554486855864525,
0.04232294484972954,
-0.07829096168279648,
0.024730758741497993,
0.008953... |
a07ad64e-70ed-465b-9068-a58779f3f2ec | description: 'Landing page with table of contents for the object storage ClickPipes section'
slug: /integrations/clickpipes/object-storage/index
sidebar_position: 1
title: 'Object storage ClickPipes'
doc_type: 'landing-page'
| Page | Description |
|-----|-----|
|
Reference
| Details supported formats, exactly-o... | {"source_file": "index.md"} | [
-0.010194786824285984,
-0.05307226628065109,
-0.058046698570251465,
0.001943042385391891,
-0.0007790977251715958,
-0.012672405689954758,
-0.022976873442530632,
-0.00941848661750555,
-0.032980918884277344,
0.046856075525283813,
-0.03342560678720474,
0.01284970622509718,
-0.0037365765310823917... |
8d846974-9bbe-400a-ba9a-f5406a9c45da | sidebar_label: 'FAQ'
description: 'FAQ for object storage ClickPipes'
slug: /integrations/clickpipes/object-storage/faq
sidebar_position: 1
title: 'FAQ'
doc_type: 'reference'
integration:
- support_level: 'core'
- category: 'clickpipes'
FAQ {#faq}
Does ClickPipes support GCS buckets prefixed with `gs://`?
... | {"source_file": "03_faq.md"} | [
-0.0619509220123291,
-0.03911810740828514,
-0.014756240881979465,
0.000643144128844142,
-0.014093787409365177,
-0.013810799457132816,
0.03729171305894852,
-0.0007245703600347042,
-0.040966104716062546,
0.02647118642926216,
-0.028035840019583702,
-0.02465192787349224,
0.01674698293209076,
-... |
b5d23196-e272-4c30-85e4-3222a8004ad8 | sidebar_label: 'MongoDB Atlas'
description: 'Step-by-step guide on how to set up MongoDB Atlas as a source for ClickPipes'
slug: /integrations/clickpipes/mongodb/source/atlas
title: 'MongoDB Atlas source setup guide'
doc_type: 'guide'
keywords: ['clickpipes', 'mongodb', 'cdc', 'data ingestion', 'real-time sync']
im... | {"source_file": "atlas.md"} | [
-0.022311802953481674,
0.07147874683141708,
-0.03689594939351082,
0.09292984008789062,
0.016979722306132317,
-0.03666681796312332,
-0.023471737280488014,
0.021648673340678215,
-0.03356505185365677,
-0.031411729753017426,
-0.01460288092494011,
-0.049990516155958176,
-0.01326039433479309,
-0... |
1fc13b79-563a-4e44-8d1d-c2cde6f61939 | sidebar_label: 'Generic MongoDB'
description: 'Set up any MongoDB instance as a source for ClickPipes'
slug: /integrations/clickpipes/mongodb/source/generic
title: 'Generic MongoDB source setup guide'
doc_type: 'guide'
keywords: ['clickpipes', 'mongodb', 'cdc', 'data ingestion', 'real-time sync']
Generic MongoDB so... | {"source_file": "generic.md"} | [
-0.006985634099692106,
-0.0010106588015332818,
0.000584848748985678,
0.062209341675043106,
-0.001157871913164854,
-0.0972185879945755,
-0.08876656740903854,
0.031892478466033936,
0.014028066769242287,
-0.007807780057191849,
0.006398805417120457,
0.022163331508636475,
-0.027017101645469666,
... |
34bffd6b-7973-4aec-a00e-bc8e04cefc3a | sidebar_label: 'Amazon Aurora Postgres'
description: 'Set up Amazon Aurora Postgres as a source for ClickPipes'
slug: /integrations/clickpipes/postgres/source/aurora
title: 'Aurora Postgres Source Setup Guide'
doc_type: 'guide'
keywords: ['Amazon Aurora', 'PostgreSQL', 'ClickPipes', 'AWS database', 'logical replication... | {"source_file": "aurora.md"} | [
-0.014361228793859482,
-0.015666430816054344,
-0.11378559470176697,
0.024268101900815964,
-0.0009387956233695149,
-0.0016941337380558252,
0.017067335546016693,
-0.042383596301078796,
-0.036568623036146164,
0.03577358275651932,
0.07773034274578094,
-0.00798097811639309,
-0.003977328073233366,... |
39c85892-a931-41f2-9db9-c1a478ce8db7 | Grant schema permissions. The following example shows permissions for the
public
schema. Repeat these commands for each schema you want to replicate:
sql
GRANT USAGE ON SCHEMA "public" TO clickpipes_user;
GRANT SELECT ON ALL TABLES IN SCHEMA "public" TO clickpipes_user;
ALTER DEFAULT PRIVILEGES IN SCHEMA "public" G... | {"source_file": "aurora.md"} | [
0.0394648052752018,
-0.029980050399899483,
-0.1262015700340271,
0.02229437045753002,
-0.03716696426272392,
0.009894677437841892,
0.04017787426710129,
-0.054143745452165604,
-0.04768691211938858,
0.07705558836460114,
-0.03253580629825592,
-0.0696307122707367,
0.05926769971847534,
0.02320339... |
87855712-b734-46f4-9ba9-23bfd3a9ba0f | sidebar_label: 'Timescale'
description: 'Set up Postgres with the TimescaleDB extension as a source for ClickPipes'
slug: /integrations/clickpipes/postgres/source/timescale
title: 'Postgres with TimescaleDB source setup guide'
keywords: ['TimescaleDB']
doc_type: 'guide'
import BetaBadge from '@theme/badges/BetaBadg... | {"source_file": "timescale.md"} | [
-0.0461387112736702,
0.02447037771344185,
-0.06420842558145523,
0.03403181582689285,
-0.04653913527727127,
0.004227254074066877,
-0.009335614740848541,
0.009850408881902695,
0.0031107019167393446,
0.012375680729746819,
-0.05714040994644165,
0.03514513745903969,
-0.0009096217690967023,
-0.0... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.