breaking field value on hypen












0















I have following sample docs in Elasticsearch



[
{
"_index": "beatbox-2018.11.19",
"_source": {
"connection": "10",
"user": "op-dashboard",
"key": "monolith_connection_sniffer"
}
},
{
"_index": "beatbox-2018.11.19",
"_source": {
"connection": "10",
"user": "op-dashboard",
"key": "monolith_connection_sniffer"
}
}
]


When I query on user, I got expected result.



curl -X GET 
'http://127.0.0.1:9200/beatbox-2018.11.19/_search?q=user:op-dashboard'


In Grafana:



I was trying to add some query with Variable for user field.



{   "find": "terms",   "field": "user" }


But I got tokenised values of user field.



`op`, `dashboard`


In background, following payload is sending for query



{
"size": 0,
"query": {
"bool": {
"filter": [
{
"query_string": {
"analyze_wildcard": true,
"query": "*"
}
}
]
}
},
"aggs": {
"1": {
"terms": {
"field": "user",
"size": 500,
"order": {
"_term": "asc"
}
}
}
}
}


Query returns tokenised result. How can I stop it?



I have already tried with following template



{
"index_patterns": [
"beatbox*"
],
"mappings": {
"doc":
"properties": {
"user": {
"type": "text",
"fielddata": true,
"analyzer":"whitespace",
"search_analyzer": "whitespace"
}
}
}
}
}


And also with analyzer



{
"index": {
"analysis": {
"default": {
"analyzer": {
"analyzer_keyword": {
"tokenizer": "whitespace"
}
}
}
}
}
}


Mapping for index:



{
"beatbox-2018.11.19":{
"mappings":{
"doc":{
"_all":{
"enabled":false
},
"numeric_detection":true,
"properties":{
"connection":{
"type":"long"
},
"key":{
"type":"text",
"norms":false,
"index_options":"freqs"
},
"user":{
"type":"text",
"fielddata":true
}
}
}
}
}
}


Any help?










