Replies: 2 comments 4 replies
-
Hi yes, should work, try as below. # env.yaml
connections:
S3_LAKE_ZONE_A:
type: s3
# this sets environment variables in sling process
variables:
path_prefix: /dev-binoy/elt/data_landing # replication.yaml
source: MY_MYSQL
target: S3_LAKE_ZONE_A
defaults:
object: {path_prefix}/{stream_schema}/{stream_table}/{YYYY}_{MM}_{DD}.parquet < - Use Path Prefix ?
target_options:
format: parquet
streams:
# all tables in schema, except "forbidden_table"
my_schema.*:
object: {stream_schema}/{stream_table}/{YYYY}_{MM}_{DD}/
target_options:
file_max_rows: 400000 # will split files into folder
env:
# ${path_prefix} pulls from environment variables in sling process or env
path_prefix: '${path_prefix}' |
Beta Was this translation helpful? Give feedback.
4 replies
-
Thank you, that resolves it |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi @flarco,
The docs at https://docs.slingdata.io/sling-cli/run/configuration#object-patterns mentions that there are lot of inbuilt variables that can be used to add some dynamic patterns for naming objects, etc.
Is it possible to use the variables defined in the
variables
section ofenv.yaml
file be accessed by all other task/replication/cli definitions via the{variable_name}
convention ?my
env.yaml
filemy
replication.yaml
fileBeta Was this translation helpful? Give feedback.
All reactions