From 0f8371fa18d037c0925d32075e88e5c110f268e6 Mon Sep 17 00:00:00 2001 From: Chuck Lu Date: Wed, 15 Jul 2020 02:34:08 +0800 Subject: [PATCH] Update README.md (#344) add link for issue 184 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 8a422978..d3a9dd37 100644 --- a/README.md +++ b/README.md @@ -125,7 +125,7 @@ var loggerConfig = new LoggerConfiguration() Be aware that there is an explicit and implicit mapping of types inside an Elasticsearch index. A value called `X` as a string will be indexed as being a string. Sending the same `X` as an integer in a next log message will not work. ES will raise a mapping exception, however it is not that evident that your log item was not stored due to the bulk actions performed. -So be careful about defining and using your fields (and type of fields). It is easy to miss that you first send a {User} as a simple username (string) and next as a User object. The first mapping dynamically created in the index wins. See also issue #184 for details and a possible solution. There are also limits in ES on the number of dynamic fields you can actually throw inside an index. +So be careful about defining and using your fields (and type of fields). It is easy to miss that you first send a {User} as a simple username (string) and next as a User object. The first mapping dynamically created in the index wins. See also issue [#184](https://github.com/serilog/serilog-sinks-elasticsearch/issues/184) for details and a possible solution. There are also limits in ES on the number of dynamic fields you can actually throw inside an index. ### A note about Kibana