Search metadata
Quick question:
What is "hasLenientDiscoverability" under the Metadata context?
You can find it as the response example here:
https://developers.thoughtspot.com/docs/rest-apiv2-metadata-search
I thought it would be because of the Discoverable Checkbox, but it does not seem to be... I got that as
hasLenientDiscoverability: true even when I have this checkbox unchecked.Search metadata
Many use cases are possible with the very V2.0 metadata/search endpoint
8 Replies
I think this property should show effectively if the answer is discoverable or not. Let me check as to why this might return true even if the box is unchecked.
Thank you @shikharTS !
Right now 50% of my examples are set as NOT Discoverable, but this property comes always as
True from the linked MetadataAPI.
I am using TrustedAuthTokenCookieless. (Not sure if that helps or not)
I think I found a possible cause...
- Create an Answer that is NOT Discoverable
- Go to the share icon and verify that it is NOT Discoverable
- Then make a change on this Answer and save
- Now go back to the share icon and verify that now IT IS Discoverable
Is that expected?This looks like a bug @Geovane. I was able to repro it as well. Let me raise this to the relevant team. But you might need to wait for the fix. If this is important for you, you can raise a ticket with your TS SRE and we can get the fix to you
Sure @shikharTS I assume it is a critical bug since private (not discoverable) TS resources could potentially be exposed to non-authorized users right?
Is there anything else I could provide to assist?
So these will not be exposed to non authorized users. As we can see, they will only be exposed if a user has access to underlying data sources(worksheets/table etc).
But if I have a private Answer, that could be visible to others that have access to the Datasource too.
Still think it is bad, but I will let the TS team prioritize.
Thanks for replying
I have raised a ticket internally and we should see a solution for this. Thanks for poinitng this out
Always happy to help @shikharTS 🙂
Just checking if we had an update on this bug. We are holding a feature release because of the Embed Answer problems