[SOLR-8773] Make blob store usage intuitive and robust

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Assignee: Noble Paul
• Reporter: Noble Paul
• Created: 02/Mar/16 11:21
• Updated: 29/Sep/21 20:50
• Resolved: 29/Sep/21 20:50

Description

blob store is provided as a feature and the only current use is to load jars from there. Ideally, all resources should be loadable from blob store. But, it is not yet ready for prime time because it is just a simple crud handler for binary files. We should provide nice wrappers (java APIs as well as http APIs) which mask the complexity of the underlying storage.

Sub-Tasks

• components that rely on blob store should be loaded as soon as it is available: Resolved
• SolrResourceLoader should be able to load content from blob store: Resolved
• Allow sharing of large in memory data structures across cores: Closed
• Store the latest available version of a blob so that some components can access it w/o version: Resolved
• provide friendly APIs to edit well known formats like json and text files: Resolved
• CoreContainer level plugins should be loadable from blob store: Resolved
• Remove documentation of ZooKeeper sysprop jute.maxbuffer once the blob store is a viable alternative for storing/loading large configuration files everywhere in Solr: Resolved
• classes referenced in schema.xml should also support loading from the blob store: Resolved
• ManagedResources should be able to load from blob store: Resolved