-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
UI exception after adding a data contract #10456
Comments
When deleting the datacontract via CLI, the issue seems to be persisting and now I have a broken entity I can't access anymore. |
The same happens when in the contract you specify a schema. This time the exception is: Trying to fetch the entity via Rest.li doesn't return any info to a connected data contract:
This makes me think that during the graphql call from the UI there's some cached element:
|
Same issue here, is anybody looking into this ? |
The issue persists even after deleting the document related to the datacontract in elasticsearch. |
Same issue here - it made the asset that i have attached the data contract to unusable even after removing the object. |
Hey everyone, I've opened a PR with a possible fix here: #10534 |
Thanks @jayacryl for addressing this! |
After adding the data contract below via:
datahub datacontract upsert -f mq.yaml
, when navigating to the dataset in UI I get:No enum constant com.linkedin.datahub.graphql.generated.AssertionType.FRESHNESS (code 400)
mq.yaml
I would have expected the data contract to show up in the UI under the validation tab. At the moment, the dataset is not accessible anymore because of said error.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: