Hi Solr Community,

I’ve opened a pull request to add an *Azure Blob Storage backup repository
module* to Solr:

https://github.com/apache/solr/pull/3750
<https://github.com/apache/solr/pull/3750?utm_source=chatgpt.com>

*JIRA:* https://issues.apache.org/jira/browse/SOLR-17949
<https://issues.apache.org/jira/browse/SOLR-17949?utm_source=chatgpt.com>

This module introduces native integration with Azure Blob Storage for Solr
backups and restores, extending the existing cloud storage options (S3,
GCS, etc.).
It implements the BackupRepository interface and supports multiple
authentication mechanisms:

   -

   Account key–based auth
   -

   SAS token–based auth
   -

   Service principal–based auth (via Client ID/Secret)
   -

   Managed identity–based auth (for Azure-hosted Solr instances)

The module also supports Azurite, allowing local testing and CI validation
without requiring Azure credentials.
------------------------------

*WHY IT’S USEFUL*

   -

   Many organizations use Azure for cloud storage.
   -

   Provides a cost-effective backup solution for Azure-hosted Solr
   instances.
   -

   Supports enterprise-grade authentication via Azure AD.

------------------------------

*KEY HIGHLIGHTS*

   -

   Mirrors the structure and configuration of the existing s3-repository
   module for consistency.
   -

   Adds a new azure-blob-repository module under modules/.
   -

   Includes integration tests for backup/restore and authentication flows.
   -

   Compatible with Solr 10.x and Java 17+.
   -

   Reference Guide (Backup & Restore section) updated with usage
   instructions and configuration examples.

------------------------------

I’d appreciate feedback on:

   -

   The overall module structure and naming conventions.
   -

   Parity with other repository modules (configuration parameters, error
   handling).
   -

   Suggestions for test coverage, documentation layout, or dependency
   management.

Once the module stabilizes, I plan to follow up with updates in the Solr
Operator to add Azure backup support.

Thanks in advance for taking the time to review and share your feedback!

Thank you,
Prateek Singhal
(prateeksolr)

Reply via email to