ElasticSearch natural sort on a single complex field
This is for ElasticSearch 6.4.1.
The client is an archive and the records have a "RefNo" (reference number) field which is how they mostly identify the records. It's not a simple field, though, but a slash-delimited field that represents a hierarchy of records where each identifying section can be a mixture of numbers and letters, so that for instance "abc" represents one collection and "a142" another: "abc/foo", "abc/bar", "a142/1/letters", "a142/2/letters", "a142/10/letters" are all various items at different levels. They look pretty abstract to me but to the archivists they're actually meaningful.
I guess you can anticipate the problem. I want to be able to order on this field (actually a keyword version of it called RefNo.keyword) in a way which gives the obvious, natural order:
a15
a142
abc
abc/bar
abc/bar/1
abc/bar/2
abc/bar/10/letters
abc/bar/10/letters/1
abc/bar/10/letters/2
abc/foobar/
and so on. The trick is in getting the numerical sections to order in natural numerical order rather than alphabetically, whereas the rest of it is alphabetical.
In another context I have a list of the child records of a single record, and in that case the solution was to order first on the length of the field and then numerically:
"sort:[
"_script":{
"script":"doc['RefNo.keyword'].value.length()",
"type":"number",
"order":asc"
},
"RefNo.keyword":{
"order":"asc"
}
]
But of course that only works if the values are all identical apart from the last section.
For the general case, I have a feeling there is something very simple that I'm missing. Is that just wishful thinking?
Thanks,
Ben
sorting
elasticsearch elasticsearch-6 asked Nov 23 '18 at 11:23
Spunto the Rat Boy
34
add a comment |
This is for ElasticSearch 6.4.1.
The client is an archive and the records have a "RefNo" (reference number) field which is how they mostly identify the records. It's not a simple field, though, but a slash-delimited field that represents a hierarchy of records where each identifying section can be a mixture of numbers and letters, so that for instance "abc" represents one collection and "a142" another: "abc/foo", "abc/bar", "a142/1/letters", "a142/2/letters", "a142/10/letters" are all various items at different levels. They look pretty abstract to me but to the archivists they're actually meaningful.
I guess you can anticipate the problem. I want to be able to order on this field (actually a keyword version of it called RefNo.keyword) in a way which gives the obvious, natural order:
a15
a142
abc
abc/bar
abc/bar/1
abc/bar/2
abc/bar/10/letters
abc/bar/10/letters/1
abc/bar/10/letters/2
abc/foobar/
and so on. The trick is in getting the numerical sections to order in natural numerical order rather than alphabetically, whereas the rest of it is alphabetical.
In another context I have a list of the child records of a single record, and in that case the solution was to order first on the length of the field and then numerically:
"sort:[
"_script":{
"script":"doc['RefNo.keyword'].value.length()",
"type":"number",
"order":asc"
},
"RefNo.keyword":{
"order":"asc"
}
]
But of course that only works if the values are all identical apart from the last section.
For the general case, I have a feeling there is something very simple that I'm missing. Is that just wishful thinking?
Thanks,
Ben
sorting
elasticsearch elasticsearch-6 asked Nov 23 '18 at 11:23
Spunto the Rat Boy
34
add a comment |
This is for ElasticSearch 6.4.1.
The client is an archive and the records have a "RefNo" (reference number) field which is how they mostly identify the records. It's not a simple field, though, but a slash-delimited field that represents a hierarchy of records where each identifying section can be a mixture of numbers and letters, so that for instance "abc" represents one collection and "a142" another: "abc/foo", "abc/bar", "a142/1/letters", "a142/2/letters", "a142/10/letters" are all various items at different levels. They look pretty abstract to me but to the archivists they're actually meaningful.
I guess you can anticipate the problem. I want to be able to order on this field (actually a keyword version of it called RefNo.keyword) in a way which gives the obvious, natural order:
a15
a142
abc
abc/bar
abc/bar/1
abc/bar/2
abc/bar/10/letters
abc/bar/10/letters/1
abc/bar/10/letters/2
abc/foobar/
and so on. The trick is in getting the numerical sections to order in natural numerical order rather than alphabetically, whereas the rest of it is alphabetical.
In another context I have a list of the child records of a single record, and in that case the solution was to order first on the length of the field and then numerically:
"sort:[
"_script":{
"script":"doc['RefNo.keyword'].value.length()",
"type":"number",
"order":asc"
},
"RefNo.keyword":{
"order":"asc"
}
]
But of course that only works if the values are all identical apart from the last section.
For the general case, I have a feeling there is something very simple that I'm missing. Is that just wishful thinking?
Thanks,
Ben
sorting
elasticsearch elasticsearch-6 asked Nov 23 '18 at 11:23
Spunto the Rat Boy
34
This is for ElasticSearch 6.4.1.
The client is an archive and the records have a "RefNo" (reference number) field which is how they mostly identify the records. It's not a simple field, though, but a slash-delimited field that represents a hierarchy of records where each identifying section can be a mixture of numbers and letters, so that for instance "abc" represents one collection and "a142" another: "abc/foo", "abc/bar", "a142/1/letters", "a142/2/letters", "a142/10/letters" are all various items at different levels. They look pretty abstract to me but to the archivists they're actually meaningful.
I guess you can anticipate the problem. I want to be able to order on this field (actually a keyword version of it called RefNo.keyword) in a way which gives the obvious, natural order:
a15
a142
abc
abc/bar
abc/bar/1
abc/bar/2
abc/bar/10/letters
abc/bar/10/letters/1
abc/bar/10/letters/2
abc/foobar/
and so on. The trick is in getting the numerical sections to order in natural numerical order rather than alphabetically, whereas the rest of it is alphabetical.
In another context I have a list of the child records of a single record, and in that case the solution was to order first on the length of the field and then numerically:
"sort:[
"_script":{
"script":"doc['RefNo.keyword'].value.length()",
"type":"number",
"order":asc"
},
"RefNo.keyword":{
"order":"asc"
}
]
But of course that only works if the values are all identical apart from the last section.
For the general case, I have a feeling there is something very simple that I'm missing. Is that just wishful thinking?
Thanks,
Ben
sorting
elasticsearch elasticsearch-6 sorting
elasticsearch elasticsearch-6 asked Nov 23 '18 at 11:23
Spunto the Rat Boy
34
asked Nov 23 '18 at 11:23
Spunto the Rat Boy
34
asked Nov 23 '18 at 11:23
Spunto the Rat Boy
34
asked Nov 23 '18 at 11:23
Spunto the Rat Boy
34
asked Nov 23 '18 at 11:23
Spunto the Rat Boy
34
34
add a comment |
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%2f53445794%2felasticsearch-natural-sort-on-a-single-complex-field%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%2f53445794%2felasticsearch-natural-sort-on-a-single-complex-field%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
