- https://www.elastic.co/guide/en/elasticsearch/reference/6.x/breaking-changes-6.0.html
- https://github.com/elastic/elasticsearch-ruby
- https://stackoverflow.com/questions/47452770/no-handler-for-type-string-declared-on-field-name
I notice that the code doesn’t seem to be using the actual Ruby gem at this time; and that there’s an issue with the deprecation of “string” for “text”. Having trouble finding that in the code to fix; otherwise, I can imagine that the logic that detects 5.x vs 6.x usage, could be used to indicate if “string” or “text” should be used.