[TR-130] Manager should use Index specified in Request object Created: 15/Oct/09  Updated: 05/Apr/11  Resolved: 25/Mar/11

Status: Resolved
Project: Terrier Core
Component/s: .querying
Affects Version/s: None
Fix Version/s: 3.5

Type: Bug Priority: Major
Reporter: Rodrygo L. T. Santos Assignee: Rodrygo L. T. Santos
Resolution: Fixed  
Labels: None

Issue Links:
Block
is blocked by TR-67 Request object should contain the Index Resolved

 Description   
This will faciliate collection enrichment.

 Comments   
Comment by Craig Macdonald [ 29/Jan/10 ]

Tagging for 3.1

Comment by Rodrygo L. T. Santos [ 25/Mar/11 ]

Manager.getMatchingModel currently takes as argument a Matching class (as a String), and returns a corresponding Matching object, instantiated with the default Index kept by the Manager.

Instead (or complementarily), Manager.getMatchingModel should take a Request object as argument, so that a Matching object could be created based on the specified Matching, but also on the Index used by the Request.

Comment by Rodrygo L. T. Santos [ 25/Mar/11 ]
  • Both Matching and WeightingModel are instantiated according to the specifications in the Request object.
  • getWeightingModel now uses WeightingModelFactory.
Generated at Fri Dec 15 06:31:56 GMT 2017 using JIRA 7.1.1#71004-sha1:d6b2c0d9b7051e9fb5e4eb8ce177ca56d91d7bd8.