Re: Date Query Confusion

2018-05-17 Thread Tim Casey
A simple date range query does not really represent how people query over time and dates. If you want any form of date queries, above a single range, then a special field allowing tokenized query will be the only way to find documents. A query for 'ever tuesday in november of 2017' would have to

Re: Date Query Confusion

2018-05-17 Thread Alessandro Benedetti
Hi Terry, let me go in order : /"Tried creation_date: 2016-11. That's supposed to match documents with any November 2016 date. But actually produces: |"Invalid Date String:'2016-11'| "/ Is "*DateRangeField*" the field type for your field : "creation_date" ? [1] You mentioned :

Re: Date Query Confusion

2018-05-17 Thread Erick Erickson
Yeah, dates are "special". Those abbreviated dates are for DateRangeField, which is a distinct type from "TrieDate" in your schema. bq. And Solr doesn't seem to let me sort on a date field It's not a date field that's the problem, it's the "multiValued" part. When you specify in your schema

Date Query Confusion

2018-05-17 Thread Terry Steichen
To me, one of the more frustrating things I've encountered in Solr is working with date fields.  Supposedly, according to the documentation, this is straightforward.  But in my experience, it is anything but that.  In particular, I've found that the abbreviated forms of date queries, don't work as