We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
input { elasticsearch { hosts => "10.x.y.z:9200" index => "data_for_mapping_test" query => ' { "query": { "term": { "_id": { "value": "1" } } } } ' } } filter { elasticsearch { hosts => ["10.x.y.z:9200"] index => "mappings" query_template => "/etc/logstash/conf.d/mapping_test.dsl" # query => '{ "query": { "term": { "AssetType": "%{AssetType}"} } }' fields => {"AssetTypeGrouping" => "AssetTypeGroupingMapped"} enable_sort => false } } output { elasticsearch { hosts => ["10.x.y.z:9200"] index => "mappings_test" } }
"AssetType":"\\Demo\\Something"
mappings
{ "AssetType": "\\Demo\\Something", "AssetTypeGrouping": "marketing assets" }
:error=>#<LogStash::Json::ParserError: Unrecognized character escape 'D' [...]
NOTE: It helped (worked as expected) when I added the following step in the query parsing in the plugin code:
query_tmp = event.sprintf(@query_dsl).gsub!('\\', '\\\\\\')
So it seems that the query parser doesn't understand backslashes in the query string. Is it the solution or am I doing something completely stupid?
The text was updated successfully, but these errors were encountered:
Sorry about the delay here :-(
Did the fix in ElasticSearch help with the issue on the Logstash side?
Sorry, something went wrong.
No branches or pull requests
My input data contains a field like this:
"AssetType":"\\Demo\\Something"
My
mappings
index contains documents like this:NOTE: It helped (worked as expected) when I added the following step in the query parsing in the plugin code:
So it seems that the query parser doesn't understand backslashes in the query string.
Is it the solution or am I doing something completely stupid?
The text was updated successfully, but these errors were encountered: