[
https://issues.apache.org/jira/browse/SOLR-11250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christine Poerschke updated SOLR-11250:
---------------------------------------
Attachment: SOLR-11250.patch
bq. ... the name of wrapper model can be used as the alias of the wrapped
model. ... if we fix the name of wrapper model (like "prodModel"), users can
always use same rerankModel (i.e, "prodModel") even if the version of wrapped
model was changed (like "20171103" to "20171206"). I think this feature is
useful because we can avoid the influence of updating models to users (in other
words, we can develop front-end and back-end separately).
That summarises the wrapper/wrapped model naming choices very nicely, thank you!
(And actually people might even wish to use the wrapper model just in order to
get the aliasing effect i.e. the wrapped model need not necessarily be a 'too
large for ZooKeeper' model.)
Attaching slightly revised patch:
* reverted the wrapper/wrapped model name restriction as per above
* Solr Ref Guide entry:
** wrapper/wrapped model feature store restriction mentioned and illustrated
** added class to the models list/table
** no-longer-present "format" param removed from example
* solrconfig-ltr.xml comment updated to match the final DefaultWrapperModel
class name
* rebased against latest master and added {{assumeWorkingMockito()}} calls as
per SOLR-11606
----
{{ant precommit}} and tests pass. Does anyone else have any further comments or
suggestions here at this point? If not then I think we're good to go here and
I'll proceed to commit to master branch sometime next week and then cherry-pick
to branch_7x a couple of days later.
> Add new LTR model which loads the model definition from the external resource
> -----------------------------------------------------------------------------
>
> Key: SOLR-11250
> URL: https://issues.apache.org/jira/browse/SOLR-11250
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: contrib - LTR
> Reporter: Yuki Yano
> Assignee: Christine Poerschke
> Priority: Minor
> Attachments: SOLR-11250.patch, SOLR-11250.patch, SOLR-11250.patch,
> SOLR-11250.patch, SOLR-11250_master.patch, SOLR-11250_master_v2.patch,
> SOLR-11250_master_v3.patch, SOLR-11250_master_v4.patch
>
>
> We add new model which contains only the location of the external model and
> loads it during the initialization.
> By this procedure, large models which are difficult to upload to ZooKeeper
> can be available.
> The new model works as the wrapper of existing models, and deligates APIs to
> them.
> We add two classes by this patch:
> * {{ExternalModel}} : a base class for models with external resources.
> * {{URIExternalModel}} : an implementation of {{ExternalModel}} which loads
> the external model from specified URI (ex. file:, http:, etc.).
> For example, if you have a model on the local disk
> "file:///var/models/myModel.json", the definition of {{URIExternalModel}}
> will be like the following.
> {code}
> {
> "class" : "org.apache.solr.ltr.model.URIExternalModel",
> "name" : "myURIExternalModel",
> "features" : [],
> "params" : {
> "uri" : "file:///var/models/myModel.json"
> }
> }
> {code}
> If you use LTR with {{model=myURIExternalModel}}, the model of
> {{myModel.json}} will be used for scoring documents.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
