[
https://issues.apache.org/jira/browse/SOLR-12590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16560103#comment-16560103
]
Christine Poerschke commented on SOLR-12590:
--------------------------------------------
bq. ... added info about how the resource loader works. ... the
learning-to-rank large model discussion to point to local storage as an
alternative, but I think it should be applicable; I haven't tried myself. ...
is it possible that that indirection is not necessary?
Good question. In your patch the "Resources in ConfigSets on ZooKeeper" lead
paragraph is:
bq. Under SolrCloud, resources to be loaded are first looked up in ZooKeeper
under the collection's configset znode. If the resource isn't found there,
Solr will fall back to loading resources from the filesystem.
A nicely concise and clear lead paragraph, I like it. Side question: was this
fallback logic 'always' there (and I just didn't know about it, oops) or is it
something introduced in a recent-ish version?
Either way, if the documentation provides one recommended way of doing things
that should be clearest from a user's point of view. So yes, if the wrapper
model concept is not or no longer needed then let's not mention it in the
documentation.
> Improve Solr resource loader coverage in the ref guide
> ------------------------------------------------------
>
> Key: SOLR-12590
> URL: https://issues.apache.org/jira/browse/SOLR-12590
> Project: Solr
> Issue Type: Task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: documentation
> Reporter: Steve Rowe
> Assignee: Steve Rowe
> Priority: Major
> Attachments: SOLR-12590.patch
>
>
> In SolrCloud, storing large resources (e.g. binary machine learned models) on
> the local filesystem should be a viable alternative to increasing ZooKeeper's
> max file size limit (1MB), but there are undocumented complications.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
