Distribute missing across multiple values
Elasticsearch has this missing
property that assign buckets with missing value some some other value.
I'm just wondering if there is a way to distribute the bucket across many buckets or even still just distribute them to the already existing buckets.
Use case:
Take documents that need to index location fields.
...
"locations": [
"city" : "LA",
"suburb": "Beverly Hills"
,
"city" : "LA",
"suburb": "Hollywood"
]
Some documents need to index to one suburb and can go till suburb level while others span multiple suburbs. Instead of indexing documents to all suburbs, just index the document till city level and all suburbs missing suburb span the whole city (i.e. all suburbs in city)
...
"locations": [
"city" : "LA"
]
Including the document is search results is not much of a problem, problem now is to count those documents for all suburbs. So in essence if LA has 2 suburbs and the above is our only document, we end up with the following buckets for suburb aggregation.
"buckets" : [
"key" : "Beverly Hills",
"doc_count" : 1
,
"key" : "Hollywood",
"doc_count" : 1
]
elasticsearch elasticsearch-net
add a comment |
Elasticsearch has this missing
property that assign buckets with missing value some some other value.
I'm just wondering if there is a way to distribute the bucket across many buckets or even still just distribute them to the already existing buckets.
Use case:
Take documents that need to index location fields.
...
"locations": [
"city" : "LA",
"suburb": "Beverly Hills"
,
"city" : "LA",
"suburb": "Hollywood"
]
Some documents need to index to one suburb and can go till suburb level while others span multiple suburbs. Instead of indexing documents to all suburbs, just index the document till city level and all suburbs missing suburb span the whole city (i.e. all suburbs in city)
...
"locations": [
"city" : "LA"
]
Including the document is search results is not much of a problem, problem now is to count those documents for all suburbs. So in essence if LA has 2 suburbs and the above is our only document, we end up with the following buckets for suburb aggregation.
"buckets" : [
"key" : "Beverly Hills",
"doc_count" : 1
,
"key" : "Hollywood",
"doc_count" : 1
]
elasticsearch elasticsearch-net
add a comment |
Elasticsearch has this missing
property that assign buckets with missing value some some other value.
I'm just wondering if there is a way to distribute the bucket across many buckets or even still just distribute them to the already existing buckets.
Use case:
Take documents that need to index location fields.
...
"locations": [
"city" : "LA",
"suburb": "Beverly Hills"
,
"city" : "LA",
"suburb": "Hollywood"
]
Some documents need to index to one suburb and can go till suburb level while others span multiple suburbs. Instead of indexing documents to all suburbs, just index the document till city level and all suburbs missing suburb span the whole city (i.e. all suburbs in city)
...
"locations": [
"city" : "LA"
]
Including the document is search results is not much of a problem, problem now is to count those documents for all suburbs. So in essence if LA has 2 suburbs and the above is our only document, we end up with the following buckets for suburb aggregation.
"buckets" : [
"key" : "Beverly Hills",
"doc_count" : 1
,
"key" : "Hollywood",
"doc_count" : 1
]
elasticsearch elasticsearch-net
Elasticsearch has this missing
property that assign buckets with missing value some some other value.
I'm just wondering if there is a way to distribute the bucket across many buckets or even still just distribute them to the already existing buckets.
Use case:
Take documents that need to index location fields.
...
"locations": [
"city" : "LA",
"suburb": "Beverly Hills"
,
"city" : "LA",
"suburb": "Hollywood"
]
Some documents need to index to one suburb and can go till suburb level while others span multiple suburbs. Instead of indexing documents to all suburbs, just index the document till city level and all suburbs missing suburb span the whole city (i.e. all suburbs in city)
...
"locations": [
"city" : "LA"
]
Including the document is search results is not much of a problem, problem now is to count those documents for all suburbs. So in essence if LA has 2 suburbs and the above is our only document, we end up with the following buckets for suburb aggregation.
"buckets" : [
"key" : "Beverly Hills",
"doc_count" : 1
,
"key" : "Hollywood",
"doc_count" : 1
]
elasticsearch elasticsearch-net
elasticsearch elasticsearch-net
asked Nov 12 '18 at 13:47
legen---wait for it---darylegen---wait for it---dary
4911818
4911818
add a comment |
add a comment |
0
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%2f53263543%2fdistribute-missing-across-multiple-values%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
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.
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%2f53263543%2fdistribute-missing-across-multiple-values%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