Thanks!
-Original message-
> From:Shawn Heisey
> Sent: Tuesday 24th October 2017 19:04
> To: solr-user@lucene.apache.org
> Subject: Re: Date range queries no longer work 6.6 to 7.1
>
> On 10/24/2017 9:38 AM, Markus Jelsma wrote:
> > We have switched back to 6.
On 10/24/2017 9:38 AM, Markus Jelsma wrote:
> We have switched back to 6.6 for now so we are fine for now. Although i
> didn't try range queries other than date, i assume other Point fields can
> also have this problem?
>
> That would mean completely switch back to Trie if you don't can/want to f
On 10/24/2017 9:25 AM, Markus Jelsma wrote:
> No, we have not reindexed, we don't like to reindex one of our collections,
> it is huge!
>
> Didn't know about a index migration tool, i have not seen it in the changelog.
If you change the class on a field (in this case, probably Trie to
Point), th
forceMerge at least fixes nothing. I'll take a look at index
upgrade tool.
Thanks,
Markus
-Original message-
> From:Erick Erickson
> Sent: Tuesday 24th October 2017 17:30
> To: solr-user
> Subject: Re: Date range queries no longer work 6.6 to 7.1
>
> Assuming you
; From:alessandro.benedetti
>> Sent: Tuesday 24th October 2017 17:03
>> To: solr-user@lucene.apache.org
>> Subject: Re: Date range queries no longer work 6.6 to 7.1
>>
>> I know it is obvious, but ...
>> have you done a full re-indexing
17:03
> To: solr-user@lucene.apache.org
> Subject: Re: Date range queries no longer work 6.6 to 7.1
>
> I know it is obvious, but ...
> have you done a full re-indexing or you used the Index migration tool ?
> In the latter case, it could be a bug of the tool itself.
>
>
&
I know it is obvious, but ...
have you done a full re-indexing or you used the Index migration tool ?
In the latter case, it could be a bug of the tool itself.
-
---
Alessandro Benedetti
Search Consultant, R&D Software Engineer, Director
Sease Ltd. - www.sease.io
--
Sent from: h
Hello,
We just attempted an upgrade which went fine so far. But now we have a problem,
date range queries can no longer find records from before the upgrade, only
records after the upgrade, it probably has something to do with DatePointField.
To be clear, we upgraded our old date fields to the
