You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<td> <b>Multi-Tenancy | Partitioning | Linear Scalability</b> <br> Redis Connect manages multi-tenant replication pipelines. A pipeline from source to sink is known as a job. Jobs with different source types can be collocated without becoming noisy neighbors. Jobs can be partitioned for linear scalability across one or more cluster nodes.</td>
<td> <b>High-Availability | Recovery</b> <br> Redis Connect jobs update their checkpoint upon each committed changed-data event within a transactional scope. In the event of a node failure or network split, in-flight jobs will fail over to another node and seamlessly begin replication from the last committed checkpoint. Data is not lost, and order is preserved. Redis Connect works in container orchestration environments such as Kubernetes and OpenShift.</td>
<td> <b>Custom Transformations</b> <br> Redis Connect jobs support user-defined business logic. You can create custom workflows that include user-defined stages for proprietary business rules, custom transformations, de-tokenization, and more. You can also extend the supported list of target sinks.</td>
<td> <b>REST API | CLI | Swagger UI</b> <br> Redis Connect is entirely data-driven and relies on Redis Enterprise as its metadata store. You can configure, start, stop, migrate, and restart jobs using the built-in REST API and interactive CLI. Redis Connect also exposes a Swagger UI to simplify endpoint discovery and operational experience.</td>
<td> <b>Enterprise-Grade Security</b> <br> Redis Connect jobs are stateless, so changed-data events are always in-transit. Redis Connect benefits from Redis Enterprise’s security, including RBAC, TLS, and more. Credentials, secrets, and trust-store passwords are never stored in Redis Connect; these secrets can be dynamically rotated with minimal disruption to the replication pipeline. Vault integration is supported.</td>
| Update `credentials.file.path` and `redis.connection.url` in `/config/jobmanager.properties`<br/> Example - <ahref="/examples/postgres/demo/config/jobmanager.properties">jobmanager.properties</a> |
| Update `credentials.file.path` and `redis.connection.url` in `/config/jobmanager.properties`<br/> Example - <ahref="/examples/postgres/demo/config/jobmanager.properties">jobmanager.properties</a> |
| Update `credentialsFilePath`, `databaseURL`, `database.dbname`, `database.hostname`, `database.port`, `schemaAndTableName`, and `columns` within sample job configuration for source and target, where applicable.|
| Update `credentialsFilePath`, `databaseURL`, `database.dbname` (`database.names` for SQL Server), `database.hostname`, `database.port` and `columns` within sample job configuration for source and target, where applicable. |
Copy file name to clipboardExpand all lines: examples/vertica/demo/config/samples/payloads/cdc-job.json
-2Lines changed: 0 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,6 @@
38
38
"partitions": 2,
39
39
"selectQuery": "SELECT * FROM (SELECT ALIAS.*, ROW_NUMBER() OVER (ORDER BY employee_key) RowIndex FROM public.employee_dimension ALIAS) ALIAS WHERE ALIAS.RowIndex >= ${start} AND ALIAS.RowIndex <= ${end}"
"selectQuery": "SELECT * FROM (SELECT ALIAS.*, ROW_NUMBER() OVER (ORDER BY customer_key) RowIndex FROM public.customer_dimension ALIAS) ALIAS WHERE ALIAS.RowIndex >= ${start} AND ALIAS.RowIndex <= ${end}"
0 commit comments