com.fasterxml.jackson.core.JsonParseException: Unrecognized character escape '.' (code 46) #75531
Labels
>bug
:Core/Infra/REST API
REST infrastructure and utilities
:Search/Search
Search-related issues that do not fall into other categories
Team:Core/Infra
Meta label for core/infra team
Team:Search
Meta label for search team
Elasticsearch version (
bin/elasticsearch --version
):Version: 6.8.17, Build: default/deb/206f6a2/2021-07-01T18:51:20.391869Z, JVM: 1.8.0_242
Plugins installed: []
analysis-icu analysis-phonetic
JVM version (
java -version
):openjdk version "11.0.6" 2020-01-14
OpenJDK Runtime Environment (build 11.0.6+10-post-Ubuntu-1ubuntu118.04.1)
OpenJDK 64-Bit Server VM (build 11.0.6+10-post-Ubuntu-1ubuntu118.04.1, mixed mode, sharing)
OS version (
uname -a
if on a Unix-like system):Linux b2cb87e8e202 5.4.0-1051-aws #53~18.04.1-Ubuntu SMP Fri Jun 18 14:53:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Description of the problem including expected versus actual behavior:
On Magento 2 (where ElasticSearch is default option) I have an issue that is quite difficult to identify. And I would like to create the issue on Magento2 github project, but unfortunately I do not have valid steps to reproduce. But so far I have steps to reproduce here.
Let me show you my blurry understanding of the problem:
There is a string "Pris per fp. ." (not only this, there are others that share the same feature). It has a dot and a space that is preceding a dot and even one more dot before. My guess is that somewhere between PHP and MySQL and Elastic there is a misunderstanding about one of these suspicious sequences:
The shop is selling different details like screw drivers or for example screen replacements. So even this
2.5x3.2.
is potential issue. I am still in process of bug investigation. Now let't go back to Elastic related stuff.Steps to reproduce:
Please include a minimal but complete recreation of the problem,
including (e.g.) index creation, mappings, settings, query etc. The easier
you make for us to reproduce it, the more likely that somebody will take the
time to look at it.
Expected result:
Actual result:
Provide logs (if relevant):
On production I see these logs
The text was updated successfully, but these errors were encountered: