Hi Team..I have noticed that Datahub graphQL searc...
# troubleshoot
h
Hi Team..I have noticed that Datahub graphQL search API is only considering fieldTags field for pulling schema field level tag details though I saw there in one more field editedFieldTags in datasetindex_v2 index saving the added tag details for any schema field. So we are getting partial result from graphQL api. Can u pls look and suggest is there any other alternative ways to get all schema level tag details for now. I have used this sample query for pulling out all schema level tags : { search(input: {type: DATASET, query: "editedFieldTags:not null", start: 0, count: 50, }) { start count total searchResults { entity { urn ... on Dataset { urn type subTypes { typeNames } name platform { name } properties { name } tags { tags { tag { urn properties { name description } } } } schemaMetadata { fields { fieldPath jsonPath label tags { tags { tag { urn properties { name description } } } } } } } } } } }
a
Hi, could you describe your usecase and the desired result here, as well as what version you’re on? We can maybe point you to a better tool for the job
h
Hi @astonishing-answer-96712..I am using Datahub v0.9.5. I want to get the list of datasets (or entities) where we have schema field level tag associated. I observed in datasetindex_v2 index the field level tag details are added in two properties fieldTags & editedFieldTags based on scenario. I think when we are adding field level tag from Datahub UI, it stores the value in editedFieldTags property but when field level tag is created from ingestion it goes to fieldTags property of datasetindex_v2 index of elastic search. But the GraphQL API is only considering fieldTags property but not the editedFieldTags property. So the API result is partial. Which I think need to be enhanced. I was trying to use search GraphQL query for my purpose. Please look into the problem statement and provide your helpful input. Thanks...
a
Have you used the graphiQL explorer to confirm here?
It may be a bug report otherwise, though I wouldn’t be surprised if it’s been fixed on a more recent verison