Elastic search filter for distinct categories
I made a simple mapping with three fields and i am analyzing one field which is text type and other fields are keyword type.
example
fields: Category_one, Category_two, Category_three.
Now i am searching the documents.
Get _search/cat
{
"size": 4,
"query": {
"match": {
"Category_one.ngrams": {
"query": "Nice food place in XYZ location",
"analyzer": "standard"
}
},
"aggs":{
"distincr_values":{
"terms": {
"fields" : "Category_two"
}
}
}
}
}
It's showing this error
{
"error": {
"root_cause": [
{
"type": "parsing_exception",
"reason": "[match] malformed query, expected [END_OBJECT] but found [FIELD_NAME]",
"line": 10,
"col": 5
}
],
"type": "parsing_exception",
"reason": "[match] malformed query, expected [END_OBJECT] but found [FIELD_NAME]",
"line": 10,
"col": 5
},
"status": 400
}
Kindly help me with this error. My main motive is to find distinct searches according Category_two field.
Any help would be appreciated.
json
elasticsearch elasticsearch-5 asked Nov 14 '18 at 1:16
lohitaksh yogi
265
add a comment |
I made a simple mapping with three fields and i am analyzing one field which is text type and other fields are keyword type.
example
fields: Category_one, Category_two, Category_three.
Now i am searching the documents.
Get _search/cat
{
"size": 4,
"query": {
"match": {
"Category_one.ngrams": {
"query": "Nice food place in XYZ location",
"analyzer": "standard"
}
},
"aggs":{
"distincr_values":{
"terms": {
"fields" : "Category_two"
}
}
}
}
}
It's showing this error
{
"error": {
"root_cause": [
{
"type": "parsing_exception",
"reason": "[match] malformed query, expected [END_OBJECT] but found [FIELD_NAME]",
"line": 10,
"col": 5
}
],
"type": "parsing_exception",
"reason": "[match] malformed query, expected [END_OBJECT] but found [FIELD_NAME]",
"line": 10,
"col": 5
},
"status": 400
}
Kindly help me with this error. My main motive is to find distinct searches according Category_two field.
Any help would be appreciated.
json
elasticsearch elasticsearch-5 asked Nov 14 '18 at 1:16
lohitaksh yogi
265
add a comment |
I made a simple mapping with three fields and i am analyzing one field which is text type and other fields are keyword type.
example
fields: Category_one, Category_two, Category_three.
Now i am searching the documents.
Get _search/cat
{
"size": 4,
"query": {
"match": {
"Category_one.ngrams": {
"query": "Nice food place in XYZ location",
"analyzer": "standard"
}
},
"aggs":{
"distincr_values":{
"terms": {
"fields" : "Category_two"
}
}
}
}
}
It's showing this error
{
"error": {
"root_cause": [
{
"type": "parsing_exception",
"reason": "[match] malformed query, expected [END_OBJECT] but found [FIELD_NAME]",
"line": 10,
"col": 5
}
],
"type": "parsing_exception",
"reason": "[match] malformed query, expected [END_OBJECT] but found [FIELD_NAME]",
"line": 10,
"col": 5
},
"status": 400
}
Kindly help me with this error. My main motive is to find distinct searches according Category_two field.
Any help would be appreciated.
json
elasticsearch elasticsearch-5 asked Nov 14 '18 at 1:16
lohitaksh yogi
265
I made a simple mapping with three fields and i am analyzing one field which is text type and other fields are keyword type.
example
fields: Category_one, Category_two, Category_three.
Now i am searching the documents.
Get _search/cat
{
"size": 4,
"query": {
"match": {
"Category_one.ngrams": {
"query": "Nice food place in XYZ location",
"analyzer": "standard"
}
},
"aggs":{
"distincr_values":{
"terms": {
"fields" : "Category_two"
}
}
}
}
}
It's showing this error
{
"error": {
"root_cause": [
{
"type": "parsing_exception",
"reason": "[match] malformed query, expected [END_OBJECT] but found [FIELD_NAME]",
"line": 10,
"col": 5
}
],
"type": "parsing_exception",
"reason": "[match] malformed query, expected [END_OBJECT] but found [FIELD_NAME]",
"line": 10,
"col": 5
},
"status": 400
}
Kindly help me with this error. My main motive is to find distinct searches according Category_two field.
Any help would be appreciated.
json
elasticsearch elasticsearch-5 json
elasticsearch elasticsearch-5 asked Nov 14 '18 at 1:16
lohitaksh yogi
265
asked Nov 14 '18 at 1:16
lohitaksh yogi
265
asked Nov 14 '18 at 1:16
lohitaksh yogi
265
asked Nov 14 '18 at 1:16
lohitaksh yogi
265
asked Nov 14 '18 at 1:16
lohitaksh yogi
265
265
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I believe youre getting this error because of your query structure.
Your aggregations keyword must be outside (same level as) the query. At the moments your aggs is wrapped up inside the query.
Following this structure:
Get _search/cat
{
"size": 4,
"query": {
'query goes here'
},
"aggs":{
'aggregation go here'
}
}
answered Nov 14 '18 at 7:23
Neil Varnas
367417
I changed as you mention now it's showing a different error. "root_cause": [ { "type": "illegal_argument_exception", "reason": "[terms] unknown field [fields], parser not found"
– lohitaksh yogi
Nov 14 '18 at 17:06
Post the full query you’re trying to execute. But judging by the error looks like you are requesting Terms agh on a field that doesn’t exist.
– Neil Varnas
Nov 14 '18 at 19:11
@lohitakshyogi if you have solved your problem and my answer above helped you solve the problem, please at least up-vote.
– Neil Varnas
Nov 18 '18 at 13:03
add a comment |
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%2f53291807%2felastic-search-filter-for-distinct-categories%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I believe youre getting this error because of your query structure.
Your aggregations keyword must be outside (same level as) the query. At the moments your aggs is wrapped up inside the query.
Following this structure:
Get _search/cat
{
"size": 4,
"query": {
'query goes here'
},
"aggs":{
'aggregation go here'
}
}
answered Nov 14 '18 at 7:23
Neil Varnas
367417
I changed as you mention now it's showing a different error. "root_cause": [ { "type": "illegal_argument_exception", "reason": "[terms] unknown field [fields], parser not found"
– lohitaksh yogi
Nov 14 '18 at 17:06
Post the full query you’re trying to execute. But judging by the error looks like you are requesting Terms agh on a field that doesn’t exist.
– Neil Varnas
Nov 14 '18 at 19:11
@lohitakshyogi if you have solved your problem and my answer above helped you solve the problem, please at least up-vote.
– Neil Varnas
Nov 18 '18 at 13:03
add a comment |
I believe youre getting this error because of your query structure.
Your aggregations keyword must be outside (same level as) the query. At the moments your aggs is wrapped up inside the query.
Following this structure:
Get _search/cat
{
"size": 4,
"query": {
'query goes here'
},
"aggs":{
'aggregation go here'
}
}
answered Nov 14 '18 at 7:23
Neil Varnas
367417
I changed as you mention now it's showing a different error. "root_cause": [ { "type": "illegal_argument_exception", "reason": "[terms] unknown field [fields], parser not found"
– lohitaksh yogi
Nov 14 '18 at 17:06
Post the full query you’re trying to execute. But judging by the error looks like you are requesting Terms agh on a field that doesn’t exist.
– Neil Varnas
Nov 14 '18 at 19:11
@lohitakshyogi if you have solved your problem and my answer above helped you solve the problem, please at least up-vote.
– Neil Varnas
Nov 18 '18 at 13:03
add a comment |
I believe youre getting this error because of your query structure.
Your aggregations keyword must be outside (same level as) the query. At the moments your aggs is wrapped up inside the query.
Following this structure:
Get _search/cat
{
"size": 4,
"query": {
'query goes here'
},
"aggs":{
'aggregation go here'
}
}
answered Nov 14 '18 at 7:23
Neil Varnas
367417
I believe youre getting this error because of your query structure.
Your aggregations keyword must be outside (same level as) the query. At the moments your aggs is wrapped up inside the query.
Following this structure:
Get _search/cat
{
"size": 4,
"query": {
'query goes here'
},
"aggs":{
'aggregation go here'
}
}
answered Nov 14 '18 at 7:23
Neil Varnas
367417
answered Nov 14 '18 at 7:23
Neil Varnas
367417
answered Nov 14 '18 at 7:23
Neil Varnas
367417
answered Nov 14 '18 at 7:23
Neil Varnas
367417
367417
I changed as you mention now it's showing a different error. "root_cause": [ { "type": "illegal_argument_exception", "reason": "[terms] unknown field [fields], parser not found"
– lohitaksh yogi
Nov 14 '18 at 17:06
Post the full query you’re trying to execute. But judging by the error looks like you are requesting Terms agh on a field that doesn’t exist.
– Neil Varnas
Nov 14 '18 at 19:11
@lohitakshyogi if you have solved your problem and my answer above helped you solve the problem, please at least up-vote.
– Neil Varnas
Nov 18 '18 at 13:03
add a comment |
I changed as you mention now it's showing a different error. "root_cause": [ { "type": "illegal_argument_exception", "reason": "[terms] unknown field [fields], parser not found"
– lohitaksh yogi
Nov 14 '18 at 17:06
Post the full query you’re trying to execute. But judging by the error looks like you are requesting Terms agh on a field that doesn’t exist.
– Neil Varnas
Nov 14 '18 at 19:11
@lohitakshyogi if you have solved your problem and my answer above helped you solve the problem, please at least up-vote.
– Neil Varnas
Nov 18 '18 at 13:03
I changed as you mention now it's showing a different error. "root_cause": [ { "type": "illegal_argument_exception", "reason": "[terms] unknown field [fields], parser not found"
– lohitaksh yogi
Nov 14 '18 at 17:06
I changed as you mention now it's showing a different error. "root_cause": [ { "type": "illegal_argument_exception", "reason": "[terms] unknown field [fields], parser not found"
– lohitaksh yogi
Nov 14 '18 at 17:06
Post the full query you’re trying to execute. But judging by the error looks like you are requesting Terms agh on a field that doesn’t exist.
– Neil Varnas
Nov 14 '18 at 19:11
Post the full query you’re trying to execute. But judging by the error looks like you are requesting Terms agh on a field that doesn’t exist.
– Neil Varnas
Nov 14 '18 at 19:11
@lohitakshyogi if you have solved your problem and my answer above helped you solve the problem, please at least up-vote.
– Neil Varnas
Nov 18 '18 at 13:03
@lohitakshyogi if you have solved your problem and my answer above helped you solve the problem, please at least up-vote.
– Neil Varnas
Nov 18 '18 at 13:03
add a comment |
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%2f53291807%2felastic-search-filter-for-distinct-categories%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
