Hi Hoss,
Thanks for the clarification again.
Now I can see where the problem resides. My client application was
formatting date fields using SimpleDateFormat and as you said, it assumes
host timezone configuration.
: your dateFormat object doesn't know that the 'Z' at the end of the string
you a
: I've a wrote a Unit Test in order to simulate the date processing. A high
I think you are missunderstanding what your test is doing, but i'll get to
that in a second...
: level detail of this problem is that it occurs only when used the JavaBin
: custom format (&wt=javabin), in this case the
Hi Hoss,
Thanks for the clarification.
I've a wrote a Unit Test in order to simulate the date processing. A high
level detail of this problem is that it occurs only when used the JavaBin
custom format (&wt=javabin), in this case the dates get back set with
environment UTC offset coordinates.
On
: When using SolrJ I've realized document dates are being modified according
: to the environment UTC timezone. The timezone is being set in the inner
: class ISO8601CanonicalDateFormat of DateField class.
The dates aren't "modified" based on UTC, they are formated in UTC before
being written to
Hi,
When using SolrJ I've realized document dates are being modified according
to the environment UTC timezone. The timezone is being set in the inner
class ISO8601CanonicalDateFormat of DateField class.
I've read some posts where people say Solr should be most locale and culture
agnostic. So, wh
