-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve CouchDB "plugin" architecture for geo/search #1269
Comments
@davisp any news on this? |
From the merged #1516: Once #1515 is done, this should be easy.
|
Any more updates on this? It would be so wonderful not to be reliant on IBM! They can't even seem to handle billing 🤦🏻♂️ |
If there's progress, you'll see it linked here. As there is no update, there has been no progress. |
Part of this merged with #2037 . |
I'm curious about the status of this feature. Is there anything I/we can do to help this move forward? |
@dsebastien as far as i understood @wohali last month it will be part of couchdb 3. |
@lucidNTR Indeed, i just saw the details through this recent talk: https://www.youtube.com/watch?v=SjXyVZZFkBg. Apparently Couch v3 will be released soon! :) |
Dreyfus / clouseau is now part of couchdb as part of 3.x+ Geo hasn't gotten much support and demand at Cloudant and as such, is now removed. There a few remnants of it in the Apache CouchDB code but we should probably remove those. |
We've had multiple discussions on the mailing lists and IRC previously about this problem: right now, you need to recompile CouchDB from scratch if you want to add search (dreyfus) or geo (hastings) support.
This isn't great, and makes things like Docker images that include references to those things unwieldy (since you can't just add another layer on top of the existing
couchdb
image.)@davisp you said you had some specific ideas here, can you elaborate in this issue? Thanks!
The text was updated successfully, but these errors were encountered: