[jira] [Closed] (SENSSOFT-221) Elasticsearch 5.x does not support microsecond precision

2018-04-17 Thread Joshua Poore (JIRA)

 [ 
https://issues.apache.org/jira/browse/SENSSOFT-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joshua Poore closed SENSSOFT-221.
-
Resolution: Fixed

> Elasticsearch 5.x does not support microsecond precision
> 
>
> Key: SENSSOFT-221
> URL: https://issues.apache.org/jira/browse/SENSSOFT-221
> Project: SensSoft
>  Issue Type: Bug
>  Components: UserALE.js
>Affects Versions: UserALE.js 1.0.0
>Reporter: Michelle Beard
>Assignee: Rob Foley
>Priority: Major
> Fix For: UserALE.js 1.1.0
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> 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. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (SENSSOFT-221) Elasticsearch 5.x does not support microsecond precision

2017-11-20 Thread Rob Foley (JIRA)

 [ 
https://issues.apache.org/jira/browse/SENSSOFT-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rob Foley closed SENSSOFT-221.
--
Resolution: Fixed

> Elasticsearch 5.x does not support microsecond precision
> 
>
> Key: SENSSOFT-221
> URL: https://issues.apache.org/jira/browse/SENSSOFT-221
> Project: SensSoft
>  Issue Type: Bug
>  Components: UserALE.js
>Affects Versions: UserALE.js 0.2.0
>Reporter: Michelle Beard
>Assignee: Rob Foley
> Fix For: UserALE.js 0.2.0
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> 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. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)