https://datahubproject.io logo
Join Slack
Powered by
GraphQL always returns null for `editableSchemaMet...
# getting-started
c
GraphQL always returns null for 
editableSchemaMetadata
in 
versionedDataset
. OpenAPI does return value. Is it not implemented?
I get result when 
versionStamp
is empty. If I add a value to version stamp, that's when I get null result
b
@echoing-airport-49548 Can helo you out!
e
Hey @clever-lamp-13963 let me look into this for you and see what's going on
o
What VersionStamp are you using?
@echoing-airport-49548 pretty sure we only query for a few specific aspects with the versionstamp. So if someone took that stamp and tried to use it, it would only return the aspects the UI is looking for. You should be able to get any of the aspects back by adding 
;<aspectName>:<versionNumber>
to the stamp, but this isn't really intended for public use or manual construction of queries.
To clarify, you get a result for 
EditableSchemaMetadata
when you put in empty for versionStamp or just a result in general with 
EditableSchemaMetadata
as null?
c
I use a versionstamp like this 
browsePaths:0;dataPlatformInstance:0;datasetKey:0;schemaMetadata:0
I do get a proper result with values populated for 
EditableSchemaMetadata
when empty string is passed
o
The reason for this is editableSchemaMetadata is not specified in your versionStamp. When sending empty string it treats it as all aspects at version 0
VersionStamp is currently intended for internal use by the frontend to the backend rather than to be constructed manually by users so we don't really have it documented on how it works, but basically it will only give you what you ask for and only if that exists. So if you send in 
browsePaths:100
you wouldn't get anything, but if you send in 
editableSchemaMetadata:1
you would get the oldest version of that aspect. Each aspect:version pair is semi-colon separated in the list
6 Views
Open in Slack
PreviousNext
Powered by