anyone know how i can use multiple threads but still ensure a certain table replicates before another one due to a custom sql that depends on it?

hey @mitty i think the best way is to create 2 consecutive replications in a pipeline. Btw you can use in-line replications (without having to create a separate file):

steps:

  - replication:
      source: ...
      target: ...
      streams:
        ...
      env: { SLING_THREADS: 3 }

  - replication:
      source: ...
      target: ...
      streams:
        ...

I'll give that a try thanks