4 ms·
Bloodhound – Elasticsearch client and DSL for Haskell
- mwotton 12y agoas a contributor to the other ElasticSearch client - kudos. This is much nicer than ours in many ways :)
- coolsunglasses 12y agoThank you very much and thanks to everyone that helped me build this. You, carter, and the others in the Haskell/Haskell.au IRC channels were a big help. The thank-you list would be huge if I tried to list everybody that made a library I used or whose blog post helped me along.
- boothead 12y agoOther ES client? In haskell?
- mwotton 12y agoyeah - worked on it a bit with Ollie Charles. https://github.com/ocharles/Elasticsearch https://github.com/ocharles/Elasticsearch it's not very principled, tbh. uses error etc rather than proper sum types for returning errors.
- coolsunglasses 12y agoTo be fair, errors are implicitly encoded in the HTTP statuses and I'm not doing anything about Conduit's exceptions right now. This is something I'd like to fix later.
- boothead 12y agoAh right, I thought there might be another one I didn't know about! ocharles tends to be a lot more principled these days if it's any comfort :-)
- epimenov 12y agoAs far as I know bool filters are preferred over and/or filters (see http://www.elasticsearch.org/blog/all-about-elasticsearch-filter-bitsets/ http://www.elasticsearch.org/blog/all-about-elasticsearch-fi...) Seminearring and Monoid Filter could encourage usage of the bool filters, instead of and/or. Thank you otherwise, I was longing for something similar when I was editing JSON queries. Going to try that the next time I have to do some ES work.
- coolsunglasses 12y agoThis is great advice, I read the follow-up links in that post and they're very informative! I'll jot down a task for figuring out how to flip the Seminearring over to bool. The reason for the original design was that they mated to nested And/Or filters which I knew to be less than ideal but figured it work as a first pass. Thanks!
- funkyy 12y agoNaming is the same as Statamic Bloodhound plugin. Are those 2 projects related or just coincidence?
- coolsunglasses 12y agoUnfortunate coincidence. I've been on a "projects starting with letter B" streak[1] and Bloodhound is search related. Also I like dogs. [1]: http://bitemyapp.com/projects.html http://bitemyapp.com/projects.html
- eternalban 12y agoBear starts with a B.
- coolsunglasses 12y agoNaming a project Bear would be a little too megalomaniacal of me: https://twitter.com/bitemyapp/ https://twitter.com/bitemyapp/ :)
- eternalban 12y agoBut honey is elastic ..
- turar 12y agoAlso Apache Bloodhound.
- yalogin 12y agoHow popular is elasticsearch?
- lgas 12y agoIt's spreading pretty rapidly in my circles. It's used by a lot of popular sites, such as Github, Soundcloud, Stumbleupon, Quora, Foursquare, Etsy, etc. They have some case studies: http://www.elasticsearch.org/case-study/ http://www.elasticsearch.org/case-study/ eg. http://www.elasticsearch.org/case-study/github/ http://www.elasticsearch.org/case-study/github/ http://www.elasticsearch.org/case-study/soundcloud/ http://www.elasticsearch.org/case-study/soundcloud/ http://www.elasticsearch.org/case-study/stumbleupon/ http://www.elasticsearch.org/case-study/stumbleupon/
- Argorak 12y agoI run the Elasticsearch Berlin UG and we have a steady and fast influx of new people. I've rarely seen communities grow that fast. The community is great and active and Elasticsearch is caring a lot for that. http://www.meetup.com/Elasticsearch-UG-Berlin/ http://www.meetup.com/Elasticsearch-UG-Berlin/
- cies 12y agoFor what it's worth a gg-tends comparison between solr (the main ES competitor I know of) and ES itself. http://www.google.com/trends/explore#q=elasticsearch%2C%20solr&cmpt=q http://www.google.com/trends/explore#q=elasticsearch%2C%20so... TLDR; they are roughly equal in popularity according to gg-tends, ES growing very fast.
- coolsunglasses 12y agoMy impression is that Elasticsearch's growth is coming from being more popular outside of the Java ecosystem.
- MrRoger 12y agoWhy you never document your code? You didn't document your Clojure libs and now you're continuing the trend with Haskell. If you're going to make libs, please provide the adequate documentation with examples of usage in the code. I'm not gonna keep going back to the README. I'm going to use Hoogle and Hackage. All those comments in the README could be looking all pretty on Hackage right now.
- carterschonwald 12y agohuh, Chris definitely should add some comments to his code. I'll tease him about it for the next week!
- deleted 12y ago[deleted]
- coolsunglasses 12y agoIs there a particular Clojure library that you need more documentation for? I'll transfer the README docs over to Haddock/lhs when I do the next non-trivial release.
- the1 12y agomeh, types give you enough documentation. once you play around with examples on README, reading type annotations (that are actually written manually as a form of documentation) of functions in https://github.com/bitemyapp/bloodhound/blob/master/Database/Bloodhound/Client.hs https://github.com/bitemyapp/bloodhound/blob/master/Database... make sense. examples could be moved over into modules.. but I much much prefer to have examples in one place that could be read like a gentle introduction and walkthrough of the library. Said that, additional module and function documentation could be useful, too. But not at all if the library maintainer just fills stuff in to generate fat haddock. Again, type annotation says much. And, you're welcome to contribute documentation to the library.
- swuecho 12y agothat is frustrated me when entering functional language world. rarely good document compared to other language. In Perl, many modules will have their own tutorial
- cies 12y agoLooks really, really good. My Haskell app is just up to the point that search seems a logic next step and I will surely use ES and your lib for that.
- coolsunglasses 12y agoPing me if you need any help or have suggestions for improvements!