- 🇳🇿New Zealand janpongos
I got the same issue as well. I wonder what causes the timestamp to use a milliseconds value instead of seconds.
I think if all timestamp are in seconds, the issue will be resolve. So for now I use this patch to force convert the value into seconds if it found any milliseconds.
It will really be good if anyone can point out why timestamps got into milliseconds in the first place, then this should not be an issue.
Patch is for version 3.0.0-beta1.
- 🇬🇧United Kingdom gsquirrel London
Not sure if this helps to debug this but I only had this issue after switching from database backend to elastic search - are any others with the issue also using elastic search?
In the end I found a workaround using a custom field added to the index that stored year only via a token - then used that as facet source instead.