Solr 7.5.0, error sorting a “pdate” field in ascending 'asc' direction
by usign the Solr7.5.0 webUI, I am trying to sort a field of my schema "data_creazione", by setting:
&fl=data_creazione:[2017-11-12T00:00:00Z TO NOW]&sort=data_creazione asc
my complete query URL being:
http://localhost:8983/solr/NUR/select?fq=data_creazione:[2017-11-12T00:00:00Z%20%20TO%20%20NOW]&q=regione%20lazio&sort=data_creazione%20asc
When i inspect the results I am observing a strange and erroneous sorting behavior:
- results from 0 to 9 (start=0,rows=10) are correctly ordered (from 2018-03-01 to 2018-03-02)
- results from 10 to 19 (start=10,rows=10) are correctly ordered (from 2018-03-05 to 2018-03-07)
- results from 20 to 29 (start=20,rows=10) are incorrectly ordered (from 2018-02-23 to 2018-03-1)
Moreover, I am trying to send the same query to Solr 7.5.0 from a .netcore2.1 application by using the Solr.net driver, and I am returned the same identical sort error.
NOTICE: when I try to query the same query but in DESCENDING 'desc' direction all things go fine. All results' pages are correctly ordered.
This error does not appear with Solr 7.2.0: ascending and descending sorting over date fields works fine
In my managed-schema the field "data_creazione" is declared this way:
<fieldType name="pdate" class="solr.DatePointField" docValues="true"/>
...
<field name="data_creazione" type="pdate" multiValued="false" indexed="false" stored="true"/>
sorting date solr
asked Nov 12 '18 at 15:38
ciroBorrelli
1313
add a comment |
by usign the Solr7.5.0 webUI, I am trying to sort a field of my schema "data_creazione", by setting:
&fl=data_creazione:[2017-11-12T00:00:00Z TO NOW]&sort=data_creazione asc
my complete query URL being:
http://localhost:8983/solr/NUR/select?fq=data_creazione:[2017-11-12T00:00:00Z%20%20TO%20%20NOW]&q=regione%20lazio&sort=data_creazione%20asc
When i inspect the results I am observing a strange and erroneous sorting behavior:
- results from 0 to 9 (start=0,rows=10) are correctly ordered (from 2018-03-01 to 2018-03-02)
- results from 10 to 19 (start=10,rows=10) are correctly ordered (from 2018-03-05 to 2018-03-07)
- results from 20 to 29 (start=20,rows=10) are incorrectly ordered (from 2018-02-23 to 2018-03-1)
Moreover, I am trying to send the same query to Solr 7.5.0 from a .netcore2.1 application by using the Solr.net driver, and I am returned the same identical sort error.
NOTICE: when I try to query the same query but in DESCENDING 'desc' direction all things go fine. All results' pages are correctly ordered.
This error does not appear with Solr 7.2.0: ascending and descending sorting over date fields works fine
In my managed-schema the field "data_creazione" is declared this way:
<fieldType name="pdate" class="solr.DatePointField" docValues="true"/>
...
<field name="data_creazione" type="pdate" multiValued="false" indexed="false" stored="true"/>
sorting date solr
asked Nov 12 '18 at 15:38
ciroBorrelli
1313
Did you reindex (completely) after changing to the pdate type? Can you create a set of documents that can replicate this issue from scratch with an empty index?
– MatsLindh
Nov 12 '18 at 19:02
All documents've been indexed after managed-schema updated. Also, I can provide U the set of documents that replicates the problem. Tell me how...
– ciroBorrelli
Nov 13 '18 at 12:33
... or get'em here: link
– ciroBorrelli
Nov 13 '18 at 12:43
add a comment |
by usign the Solr7.5.0 webUI, I am trying to sort a field of my schema "data_creazione", by setting:
&fl=data_creazione:[2017-11-12T00:00:00Z TO NOW]&sort=data_creazione asc
my complete query URL being:
http://localhost:8983/solr/NUR/select?fq=data_creazione:[2017-11-12T00:00:00Z%20%20TO%20%20NOW]&q=regione%20lazio&sort=data_creazione%20asc
When i inspect the results I am observing a strange and erroneous sorting behavior:
- results from 0 to 9 (start=0,rows=10) are correctly ordered (from 2018-03-01 to 2018-03-02)
- results from 10 to 19 (start=10,rows=10) are correctly ordered (from 2018-03-05 to 2018-03-07)
- results from 20 to 29 (start=20,rows=10) are incorrectly ordered (from 2018-02-23 to 2018-03-1)
Moreover, I am trying to send the same query to Solr 7.5.0 from a .netcore2.1 application by using the Solr.net driver, and I am returned the same identical sort error.
NOTICE: when I try to query the same query but in DESCENDING 'desc' direction all things go fine. All results' pages are correctly ordered.
This error does not appear with Solr 7.2.0: ascending and descending sorting over date fields works fine
In my managed-schema the field "data_creazione" is declared this way:
<fieldType name="pdate" class="solr.DatePointField" docValues="true"/>
...
<field name="data_creazione" type="pdate" multiValued="false" indexed="false" stored="true"/>
sorting date solr
asked Nov 12 '18 at 15:38
ciroBorrelli
1313
by usign the Solr7.5.0 webUI, I am trying to sort a field of my schema "data_creazione", by setting:
&fl=data_creazione:[2017-11-12T00:00:00Z TO NOW]&sort=data_creazione asc
my complete query URL being:
http://localhost:8983/solr/NUR/select?fq=data_creazione:[2017-11-12T00:00:00Z%20%20TO%20%20NOW]&q=regione%20lazio&sort=data_creazione%20asc
When i inspect the results I am observing a strange and erroneous sorting behavior:
- results from 0 to 9 (start=0,rows=10) are correctly ordered (from 2018-03-01 to 2018-03-02)
- results from 10 to 19 (start=10,rows=10) are correctly ordered (from 2018-03-05 to 2018-03-07)
- results from 20 to 29 (start=20,rows=10) are incorrectly ordered (from 2018-02-23 to 2018-03-1)
Moreover, I am trying to send the same query to Solr 7.5.0 from a .netcore2.1 application by using the Solr.net driver, and I am returned the same identical sort error.
NOTICE: when I try to query the same query but in DESCENDING 'desc' direction all things go fine. All results' pages are correctly ordered.
This error does not appear with Solr 7.2.0: ascending and descending sorting over date fields works fine
In my managed-schema the field "data_creazione" is declared this way:
<fieldType name="pdate" class="solr.DatePointField" docValues="true"/>
...
<field name="data_creazione" type="pdate" multiValued="false" indexed="false" stored="true"/>
sorting date solr
sorting date solr
asked Nov 12 '18 at 15:38
ciroBorrelli
1313
asked Nov 12 '18 at 15:38
ciroBorrelli
1313
asked Nov 12 '18 at 15:38
ciroBorrelli
1313
asked Nov 12 '18 at 15:38
ciroBorrelli
1313
asked Nov 12 '18 at 15:38
ciroBorrelli
1313
1313
Did you reindex (completely) after changing to the pdate type? Can you create a set of documents that can replicate this issue from scratch with an empty index?
– MatsLindh
Nov 12 '18 at 19:02
All documents've been indexed after managed-schema updated. Also, I can provide U the set of documents that replicates the problem. Tell me how...
– ciroBorrelli
Nov 13 '18 at 12:33
... or get'em here: link
– ciroBorrelli
Nov 13 '18 at 12:43
add a comment |
Did you reindex (completely) after changing to the pdate type? Can you create a set of documents that can replicate this issue from scratch with an empty index?
– MatsLindh
Nov 12 '18 at 19:02
All documents've been indexed after managed-schema updated. Also, I can provide U the set of documents that replicates the problem. Tell me how...
– ciroBorrelli
Nov 13 '18 at 12:33
... or get'em here: link
– ciroBorrelli
Nov 13 '18 at 12:43
Did you reindex (completely) after changing to the pdate type? Can you create a set of documents that can replicate this issue from scratch with an empty index?
– MatsLindh
Nov 12 '18 at 19:02
Did you reindex (completely) after changing to the pdate type? Can you create a set of documents that can replicate this issue from scratch with an empty index?
– MatsLindh
Nov 12 '18 at 19:02
All documents've been indexed after managed-schema updated. Also, I can provide U the set of documents that replicates the problem. Tell me how...
– ciroBorrelli
Nov 13 '18 at 12:33
All documents've been indexed after managed-schema updated. Also, I can provide U the set of documents that replicates the problem. Tell me how...
– ciroBorrelli
Nov 13 '18 at 12:33
... or get'em here: link
– ciroBorrelli
Nov 13 '18 at 12:43
... or get'em here: link
– ciroBorrelli
Nov 13 '18 at 12:43
add a comment |
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53265447%2fsolr-7-5-0-error-sorting-a-pdate-field-in-ascending-asc-direction%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53265447%2fsolr-7-5-0-error-sorting-a-pdate-field-in-ascending-asc-direction%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Did you reindex (completely) after changing to the pdate type? Can you create a set of documents that can replicate this issue from scratch with an empty index?
– MatsLindh
Nov 12 '18 at 19:02
All documents've been indexed after managed-schema updated. Also, I can provide U the set of documents that replicates the problem. Tell me how...
– ciroBorrelli
Nov 13 '18 at 12:33
... or get'em here: link
– ciroBorrelli
Nov 13 '18 at 12:43