To get a feel for the size of Bleve, checkout this graph that shows commit rates doing into Bleve versus Elasticsearch and Vespa: http://blog.minimum.se/assets/elasticsearch-open-source-comm... If you don't need heavy lifting, then "sonic" implemented in rust is a really nice lean alternative too: https://github.com/valeriansaliou/sonic FWIW, that graph is from a blog post I published earlier today: http://blog.minim…
Bleve: Full-text search and indexing for Go
21–30 of 65 posts
Re: Bleve: Full-text search and indexing for Go
#22One of the big things we're working on at the moment is improving the release process. In addition to semantic versioning of the APIs we have to think through how it applies to the binary artifacts created. We want Go modules to be supported and be a part of the solution, but we are also mindful not to break things for existing users.
Re: Bleve: Full-text search and indexing for Go
#23Blast is a server on top of it: https://github.com/mosuka/blast
Re: Bleve: Full-text search and indexing for Go
#24Earlier quoted context omitted.
Fork of Sphinx Search with a support team around it from my understanding.
I understand what it is but I'm not sure why it wasn't included. They forked specifically because nothing was happening in sphinx and they've been releasing new features.
Re: Bleve: Full-text search and indexing for Go
#25Blast is a server on top of it: https://github.com/mosuka/blast
I’d love to see some benchmarks of this against Elasticsearch.
To give a feel for a similar use case, and the ability to run a simple benchmark...
Re: Bleve: Full-text search and indexing for Go
#26Re: Bleve: Full-text search and indexing for Go
#27Forgive my ignorance on the topic of full-text search but is this supposed to compete with Elastic or is this more of an alternative to Lucene? If the latter, then wouldn't you be limited to indexing text datasets small enough to stay in memory?
Elastic is a distributed index which can't be said of Bleve afaik. Therefore, it's more like Lucene.
Re: Bleve: Full-text search and indexing for Go
#28Core contributor here, happy to try and answer any questions. One of the big things we're working on at the moment is improving the release process. In addition to semantic versioning of the APIs we have to think through how it applies to the binary artifacts created. We want Go modules to be supported and be a part of the solution, but we are also mindful not to break things for existing users.
Re: Bleve: Full-text search and indexing for Go
#29To get a feel for the size of Bleve, checkout this graph that shows commit rates doing into Bleve versus Elasticsearch and Vespa: http://blog.minimum.se/assets/elasticsearch-open-source-comm... If you don't need heavy lifting, then "sonic" implemented in rust is a really nice lean alternative too: https://github.com/valeriansaliou/sonic FWIW, that graph is from a blog post I published earlier today: http://blog.minim…
Re: Bleve: Full-text search and indexing for Go
#30Blast is a server on top of it: https://github.com/mosuka/blast
Dgraph (a graph database) also use Bleve for its full-text search indexing.