Hi Cris
I've used TZ param with UpdateXmlMessages and data are indexed with
default GMT value on field timestamp, but one hour less than current
date system.
I am doing test using command curl, so:
/curl http://10.240.234.133:8080/solr/update?TZ=Europe/Madrid
--data-binary @data.xml -H "
: I've used this configuration to my timestamp field and it's works
:
:
that is *really* not a good idea ...
doing something like that means you will be putting incorrect data into
your index, saying a doc was added an hour lafter it realy was, and
assuming that later when clients query
thanks Cris
I've used this configuration to my timestamp field and it's works
default="NOW+1HOUR" multiValued="false"/>
Anyway, I would like to know possible configuration of TZ parameter.
When you speak "clients can specify a "TZ" param", this means it is
possible configure TZ paramete
: when I've checked the new data, I see datetime value have one hour less than
: current date.
Please note the documentation about DateField (and TrieDateField which
extends it)...
https://lucene.apache.org/solr/4_1_0/solr-core/org/apache/solr/schema/DateField.html
The response format is *alwa
Hi
I am using timestamp field configured in the schema, so this way:
default="NOW" multiValued="false"/>
when I've checked the new data, I see datetime value have one hour less
than current date.
I though it was problem on java configuration so I include in JAVA_OPTS
= -Duser.timezone=Euro
