You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 30, 2018. It is now read-only.
We hadn't noticed the problem until we overlay an ES facet series on top of a series generated with an Arel query. Our mistake.
We have a filter in our Application controller which converts to the user's localtime. This doesn't (obviously) work for ES. But I think it should for Tire.
To convert to localtime, I was intending on mapping each timestamp to the users localtime.
However, I was wondering if there a more sophisticated way to do this?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Facets are all returned with a UTC timestamp.
We hadn't noticed the problem until we overlay an ES facet series on top of a series generated with an Arel query. Our mistake.
We have a filter in our Application controller which converts to the user's localtime. This doesn't (obviously) work for ES. But I think it should for Tire.
To convert to localtime, I was intending on mapping each timestamp to the users localtime.
However, I was wondering if there a more sophisticated way to do this?
The text was updated successfully, but these errors were encountered: