Handling OData properties

[joshgav]

We should consider how to make the libraries resilient to

1. unexpected additional properties or
2. missing metadata-specified properties.

The OData spec calls for clients to never fail when they find additional properties, as 1) minor version updates and 2) open types are allowed to add properties even without clients being aware of them. So for unexpected additional properties we should log that additional properties were received but not throw any error.

For missing metadata-specified properties:

• If Key properties are missing we should throw an error immediately.
• If non-Key properties are missing, perhaps we should only throw an error if/when that property is directly accessed?

[PabloZaiden]

For (1) the library just ignores the extra properties, and the missing properties are deserialized with the default java value for each entity

[joshgav]

So we're good on (1).

For (2), as I understand the spec the value should be set to null. Search for the word "null" in OData-Protocol.