search

shamim8888 / asterixdb

Automatically exported from code.google.com/p/asterixdb
0 stars 0 forks source link

Change the way optional fields are encoded in Metadata.Datatype #899

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Right now optional fields in a closed type will be represented in the 
Metadata.Datatype dataset as a procedurally generated anonymous type of 
UNION(type,null). We need to not expose this implementation detail from the 
Metadata dataset, but rather expose the nullability of the type as part of the 
field itself. 

For example, consider a point type field in a closed type that is optional. The 
MD record for the enclosing type would look something like this: 

 { "FieldName": "sender-location","FieldType": "Field_sender-location_in_FacebookMessageType"}

While it would be better if it was exposed as something like:

{ "FieldName": "in-response-to", "FieldType":"point", "Optional":true}

Original issue reported on code.google.com by ima...@uci.edu on 13 Jun 2015 at 1:54