Comments (4)
I would say that it would be a good idea to try to recruit some maintainers who are active users. I don't think either Chris nor I use the package anymore. I've not had time to be a good maintainer so if someone is getting use out of it, I'd like to allow them to keep it going. Is that something you'd be interested in? I can also put a notice in the README.
from bloodhound.
I've invited 3 people to be collaborators on the repository who've contributed PRs and that seem trustworthy, let me know if there's anything else you'd like me to do to facilitate development and maintenance.
I can weigh in on design/API questions if people would like but I don't have time for the heavy-lifting, on track to have 3 kids under the age of 3 this year.
from bloodhound.
I accepted the invite, but I hate to say that I'm no longer an active user either. I do still use elasticsearch at work, but elasticsearch's API is just too much of a mess to target with a library. It introduces breaking changes a lot, and the main way to query Elasticsearch is just to go through kibana. At work, we use https://github.com/layer-3-communications/elasticsearch-interchange (our own library), which is a much less ambitious project than bloodhound. It supports bulk requests, bulk responses, and search responses (all at a high level). It could be a smarting point for anyone else going down this dreary road.
from bloodhound.
The intense API churn and lack of machine ingestible schemas for the API is a huge problem. It makes maintaining a library that has a high degree of fidelity with the API's underlying schema and meaningful, safe representations in the types very laborious. Apart from it being unpaid labor, Elastic has never even given me the time of day when I tried to reach out to them about schemas or specifications that people could use to generate client APIs. Part of what baffles me about this is that generating clients from API specifications is clearly where the industry is headed more generally.
There's no incentive for me to tilt at these windmills unless I need the library to do something for me and I haven't in a long time. If Elastic wants people to contribute to their ecosystem for free they need to at least show some interest and talk to the parts of the community that are building things for their platform. They might not care about Haskell but what I wanted to discuss with them is something that would've benefited everyone including Elastic themselves as far as client dev & maintenance goes.
from bloodhound.
Related Issues (20)
- Fuzziness option in MatchQuery HOT 1
- ES 6.4.2 HOT 9
- About Mappings HOT 2
- DocId needs url-encoding for certain operations HOT 7
- Docker Compose support so that full test runs can be spun up
- Re-unifying Bloodhound's implementation HOT 4
- Update to Elastic 7.x (currently 7.4)
- Support count API HOT 1
- Is it possible to use a later version of containers and http-client HOT 2
- Derive Mapping
- Support GHC 8.8 HOT 1
- Update docs at Hackage
- Latest version low upper cap HOT 2
- Build errors with `aeson-2.0.1.0` HOT 1
- Search parameter `min_score` is not supported
- Library redesign HOT 1
- Not possible to build with http-client >= 0.7 HOT 2
- Add example that deserializes response from ES HOT 2
- `parseEsResponse` not able to parse a "document not found" response HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from bloodhound.