set up multiple tables #168
Description
Describe the bug
A clear and concise description of what the bug is, with verbose log.
To Reproduce
Steps to reproduce the behaviour:
- Source table DDL
- Sink table DDL
- ReplicaDB configuration
options-file.
root@ip-172-30-2-231:/opt/conf# cat replicadb.conf
######################## ReplicadB General Options ########################
mode=incremental
jobs=1
fetch.size=100
verbose=true
Help us to improve by activating usage analysis through the Sentry service. Or set up your own Sentry DSN
sentry.dsn=https://400e0daa08c24a399b842048c409416f@o1002451.ingest.sentry.io/5962725
############################# Soruce Options ##############################
source.connect=jdbc:sqlserver://segware.cg120h1yldzn.us-east-1.rds.amazonaws.com:1433;database=XXXXXX
source.user=replicadb
source.password=xxxxx
source.table=dbo.CENTRAL_MONITORADA_HISTORICO
############################# Sink Options ################################
sink.connect=jdbc:sqlserver://sqlserver-web.cg120h1yldzn.us-east-1.rds.amazonaws.com:1433;database=XXXXXX
sink.user=replicadb
sink.password=xxxxx
sink.staging.schema=SEGWARE_BOTTOM
sink.staging.table=dbo.CENTRAL_MONITORADA_HISTORICO
sink.disable.truncate=true
Expected behavior
How do I configure multiple tables in fields:
source.table and sink.staging.table
Additional context
Add any other context about the problem here. Running environment (cloud, on premise, java version..), source and sink technologies (Oracle, MySQL, Postgres...)
AWS RDS SQL Server Standard Edition 2014 to AWS RDS SQL Server Web Edition 2017