Is it possible to identify multiple hosts with elastigo? I can't seem to find anything specific to that. Anyone using elastigo in a PROD setting? I would really like to attempt using a go based app for our web services, but we have a requirement with ElasticSearch, Redis and possibly a few others. Just not sure that the drivers for go are ready yet.
Any suggestions / info would be appreciated.
Thanks,
S
Phillip Edwards. Elasticsearch is a popular datastore for all types of information. It is distributed for speed and scalability and can index many types of content which makes it highly searchable. It uses simple REST APIs for ease of access.
Make a new index of Elasticsearch After you've deleted the Elastersearch cluster's old index, use the method CreateIndex() to make a new one in Golang. Pass the name of the index. Pass the string of Context mappings. Finally, pass the Context object instance.
Elasticsearch allows you to store, search, and analyze huge volumes of data quickly and in near real-time and give back answers in milliseconds. It's able to achieve fast search responses because instead of searching the text directly, it searches an index.
My answer could be a bit late, but still... I have recently (mid 2016) chosen olivere/elastic over elastigo as Elasticsearch Go client for our production application.
Reasons for the choice were:
I would highly recommend you to have a look at olivere/elastic if you haven't made decision yet. Also there is a blog post Working With Elasticsearch in Go, which demonstrates on example how to use olivere/elastic to index and search documents. (In case you want to get a flavour of how the code looks like.)
elastigo is working very well in a production setting for us. As far as detecting 'hosts' my best suggestion is to read the elasticsearch documentation which describes their cluster management scheme - most of that work is handled by elasticsearch itself. In our (rather straightforward) usage I've never had to think about anything beyond the server host address:port - nodes self-connect to a named cluster when brought online (with proper configuration parameters) and load balancing is handled within elasticsearch itself.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With