Hello, I have a case where each document is likely to introduce some specific & often unique properties -- leading to millions or more fields. The values stored under these should be searchable. But the mapping structure itself is not used in queries.
Having ElasticSearch treat these as dynamic fields works -- but how well does ElasticSearch cope with very large mappings? Am I right in thinking each property adds a field to the mapping, which is shared & held in memory by all nodes? So a mapping can become too large, and create performance issues. E.g 100 million documents might lead to gigabytes of ram locked up modelling the mapping. Is that correct? You can switch off dynamic fields altogether -- but then I think the content stored within them becomes unsearchable. Is there a way to have dynamic fields accessible to search, without modelling them as part of the mapping? Thank you & Best regards, - Daniel -- Dr Daniel Winterstein Director A: CodeBase Argyle House, Edinburgh, EH3 9DR M: +44 (0)772 5172 612 http://winterwell.com http://sodash.com -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEmLStmrGs%2BHaW%3De1XChi%3DFQ_LKEPEntRUvT8zt_BJKPUESkeg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
