Please read the error message:

'reason' => 'failed to parse','type' => 'mapper_parsing_exception','ca
+used_by' => {'reason' => 'Mixing up field types: class org.elasticsea
+rch.index.mapper.core.StringFieldMapper$StringFieldType != class org.
+elasticsearch.index.mapper.internal.IndexFieldMapper$IndexFieldType o
+n field _index','type' => 'illegal_state_exception'}}}

[download]

What you submit does not match what Elasticsearch expects for the string field. So you should lean what Elasticsearch expects and then submit the appropriate data types.

You don't need to convert the Perl data structure to JSON yourself. The Search::Elasticsearch wrappers handle that for you.

In reply to Re^3: Return value of Search::Elasticsearch search query by Corion
in thread Return value of Search::Elasticsearch search query by ravi45722

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.