You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, I'd like to thank you for your amazing work! This issue is rather minor, but I thought I'd raise it anyway for you to have it in the backlog.
PS : I haven's see this behavior describe in other issues, sorry if it was already discussed elsewhere.
Describe the bug
On the 0.13.0 version of Datahub, when browsing the OpenAPI page to the HEAD [/v2/entity/dataproduct/{urn}/globaltags] operation of the GlobalTags Aspect, the API returns a HTTP 204 Code if GlobalTags for the corresponding DataProduct urn exists, but the documentation states that an HTTP 200 Code should be returned in that case.
Would it be possible to align the OpenAPI specification with the actual API behavior?
To Reproduce
Steps to reproduce the behavior:
Open the OpenAPI - Swagger UI of the 0.13.0 version of DataHub
Browse to the HEAD [/v2/entity/dataproduct/{urn}/globaltags] operation of the GlobalTags Aspect of the API.
Search GlogalTags for a valid DataProduct urn containing at least one GlobalTag
The API answers with a 204 HTTP return code, whereas the Swagger specifies that a 200 return code should be returned instead
Expected behavior
The API should return an HTTP 200 OK code in that scenario, or the Swagger should be updated to state that an HTTP 204 return code is the behavior to expect.
Screenshots
Desktop (please complete the following information):
OS: Ubuntu 22.04 LTS
Browser: Firefox 122.0.1 (64 bits)
Version: 0.13.0
Additional context
None
The text was updated successfully, but these errors were encountered:
This issue is stale because it has been open for 30 days with no activity. If you believe this is still an issue on the latest DataHub release please leave a comment with the version that you tested it with. If this is a question/discussion please head to https://slack.datahubproject.io. For feature requests please use https://feature-requests.datahubproject.io
Hello,
First of all, I'd like to thank you for your amazing work! This issue is rather minor, but I thought I'd raise it anyway for you to have it in the backlog.
PS : I haven's see this behavior describe in other issues, sorry if it was already discussed elsewhere.
Describe the bug
On the
0.13.0
version of Datahub, when browsing the OpenAPI page to theHEAD [/v2/entity/dataproduct/{urn}/globaltags]
operation of the GlobalTags Aspect, the API returns a HTTP 204 Code if GlobalTags for the corresponding DataProduct urn exists, but the documentation states that an HTTP 200 Code should be returned in that case.Would it be possible to align the OpenAPI specification with the actual API behavior?
To Reproduce
Steps to reproduce the behavior:
0.13.0
version of DataHubHEAD [/v2/entity/dataproduct/{urn}/globaltags]
operation of the GlobalTags Aspect of the API.Expected behavior
The API should return an HTTP 200 OK code in that scenario, or the Swagger should be updated to state that an HTTP 204 return code is the behavior to expect.
Screenshots
Desktop (please complete the following information):
Additional context
None
The text was updated successfully, but these errors were encountered: