[ 
https://issues.apache.org/jira/browse/SOLR-17851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18013005#comment-18013005
 ] 

Gus Heck commented on SOLR-17851:
---------------------------------

For convenience I'll tell the story of SOLR-8349 here - it was added so that 
custom components that want to use a large memory object don't have to 
replicate that resource across all cores (the specific motivating case was a 
1GB map of US/Brittish post/zip-codes to gps coordinates used to infer GPS 
location for radius queries in response to post-codes and zipcodes). When I 
first implemented it, it didn't have anything to do with the blob store, but 
the feedback on that issue was that the blob store was the "right" way to 
manage large resources, and so it got rolled into that effort.

The specific challenge with sharing large resources in SOLR-8349 is that the 
SolrResourceLoader has it's own ClassLoader, so a resource loaded into a static 
field on a custom component is duplicated if that component is used in multiple 
cores (each core has it's own independent definition of the component class 
loaded by it's own ClassLoader). When you've got 30 cores, a 1GB map duplicated 
30 times gets painful. 

> Remove BlobHandler and .system collection from 10
> -------------------------------------------------
>
>                 Key: SOLR-17851
>                 URL: https://issues.apache.org/jira/browse/SOLR-17851
>             Project: Solr
>          Issue Type: Task
>          Components: blobstore
>    Affects Versions: main (10.0)
>            Reporter: Eric Pugh
>            Assignee: Eric Pugh
>            Priority: Major
>         Attachments: remove-blob-handler.patch
>
>
> Once the Schema Designer migration to the Filestore API is completed, we 
> should remove the BlobHandler and associated .system collection.   
> This issue proposes deprecating it in 9x now and removing in 10.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to