Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Bleve: Full-text search and indexing for Go

blevesearch.com

Post reply on HN
Print view View original

51–60 of 65 posts

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

#52

Post by mschoch »

philip1209 wrote: post #50

I'm looking at adding better search to our app soon, and I honestly don't really have knowledge of any systems out there. Answer to this basic question might help both me and others: How would you deploy Bleve in a 12-factor app environment? (Does Bleve directly support any persistence? Does it support distributed workloads? Could a "trained" model get passed to read-only nodes?)

Bleve is just a library that provides this functionality, you first have to build an application that uses Bleve, and deploy that.

Bleve does (optionally) support persistence, so reading/writing files is one place it does directly interact with the environment. The environment must support mmap.

There are several projects which support distributed index/search workloads with Bleve. The exact approaches vary, but they all use Bleve to perform node local operations, and coordinating this is done at a higher level by the application.

I suspect I don't understand the terminology you're using in the last question, as Bleve has no training, models or nodes.

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

#54

Post by lacksconfidence »

bratao wrote: post #21
molsson wrote: 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!!!

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?

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

#56

Post by cellularmitosis »

_adamb wrote: post #44

I am left confused, amused, and amazed by their choice of logo. I love it and it makes me reconsider my, apparently conventional, logo choices...

https://www.youtube.com/watch?v=UM0jtD_OWLU

holy smokes: https://www.youtube.com/watch?v=K-tUQTw_Vtk

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

#57

Post by networkimprov »

mschoch wrote: post #43
networkimprov wrote: post #38

Are the maintainers aware that Bleve is unsafe to use on MacOS with Go 1.11 and earlier? https://github.com/golang/go/issues/26650

We were made aware of this in September: https://github.com/blevesearch/bleve/issues/783#issuecomment...

That was me :-) It puzzled me that there was no public comment about it.

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

#58

Post by netdur »

mschoch wrote: 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.

I was looking at it and wonder if I can plug it to remote database, or any abstract mechanism to store index in cloud space, I want to run it on cloud.

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

#59

Post by bratao »

lacksconfidence wrote: post #54
bratao wrote: post #21

Earlier quoted context omitted.

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

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?

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.

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

#60

Post by ronnier »

dmitryminkovsky wrote: post #49

Really nice to see the Go ecosystem developing. The other day I was searching for a link/URL extraction library and the best one I could find was in Go: https://github.com/mvdan/xurls ("best" because it actually uses a list of TLDs, for example: https://github.com/mvdan/xurls/blob/master/tlds.go ). Was an unusual experience not finding something as good for Java.

I’ve had the same experience with video encoding and image libraries. All the momentum is in Go.
Post reply on HN