Terrier Core

Manager should use Index specified in Request object

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 3.5
  • Component/s: .querying
  • Description:
    This will faciliate collection enrichment.

Issue Links

Activity

Hide
Craig Macdonald added a comment - 29/Jan/10 3:57 PM

Tagging for 3.1

Show
Craig Macdonald added a comment - 29/Jan/10 3:57 PM Tagging for 3.1
Hide
Rodrygo L. T. Santos added a comment - 25/Mar/11 12:25 PM

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.

Show
Rodrygo L. T. Santos added a comment - 25/Mar/11 12:25 PM 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.
Hide
Rodrygo L. T. Santos added a comment - 25/Mar/11 2:22 PM
  • Both Matching and WeightingModel are instantiated according to the specifications in the Request object.
  • getWeightingModel now uses WeightingModelFactory.
Show
Rodrygo L. T. Santos added a comment - 25/Mar/11 2:22 PM
  • Both Matching and WeightingModel are instantiated according to the specifications in the Request object.
  • getWeightingModel now uses WeightingModelFactory.

People

Dates

  • Created:
    15/Oct/09 7:57 PM
    Updated:
    05/Apr/11 11:41 AM
    Resolved:
    25/Mar/11 2:22 PM