log object queries are not filtering by index ranges, rowcount

[subwaylocations]

querying a log object, I cannot filter the data results using the startDateTimeIndex or endDateTimeIndex. Also, the query seems to ignore dataRowCount as well.

[bmdiaz]

Log query logic for WITSML 1.3.1.1 has recently been updated to address several bugs. Please get the latest source and try your queries again.

[Tsmith5151]

Is is possible to send a request to the server for specific units? For instance, a well may have recorded the log curves in imperial units, however would like to return in metrics. It does not appear you can force the data returned from the server to be of a particular type by modifying the "uom" field. Thanks!

[setiri]

T, by my recollection from the standard, you send the unit you desire in the query, but the server may send back whichever it prefers and the client has to convert it. So depending on the server design, it may always standardize on one set of units, or may convert to whichever you request, or may just store it however it originally was sent. (it's been a while since I read this though :)

[Tsmith5151]

Thanks @setiri . I assumed this might have been the case. Was hoping to avoid having to manually convert the log curves if this functionality existed in the current API.

[tonineumann]

Pulled the latest code. The time filtering is working correctly. The dataRowCountis not being honored by the server.

[nilsabenson]

@tonineumann dataRowCounts is totally controlled by the limits set in the configuration file(s). The process that fetches the data from the database applies these limits above all others. However, setting these limits too small, or too large has negative effects on all GetFromStore and log UpdateInStore queries leading to excessive CPU use or failed updates to existing data. We have forked the server to look at this and will be submitting a PR when it's done.