I'm not sure if this is considered bad practice bu...
# announcements
a
I'm not sure if this is considered bad practice but I'm wondering if I could setup a
dagster_type_materializer
for
ExpectationResults
. The basic use case is I'm looking to automatically persist
ExpectationResults
to a service. Please let me know if I should consider approaching the problem differently.
l
We've got something in the pipeline that might be up your alley 🙂 but the short answer is 'that's a concept mismatch, ExpectationResults aren't a dagster type
👍 1
a
Do you have any links to issues/tickets you can share? Sounds like I should probably switch to my own Dagster type in the meantime.
l
Nothing yet, but hopefully something usable should be in today's release
🙌 1
Have you heard of a library called Great Expectations?
k
Hi, wanted to follow up on this since I'm looking into materializing/saving expectation results somehow - I saw that there is a solid factory that integrates with the Great Expectations library - but there's only one function in it. Is this library being built out as the primary way to persist
ExpectationResults
?
l
This library is specifically for GE, not general expectation results
k
Got it, is there any other way to materialize/persist
ExpectationResults
? Curious about what you were alluding to above when you said you had something in the pipeline
l
There's likely going to be something in 0.10.0, but I can't speak more to it since my time with dagster (summer internship) ended 2 weeks ago