-
-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with disabling a table in the replication yaml after upgrade #441
Comments
I am unable to reproduce. Below works for me. Perhaps you have some white space character somewhere? source: MSSQL
target: POSTGRES
defaults:
mode: full-refresh
object: mssql.{stream_table}
streams:
dbo.*:
dbo.test1k_sqlserver_bcp_wide:
disabled: true |
Very strange. I've copy/pasted your yaml from above, still not working. I've tried in a brand new virtual environment, still not working. Seem to be in the def _run(cmd: str, temp_file: str, return_output=False, env:dict=None, stdin=None): function that it's having issues:
Something odd in my python env I can only assume. |
Oh, you're not using the CLI? Can you share your python code? |
Sure. This is in a notebook, using Python 3.12.3
test5.yaml=
|
Issue Description
There seems to be an issue using the 'disabled' flag in the stream section of the replication yaml, which seems to have started with the 1.2.22 update I did earlier today.
Sling version (
sling --version
): 1.2.22Operating System (
linux
,mac
,windows
): macReplication Configuration:
This YAML works correctly (i.e. dbo.staging_node_usage2 is ignored from the replication):
This generates an error:
Error message:
The text was updated successfully, but these errors were encountered: