> You could do it that way ... but instead, I'd create a new fieldType,
> not change an existing one. The existing name is "pdate" which implies
> "point date". I would probably go with "daterange" or "rdate" as the
> name, but that is completely up to you.
>
>
I did that, deleted docs, stopped,
On 11/13/2019 10:45 AM, rhys J wrote:
If you use DateRangeField instead of DatePointField for your field's
class, then you can indeed use partial timestamps for both indexing and
querying. This only works with DateRangeField.
I don't see that as an option in the API? Do I need to change what
> If you use DateRangeField instead of DatePointField for your field's
> class, then you can indeed use partial timestamps for both indexing and
> querying. This only works with DateRangeField.
>
>
I don't see that as an option in the API? Do I need to change what pdate's
type is in the managed-sc
On 11/13/2019 10:07 AM, rhys J wrote:
I have date fields in my documents that are just -MM-DD.
and
When I use the API to do a search and try:
2018-01-01
[2018-01-01 TO NOW]
I get 'Invalid Date String'.
Did I type my data wrong in the schema? Is there something I'm missing from
the fie
