[FLAGON-221] Elasticsearch 5.x does not support microsecond precision

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Done
• Affects Version/s: UserALE.js 2.0.0
• Fix Version/s: UserALE.js 2.0.0
• Component/s: UserALE.js
• Flags: Important
• Sprint: Sprint 14, Sprint 15
• Assignee: Rob Foley
• Reporter: Michelle Beard
• Created: 04/Aug/17 16:31
• Updated: 30/May/19 05:15
• Resolved: 30/May/19 05:15

Description

In order to do accurate sequence analysis, it is imperative that the clientTime generated by userALE is set to microseconds. Unfortunately, Elasticsearch only supports up to milliseconds. This impacts how sorting is done at the clientTime level.

Sub-Tasks

• Add Micro Second Field in UserALE.js to cover Elastic indexing and time encoding issues.: Closed
• Update Elasticsearch mapping to accurately parse clientTime variable from userale.js: Closed