Hi team,how to customize job name?
# troubleshootingh
hello_dev
07/18/2022, 1:15 PMHi team,how to customize job name?
hello_dev
07/19/2022, 1:40 PMhave any suggestions? I don't want to use the default job name
a
aaronsteers
07/20/2022, 1:13 AMCan you say a bit more about your use case and your preference for not using the default name/convention?
aaronsteers
07/20/2022, 1:15 AMWe have plans to give users ability to create their own naming convention but this is specifically to allow outside factors to provide additional uniqueness, such as dynamic input variables that would change the extraction logic and therefore also need to be fed into the state ID.
h
hello_dev
07/20/2022, 3:14 AMHi @aaronsteers , the default job name is like
dev:tap-mysql-to-target-postgresdata001-to-dwa
aaronsteers
07/21/2022, 4:35 PMNow that job IDs (or "state IDs" in post-2.0) are internal and presumably automatic, can you say more about why you have this preference? For instance, is it primarily cosmetic, or is this because you want the same state to intentionally be recycled across different environments, or is it because you want to match a state ID from previous
meltano eltc
connor_lough
07/22/2022, 1:29 AMHi AJ, I have this same want as well.
This is because I have multiple postgres databases so I'm asssuming
dev:tap-postgres-to-target-snowflakea
aaronsteers
07/22/2022, 2:02 AMHi, @connor_lough. Specifically, for your use case, we recommend creating multiple instance of the Postgres tap using "inherits from" syntax. So, tap-postres-hr and tap-postgres-marketing would have distinct names while still leveraging the same underlying extractor. What do you think of this approach?
aaronsteers
07/22/2022, 2:04 AMThe added benefit of this approach is that each instance can override config and select rules as needed, among other things.
c
connor_lough
07/22/2022, 1:00 PMlove it, that'll work for me!
I do think that on default, the project_id or some other unique identifier should be added to the end of that name.