Aaron Sheldon - Hello ThoughtSpot Devs, I have ...
Hello ThoughtSpot Devs, I have notice a bug while using the Metadata Search endpoint
*.cloud/api/rest/2.0/metadata/search
. If the exclude_objects
array is present in the request JSON, even with something as simple as [ { type: "TABLE" } ]
, then the response is empty. For now we can work around this by not using the exclude_objects
property and filtering the response after it is returned.4 Replies
I see some issues with
[ { type: "TABLE" } ]
First I do not see type:table while looking at options in the playground.
Also, looks like identifier is a required field to add in exclude objects otherwise it throws an error..
Were you just getting empty results or did you get any error?
I'll have to check the logs to see if it was generating a 404. I also face the same issue when passing in a list of GUIDs to exclude
Type : "TABLE" will also throw an error though..
Yup, it is returning 400 - bad request. This happens if I just pass a type, such as LOGICAL_TABLE, or just pass a GUID in the identifier. So does this mean that for exclude_objects to parse correctly it requires by type and identifier?
Got it. Found the documentation that confirms both are required. I'll refactor the interface on our side