Open chicco785 opened 5 years ago
A new parameter to configure this should be defined in config.js. The default should be as it is now (i.e. ISO8601 format) in order to keep backward compatibility.
Now that Orion supports milliseconds, maybe this issue is obsolete and could be closed?
most probably that's correct. e2e test should be made
I understand you have a way to test the e2e for this issue. If I'm right it would be great if you could test and tell us :). Thanks!
as discussed here: https://github.com/telefonicaid/fiware-orion/issues/432 for
DataTime
type orion strips milliseconds.now timestamp send by the iot agent lib are all in
DataTime
type. So despite IoT Agent handles milliseconds, these are not stored in Orion.The proposal then is to be able to configure the "timestamp" type, either Unix timestamp, or to a valid alternative.