: rather than seconds. This is how Java deals with time internally. I'm fairly : sure that this is also how Solr's date types work internally.
More specifically: the QParser is giving you that query, because the FieldType you have for the specified field (prbably TrieDateField) is parsing the low & high end points specified in the RangeQuery in order to determine what underlying index terms should be used for hte query. if you had a StrField that you were using to keep raw strings in, and it just so happened that you were using it to index formatted dates (but nothing in your solr config knew about that) then you'd get a string based range query using the raw strings you pass in. maybe you should backup and tell us more about your schema and your data and what you are doing in your custom request handler so we can understand if what you are describing is even a problem, or if you are just having a missunderstanding of what you are seeing in the debug output? https://people.apache.org/~hossman/#xyproblem -Hoss http://www.lucidworks.com/
