# Bad charset encoding in field names (II)

**URL:** <https://discuss.elastic.co/t/bad-charset-encoding-in-field-names-ii/129715>\
**Category:** Elasticsearch\
**Created:** [April 26, 2018, 3:29pm UTC](https://discuss.elastic.co/t/bad-charset-encoding-in-field-names-ii/129715 "2018-04-26T15:29:21Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Thiago\_Ruiz](https://avatars.discourse-cdn.com/v4/letter/t/b487fb/32.png) [@Thiago\_Ruiz](https://discuss.elastic.co/u/Thiago_Ruiz)\
**Post date:** [April 26, 2018, 3:29pm UTC](https://discuss.elastic.co/t/bad-charset-encoding-in-field-names-ii/129715/1 "2018-04-26T15:29:22Z")

</div>

Hi!

I have exactly the same issue as described by Ondřej Bílka on this thread:

> [@Bad charset encoding in field names](https://discuss.elastic.co/t/bad-charset-encoding-in-field-names/107947):
>
> I have an issue with ElasticSearch after upgrade to 5.6. I am generating documents using logstash and dynamic fields using native Ruby extension in logstash: filter { if [attributes] =~ /[^\s\\]+/ { kv { source =\> "attributes" field\_split =\> ";" value\_split =\> ":" target =\> "attributes" } ruby { code =\> " event.get('attributes').each do |cusField| event.set(cusField[0], cusField[1].split(',')) end " } } In these dynamic fields, there are ke…

Since the discussion was closed I'm trying to reopen it again.

All my files are in UTF-8 and just the dinamic fields are wrong - I have one 'message' field with all the data and on that field the special characters are ok.

Thanks.

---

<div class="post-metadata">

**Author:** ![Ondrej\_Bilka](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ondrej_bilka/32/2912_2.png) [@Ondrej\_Bilka](https://discuss.elastic.co/u/Ondrej_Bilka)\
**Post date:** [April 26, 2018, 3:48pm UTC](https://discuss.elastic.co/t/bad-charset-encoding-in-field-names-ii/129715/2 "2018-04-26T15:48:43Z")

</div>

Hi, my only solution was to change the keys to web url-safe slugs...

---

<div class="post-metadata">

**Author:** ![Thiago\_Ruiz](https://avatars.discourse-cdn.com/v4/letter/t/b487fb/32.png) [@Thiago\_Ruiz](https://discuss.elastic.co/u/Thiago_Ruiz)\
**Post date:** [April 26, 2018, 5:00pm UTC](https://discuss.elastic.co/t/bad-charset-encoding-in-field-names-ii/129715/3 "2018-04-26T17:00:29Z")

</div>

Sorry to hear that....

I'll try to solve this issue a little longer.

This was not a problem until I updated all ELK tools from 5.5.2 to 6.2.3

---

<div class="post-metadata">

**Author:** ![Ondrej\_Bilka](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ondrej_bilka/32/2912_2.png) [@Ondrej\_Bilka](https://discuss.elastic.co/u/Ondrej_Bilka)\
**Post date:** [April 27, 2018, 10:05am UTC](https://discuss.elastic.co/t/bad-charset-encoding-in-field-names-ii/129715/4 "2018-04-27T10:05:35Z")

</div>

I wish you good luck 🙂 and if you will figure anything out, please let me know..  
On the other hand I think that "webalized" string keys are much more secured because of possible encoding issues in another parts of application.

---

<div class="post-metadata">

**Author:** ![Thiago\_Ruiz](https://avatars.discourse-cdn.com/v4/letter/t/b487fb/32.png) [@Thiago\_Ruiz](https://discuss.elastic.co/u/Thiago_Ruiz)\
**Post date:** [May 2, 2018, 2:41pm UTC](https://discuss.elastic.co/t/bad-charset-encoding-in-field-names-ii/129715/5 "2018-05-02T14:41:09Z")

</div>

Yeah... i gave up and used this on my ugly field inside of a ruby filter:

> event.set(strKey.tr( "ÀÁÂÃÄÅàáâãäåAaAaAaÇçCcCcCcCcÐðDdÐdÈÉÊËèéêëEeEeEeEeEeGgGgGgGgHhHhÌÍÎÏìíîïIiIiIiIiIiJjKk?LlLlLl??LlÑñNnNnNn???ÒÓÔÕÖØòóôõöøOoOoOoRrRrRrSsSsSsŠš?TtTtTtÙÚÛÜùúûüUuUuUuUuUuUuWwÝýÿYyŸZzZzŽž", "AAAAAAaaaaaaAaAaAaCcCcCcCcCcDdDdDdEEEEeeeeEeEeEeEeEeGgGgGgGgHhHhIIIIiiiiIiIiIiIiIiJjKkkLlLlLlLlLlNnNnNnNnnNnOOOOOOooooooOoOoOoRrRrRrSsSsSsSssTtTtTtUUUUuuuuUuUuUuUuUuUuWwYyyYyYZzZzZz"), strValue.to\_f)

Don't know how is the performance of this, though I dont have a high volume of data going through this code..

---

<div class="post-metadata">

**Author:** ![Kyo\_Hwang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kyo_hwang/32/31502_2.png) [@Kyo\_Hwang](https://discuss.elastic.co/u/Kyo_Hwang)\
**Post date:** [May 23, 2018, 6:02am UTC](https://discuss.elastic.co/t/bad-charset-encoding-in-field-names-ii/129715/6 "2018-05-23T06:02:18Z")

</div>

There is still a problem when I use a docker image sebp/elk 6.2.3 or 6.2.4.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 20, 2018, 6:02am UTC](https://discuss.elastic.co/t/bad-charset-encoding-in-field-names-ii/129715/7 "2018-06-20T06:02:33Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.