Hello, I initially posted this in <#CUMUWQU66|inge...
# getting-started
d
Hello, I initially posted this in #ingestion but I think this is probably the better spot for my question. I am new here and new to datahub in general. I am on version: 0.12.1.4 We are looking at datahub primarily for its metadata and dataset lineage capabilities with a focus on supporting our parquet based data lake and distributed access client, but I think we could potentially find broad utility across the firm's data and analytics teams. I am using the python sdk for ingestion and hope to also leverage the graphql api for pulling metadata back to the client, which would help simplify our current metadata workflow. My simple POC so far is working fairly well. However, I am a little stuck on figuring out how to use the emitters to push Queries up to the UI for a given dataset. Having an example query, tied to a dataset adds a lot of value for me. I see there is a QueryStatementClass, but I can't find any documentation. Am I on the right path here, is adding queries to the UI via the SDk a viable option, and if so, is there an example anywhere on what that might look like? For reference, I am referring to the queries tab under Dataset: EDIT: I was able to hack my way to accomplishing this using gql, but would prefer to standardize my integrations on the python SDK if at all possible.
b
I dunno if you'll get a reply, and honestly I have not pushed a query before, but I'll hazard a guess that it should be similar to the other aspects - using the sdk, instantiate the graph class to connect to gms, create a copy of the querystatement class, and wrap it in the metadataproposalwrapper before using the graph to emit it. Or you could just wait for a better informed reply. Like the samples here https://github.com/datahub-project/datahub/blob/master/metadata-ingestion/examples/library/dataset_add_owner.py
thanks bear 1
d
Thanks, I'll try it out.
l
Hey @dazzling-solstice-43361! In this didn’t work out for ya, wanted to plug our live Community Marathon on Thursday — this would be a great options to chat with our core engineers in the Getting Started sessions teamwork