share|improve this question





























    0















    I have following sample docs in Elasticsearch



    [
    {
    "_index": "beatbox-2018.11.19",
    "_source": {
    "connection": "10",
    "user": "op-dashboard",
    "key": "monolith_connection_sniffer"
    }
    },
    {
    "_index": "beatbox-2018.11.19",
    "_source": {
    "connection": "10",
    "user": "op-dashboard",
    "key": "monolith_connection_sniffer"
    }
    }
    ]


    When I query on user, I got expected result.



    curl -X GET 
    'http://127.0.0.1:9200/beatbox-2018.11.19/_search?q=user:op-dashboard'


    In Grafana:



    I was trying to add some query with Variable for user field.



    {   "find": "terms",   "field": "user" }


    But I got tokenised values of user field.



    `op`, `dashboard`


    In background, following payload is sending for query



    {
    "size": 0,
    "query": {
    "bool": {
    "filter": [
    {
    "query_string": {
    "analyze_wildcard": true,
    "query": "*"
    }
    }
    ]
    }
    },
    "aggs": {
    "1": {
    "terms": {
    "field": "user",
    "size": 500,
    "order": {
    "_term": "asc"
    }
    }
    }
    }
    }


    Query returns tokenised result. How can I stop it?



    I have already tried with following template



    {
    "index_patterns": [
    "beatbox*"
    ],
    "mappings": {
    "doc":
    "properties": {
    "user": {
    "type": "text",
    "fielddata": true,
    "analyzer":"whitespace",
    "search_analyzer": "whitespace"
    }
    }
    }
    }
    }


    And also with analyzer



    {
    "index": {
    "analysis": {
    "default": {
    "analyzer": {
    "analyzer_keyword": {
    "tokenizer": "whitespace"
    }
    }
    }
    }
    }
    }


    Mapping for index:



    {
    "beatbox-2018.11.19":{
    "mappings":{
    "doc":{
    "_all":{
    "enabled":false
    },
    "numeric_detection":true,
    "properties":{
    "connection":{
    "type":"long"
    },
    "key":{
    "type":"text",
    "norms":false,
    "index_options":"freqs"
    },
    "user":{
    "type":"text",
    "fielddata":true
    }
    }
    }
    }
    }
    }


    Any help?










    share|improve this question



























      0












      0








      0








      I have following sample docs in Elasticsearch



      [
      {
      "_index": "beatbox-2018.11.19",
      "_source": {
      "connection": "10",
      "user": "op-dashboard",
      "key": "monolith_connection_sniffer"
      }
      },
      {
      "_index": "beatbox-2018.11.19",
      "_source": {
      "connection": "10",
      "user": "op-dashboard",
      "key": "monolith_connection_sniffer"
      }
      }
      ]


      When I query on user, I got expected result.



      curl -X GET 
      'http://127.0.0.1:9200/beatbox-2018.11.19/_search?q=user:op-dashboard'


      In Grafana:



      I was trying to add some query with Variable for user field.



      {   "find": "terms",   "field": "user" }


      But I got tokenised values of user field.



      `op`, `dashboard`


      In background, following payload is sending for query



      {
      "size": 0,
      "query": {
      "bool": {
      "filter": [
      {
      "query_string": {
      "analyze_wildcard": true,
      "query": "*"
      }
      }
      ]
      }
      },
      "aggs": {
      "1": {
      "terms": {
      "field": "user",
      "size": 500,
      "order": {
      "_term": "asc"
      }
      }
      }
      }
      }


      Query returns tokenised result. How can I stop it?



      I have already tried with following template



      {
      "index_patterns": [
      "beatbox*"
      ],
      "mappings": {
      "doc":
      "properties": {
      "user": {
      "type": "text",
      "fielddata": true,
      "analyzer":"whitespace",
      "search_analyzer": "whitespace"
      }
      }
      }
      }
      }


      And also with analyzer



      {
      "index": {
      "analysis": {
      "default": {
      "analyzer": {
      "analyzer_keyword": {
      "tokenizer": "whitespace"
      }
      }
      }
      }
      }
      }


      Mapping for index:



      {
      "beatbox-2018.11.19":{
      "mappings":{
      "doc":{
      "_all":{
      "enabled":false
      },
      "numeric_detection":true,
      "properties":{
      "connection":{
      "type":"long"
      },
      "key":{
      "type":"text",
      "norms":false,
      "index_options":"freqs"
      },
      "user":{
      "type":"text",
      "fielddata":true
      }
      }
      }
      }
      }
      }


      Any help?










      share|improve this question
















      I have following sample docs in Elasticsearch



      [
      {
      "_index": "beatbox-2018.11.19",
      "_source": {
      "connection": "10",
      "user": "op-dashboard",
      "key": "monolith_connection_sniffer"
      }
      },
      {
      "_index": "beatbox-2018.11.19",
      "_source": {
      "connection": "10",
      "user": "op-dashboard",
      "key": "monolith_connection_sniffer"
      }
      }
      ]


      When I query on user, I got expected result.



      curl -X GET 
      'http://127.0.0.1:9200/beatbox-2018.11.19/_search?q=user:op-dashboard'


      In Grafana:



      I was trying to add some query with Variable for user field.



      {   "find": "terms",   "field": "user" }


      But I got tokenised values of user field.



      `op`, `dashboard`


      In background, following payload is sending for query



      {
      "size": 0,
      "query": {
      "bool": {
      "filter": [
      {
      "query_string": {
      "analyze_wildcard": true,
      "query": "*"
      }
      }
      ]
      }
      },
      "aggs": {
      "1": {
      "terms": {
      "field": "user",
      "size": 500,
      "order": {
      "_term": "asc"
      }
      }
      }
      }
      }


      Query returns tokenised result. How can I stop it?



      I have already tried with following template



      {
      "index_patterns": [
      "beatbox*"
      ],
      "mappings": {
      "doc":
      "properties": {
      "user": {
      "type": "text",
      "fielddata": true,
      "analyzer":"whitespace",
      "search_analyzer": "whitespace"
      }
      }
      }
      }
      }


      And also with analyzer



      {
      "index": {
      "analysis": {
      "default": {
      "analyzer": {
      "analyzer_keyword": {
      "tokenizer": "whitespace"
      }
      }
      }
      }
      }
      }


      Mapping for index:



      {
      "beatbox-2018.11.19":{
      "mappings":{
      "doc":{
      "_all":{
      "enabled":false
      },
      "numeric_detection":true,
      "properties":{
      "connection":{
      "type":"long"
      },
      "key":{
      "type":"text",
      "norms":false,
      "index_options":"freqs"
      },
      "user":{
      "type":"text",
      "fielddata":true
      }
      }
      }
      }
      }
      }


      Any help?







      elasticsearch grafana elasticsearch-6 grafana-variable






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 19 '18 at 9:28







      aerokite

















      asked Nov 19 '18 at 6:47









      aerokiteaerokite

      6,35643466




      6,35643466
























          1 Answer
          1






          active

          oldest

          votes


















          1














          You should you Keyword Datatype of elasticsearch instead of text datatype in user fields as you are aggregating it.






          share|improve this answer
























          • Thank you. It works

            – aerokite
            Nov 19 '18 at 10:46











          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
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53369593%2fbreaking-field-value-on-hypen%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









          1














          You should you Keyword Datatype of elasticsearch instead of text datatype in user fields as you are aggregating it.






          share|improve this answer
























          • Thank you. It works

            – aerokite
            Nov 19 '18 at 10:46
















          1














          You should you Keyword Datatype of elasticsearch instead of text datatype in user fields as you are aggregating it.






          share|improve this answer
























          • Thank you. It works

            – aerokite
            Nov 19 '18 at 10:46














          1












          1








          1







          You should you Keyword Datatype of elasticsearch instead of text datatype in user fields as you are aggregating it.






          share|improve this answer













          You should you Keyword Datatype of elasticsearch instead of text datatype in user fields as you are aggregating it.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 19 '18 at 9:49









          safwansafwan

          712




          712













          • Thank you. It works

            – aerokite
            Nov 19 '18 at 10:46



















          • Thank you. It works

            – aerokite
            Nov 19 '18 at 10:46

















          Thank you. It works

          – aerokite
          Nov 19 '18 at 10:46





          Thank you. It works

          – aerokite
          Nov 19 '18 at 10:46


















          draft saved

          draft discarded




















































          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.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53369593%2fbreaking-field-value-on-hypen%23new-answer', 'question_page');
          }
          );

          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







          Popular posts from this blog

          How to pass form data using jquery Ajax to insert data in database?

          National Museum of Racing and Hall of Fame

          Guess what letter conforming each word