I do a lot of work with Solrcloudpy. It has a fantastic API for handling collections in Solrcloud, allowing you to shard your business logic across intelligent pivots and horizontally scale to an arbitrary size. This is super important stuff when you're in a multi-tenant, service-oriented world.
Keeping vital libraries like this up to date is important. As Solr evolves, we want to make sure you can continue to use Solrcloudpy with a minimum of disruption. There are other Solr libraries such as SolrClient, but this one in particular supports Python 3 only. If you have a high-scale infrastructure primarily in Python, you may be using Celery. A popular backend for Celery is RabbitMQ. The Celery community has no plans to add Python 3 support to their RabbitMQ driver, keeping many committed to 2.7 without changing backends, which has significant ramifications in operationalization, monitoring, and other production acceptance concerns. In other words, we've got a real hairy yak on our hands.
For this reason, I reached out to Didier Deshommes, the former maintainer of Solrcloudpy. His work was moving away from Solr, and he was looking for new maintainers. I worked with him to build out the Solrcloudpy organization in Github. We collaborated on delivering version 1.8.
Version 1.8 includes the following features:
- Compatibility with later versions of Solr 5.x
- Improved documentation for the specific purpose of adding code completion to popular IDEs
- An improved test plan for multiple versions of Solr
- Conformance to PEP8 standards
Now as one of the library's primary maintainers, I plan on doing some work in the future to add functionality in a backwards-compatible and well-tested manner. We welcome contributors and look forward to everyone's involvement in the future of this project. Thanks again to Didier Deshommes for the great work that he's done with Solrcloudpy, and to all its other former contributors.