karmi

vor 3 Jahrendiscuss

Part practical demonstration of differences between lexical and semantic search in Elasticsearch, with a Sentence Transformer model and the Quora dataset, part text embeddings explanation using Saussure's theory of language.

karmi

vor 12 Jahrendiscuss

Have a look here: https://github.com/elasticsearch/elasticsearch-rails/tree/ma... -- it offers a "repository" based approach to persistence. An "ActiveRecord-like" pattern is being actively working on in the `persistence-model` branch (https://github.com/elasticsearch/elasticsearch-rails/pull/91)

karmi

vor 14 Jahrendiscuss

Try http://codeclimate.com

karmi

vor 14 Jahrendiscuss

Link to the Ember Data adapter: https://github.com/karmi/ember-data-elasticsearch/, link to the gist with Goliath proxy for Twitter @Anywhere authentication: https://gist.github.com/3369662#file_proxy.rb

karmi

vor 14 Jahrendiscuss

That's legitimate concern -- you can of course put an Nginx proxy in front of elasticsearch to deny DELETE requests (see eg. http://www.elasticsearch.org/tutorials/2012/03/21/deploying-...)

But wait for an article at the http://elasticsearch.org blog with an example of a more sophisticated, Ruby-based proxy.)

karmi

vor 14 Jahrendiscuss

Check out the example application as well: https://github.com/karmi/ember-data-elasticsearch/tree/maste...

karmi

vor 14 Jahrendiscuss

Also, don't forget to check the ecosystem around elasticsearch: clients, integration, Puppet & Chef manifests/recipes, etc: http://www.elasticsearch.org/guide/appendix/clients.html

karmi

vor 14 Jahrendiscuss

Cubism is pretty easy to work with, or? See my heavily annotated sketch of continuous polling with Cubism; http://bl.ocks.org/2689616

karmi

vor 14 Jahrendiscuss

Running ElasticSearch on AWS is pretty easy, see http://www.elasticsearch.org/tutorials/2012/03/21/deploying-...

karmi

vor 15 Jahrendiscuss

While I understand where you're coming from, Max, this is really dangerous delusion. Couch just lost the drive it had in the beginning, for whatever reasons, crazy focus on "data liberation" and cell phones included.

That said, I agree with @dasil003 above that Couch played a irreplaceable role in getting people on the NoSQL track. I speak from my own experience. Compared to Mongo, Couch allowed me to wrap my head about design differences in the NoSQL world.

It's sad to see Couch fade into obscurity, but hey!, it's initial drive, it's original story (cf. the Rubyfringe video of Damien's talk), is an important part of "NoSQL archeology" for me.

karmi

vor 15 Jahrendiscuss

> Each modification generates a new version of the document. (...) we don’t need it, and there’s no way to disable it (...)

Note that there's a `_revs_limit` setting available: <http://wiki.apache.org/couchdb/HTTP_database_API>. It's very beneficial for a use case like yours.

(Though I've seen CouchDB performing rather poorly when taking really heavy read/write load or compacting big datasets, on occasion.)

Submissions

Semantic Search with Elasticsearch, Sentence Transformers and the Quora Dataset

The architecture of the Go client for Elasticsearch

New Go Client for Elasticsearch

Create Ember.js applications with persistence in elasticsearch

Ember.js Data Adapter for elasticsearch

Deploy ElasticSearch clusters with Chef Solo on AWS

“Reversed” or “Real Time” Search with ElasticSearch and Ruby

Ruby/Sinatra interface for displaying info from multiple Monits instances

comments