Bleve: Full-text search and indexing for Go

Re:Bleve: Full-text search and indexing for Go by molsson on Monday April 08, 2019 @11:54AM (#19606330)

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.minimum.se/2019/04/08/elastic-search-introductio...

[ Parent | on HN ]

Re:Bleve: Full-text search and indexing for Go by ako on Monday April 08, 2019 @01:43PM (#19607351)

How does this compare to full text search in Postgres?

[ Parent | on HN ]

Re:Bleve: Full-text search and indexing for Go by manigandham on Monday April 08, 2019 @02:55PM (#19608021)

Great blog post! First one I've seen with good comparisons to the other options. I would recommend adding Xapiand too: https://github.com/Kronuz/Xapiand

[ Parent | on HN ]

Re:Bleve: Full-text search and indexing for Go by molsson on Monday April 08, 2019 @03:03PM (#19608081)

Thanks (you can upvote it here if you want: https://news.ycombinator.com/item?id=19605334 )

I've added a mention of Xapian/Xapiand as well now and generated new graphs that include data for those two projects.

[ Parent | on HN ]

Re:Bleve: Full-text search and indexing for Go by drenvuk on Monday April 08, 2019 @12:35PM (#19606732)

Where the heck is manticore?

[ Parent | on HN ]

Re:Bleve: Full-text search and indexing for Go by uhhhhhhh on Monday April 08, 2019 @12:36PM (#19606741)

Fork of Sphinx Search with a support team around it from my understanding.

[ Parent | on HN ]

Re:Bleve: Full-text search and indexing for Go by drenvuk on Monday April 08, 2019 @12:38PM (#19606767)

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.

[ Parent | on HN ]

Re:Bleve: Full-text search and indexing for Go by molsson on Monday April 08, 2019 @01:08PM (#19607021)

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

[ Parent | on HN ]

Re:Bleve: Full-text search and indexing for Go by uhhhhhhh on Monday April 08, 2019 @12:44PM (#19606813)

I read that as "What" not "where", sorry.

[ Parent | on HN ]

Re:Bleve: Full-text search and indexing for Go by bratao on Monday April 08, 2019 @12:55PM (#19606917)

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

[ Parent | on HN ]

Re:Bleve: Full-text search and indexing for Go by lacksconfidence on Monday April 08, 2019 @05:25PM (#19609199)

Would you be willing to expand on this a bit? We run multiple elasticsearch clusters and there are pain points everywhere, I wonder where vespa improves?

[ Parent | on HN ]

Re:Bleve: Full-text search and indexing for Go by bratao on Monday April 08, 2019 @07:31PM (#19610195)

For us, Vespa It is in a different league. Some quick things I remember: - Native Tensor/ XGBoost support - Automatic data partitioning and auto balancing( no need to set shards before hand) - Jdisk (https://docs.vespa.ai/documentation/jdisc/) - This is the major feature for us. It enables us to create Distributed Applications that manipulate the search results directly on the nodes.

I'm not associated with the team, but I take every opportunity to promote it, as I think it is a very underrated project.

[ Parent | on HN ]