https://answers.axonivy.com/questions/3903/elasticsearch-fail-because-auto-conversion-changes-string-values-into-date<p>We get an error of the Elasticsearch by saving a BusinessObject over the ivy.repo with a field of type <code>Map&lt; String,String &gt;</code>.</p> <pre><code>Elasticsearch update index of document failed because of: {"root_cause":[{"type":"illegal_argument_exception","reason":"mapper [details.data.Value1] of different type, current_type [text], merged_type [date]"}],"type":"illegal_argument_exception","reason":"mapper [details.data.Value1] of different type, current_type [text], merged_type [date]"}</code></pre> <p>The problem ist clear. The field "details.data.Value1" is a date field and i try to store a String.</p> <p><strong>But</strong> the definition of our BusinessObject is different to that!<br> The field "data" of the "detail" object is defined as a <code>Map&lt; String,String &gt;</code>.<br> We get this error when we run the following code in an IvyScript (we used a helper class for Maps, because IvyScript is not able to handle double generics).</p> <pre><code>JobDetail detail = new JobDetail(); Helper helper = new Helper(); helper.setParam("Value1", (new Date()).toString()); detail.data = helper.getParams(); job.details.add(detail); detail = new JobDetail(); helper.setParam("Value1", "foo"); detail.data = helper.getParams(); job.details.add(detail);</code></pre> <p>Why does Elasticsearch change the given attribute to a date field, although we just fill in String values?<br> Furthermore we defined the value as a Map of Sting-String value pairs.<br> Is there a solution of this issue?</p> <p>We decided not to use JSON objects instead of our Map, because of the easy handling in further uses.</p>enMon, 26 Aug 2019 10:03:03 -0400https://answers.axonivy.com/questions/3903/elasticsearch-fail-because-auto-conversion-changes-string-values-into-date#3929<p>Solution one is not what we want. Solution two works fine. ...but it still makes no sense to me. The code as follow works: helper.setParam("Value1", (new Date() as java.util.Date).toString());</p> <p>Sorry, but for me it looks like a bug in ivy.</p>Adrian ImfeldMon, 26 Aug 2019 10:03:03 -0400https://answers.axonivy.com/questions/3903/elasticsearch-fail-because-auto-conversion-changes-string-values-into-date#3929https://answers.axonivy.com/questions/3903/elasticsearch-fail-because-auto-conversion-changes-string-values-into-date/3904<p>Hi Adrian</p> <p>As it looks like Elasticsearch converts the result of <code>ch.ivyteam.ivy.scripting.objects.Date.toString()</code> automatically into a Date type. As much as I know it is not possible to turn off this auto-conversion, most of the time it is a useful feature.</p> <p>To avoid this problem you have two possibilities:</p> <ol> <li>Overwrite the Elasticsearch template and redefine the field as String type.</li> <li>Don't use the <code>ch.ivyteam.ivy.scripting.objects.Date</code> but the <code>java.util.Date</code> class. Elasticsearch doesn't recognize the format in <code>toString()</code> automatically - or you can write your own Date output format with <code>SimpleDateFormat</code> (which goes into the same direction).</li> </ol> <p>I recommend solution 2.</p>Andreas RuschMon, 05 Aug 2019 02:36:22 -0400https://answers.axonivy.com/questions/3903/elasticsearch-fail-because-auto-conversion-changes-string-values-into-date/3904