Live data from Hacker News

Bleve: Full-text search and indexing for Go

blevesearch.com

21–30 of 65 posts

Re: Bleve: Full-text search and indexing for Go

#21
post #14

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…

Vespa.ai is the Number 1. And I get behind it, from a previous ElasticSearch user , Vespa is amazing!!!

Re: Bleve: Full-text search and indexing for Go

#22
Core 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

#24
post #18

Earlier 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.

Good point; I've added it now, both to the blog post and to the graph: https://blog.minimum.se/assets/elasticsearch-open-source-com...

Re: Bleve: Full-text search and indexing for Go

#25
post #9
post #3

Blast is a server on top of it: https://github.com/mosuka/blast

I’d love to see some benchmarks of this against Elasticsearch.

I'd love to see some more projects with similar instructions to: https://github.com/mosuka/blast/blob/master/README.md#wikipe...

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

#27
post #7
post #6

Forgive 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.

Correct. Couchbase uses Bleve to provide the distributed search index/query. See: https://docs.couchbase.com/server/6.0/fts/full-text-intro.ht...

Re: Bleve: Full-text search and indexing for Go

#28
post #22

Core 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.

Thank you very much for Bleve! It was useful for me on a few projects. And, do not be afraid to break things in the future major version, modules are handling that nicely.

Re: Bleve: Full-text search and indexing for Go

#29
post #14

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…

How does this compare to full text search in Postgres?

Re: Bleve: Full-text search and indexing for Go

#30
post #23
post #3

Blast 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.

(author of Dgraph) We use specific libraries from Bleve to do, for e.g., full-text tokenization and such. But, we use our own indexing and storage mechanism, not Bleve's.
Post reply on HN