DEV: LOG: Issues in CRUD of log data objects (HIGH PRIORITY)

This is the card to address the client identified issues in CRUD of log data objects. Please review and update with high priority. See below for detail as captured in the email from Xiangyi KONG . Sun 6/16/2019 9:16 PM.

Dear Drillflow team,
We have found the following issue during testing for log data objects:
(The issues can be reproduced by the sample data provided by Energistics http://w3.energistics.org/schema/WITSML_v1.4.1.1_Data_Schema/witsml_v1.4.1.1_data/XML_Examples/log_no_xsl.xml)
1. The element is missing in the response of WMLS_GetFromStore()
2. One of the logCurveInfo is missing in the response of WMLS_GetFromStore()
3. In V1311 response, the order of logCurveInfo is not consistent with the columns of log data
4. (This not only applies to log data objects) The “NaN” input in the numeric fields was not handled. Please refer to section 6.4.4.3 of WITSML Store API specification:
Nullable Parameters
If a client sends a value of NaN in a numeric field to the server, then the server MUST convert it to null or“not given”.

It would be appreciated if these issues can be followed up.