-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
DagsterSlingTranslator does not recognise target_prefix argument #20485
Comments
EDIT: disregard this message, and see the comment below! Hi @temminks - thanks again for reporting this. If you override the class without the
|
@temminks, Ok, I think I've found the issue with what you've shared above. Both
I believe that we can remove the dependency to pass the translator in two locations; I will create a ticket to track such an enhancement. |
Just to follow up here, a code change was pushed that makes it so you only have to specify the translator and replication config in the asset decorator. This is to avoid the confusion of the above scenario. You can see the details here: This change also makes it so you can use the Sling integration from an |
Dagster version
1.6.9
What's the issue?
I copied the
replication.yaml
from the embedded-elt docs and tried to customise the target asset key's prefix, using thetarget_prefix
argument inDagsterSlingTranslator()
. The parameter defaults totarget
.I'd expect the asset's key to be prefixed with
my_prefix
, but the prefix staystarget
. This is unexpected and different from what the documentation describes.What did you expect to happen?
The prefix of the asset should be set to the value provided in
target_prefix
of theDagsterSlingTranslator
.How to reproduce?
Follow the documentation for Dagster Embedded ELT (https://docs.dagster.io/integrations/embedded-elt). and try setting the
target_prefix
parameter.Deployment type
Local
Deployment details
No response
Additional information
No response
Message from the maintainers
Impacted by this issue? Give it a 👍! We factor engagement into prioritization.
The text was updated successfully, but these errors were encountered: