Uploaded image for project: 'Terrier Core'
  1. Terrier Core
  2. TR-154

Default result set size for TRECResultMatching

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.5
    • Component/s: .matching
    • Labels:
      None

      Description

      TRECResultMatching bypasses normal matching by "retrieving" directly from a TREC run (as opposed to the entire collection). However, unless an expected result set size is explicitly provided (through trecresults.matching.number.docs), it creates a ResultSet object to hold every document in the collection, which penalises efficiency.

      trecresults.matching.number.docs should have a default value, probably 1000 (the typical TREC run size). If more than this default number of objects is loaded, an exception should be raised.

        Attachments

          Activity

          Hide
          rodrygo Rodrygo L. T. Santos added a comment -

          The version committed for TREC-214 resolves this issue. In particular, the default size is set to 1000. However, no warning is raised if there are more than this amount of results available.

          Show
          rodrygo Rodrygo L. T. Santos added a comment - The version committed for TREC-214 resolves this issue. In particular, the default size is set to 1000. However, no warning is raised if there are more than this amount of results available.
          Hide
          craigm Craig Macdonald added a comment -

          Tagging for 3.1, as TRECResultMatching are moving into CORE for 3.1

          Show
          craigm Craig Macdonald added a comment - Tagging for 3.1, as TRECResultMatching are moving into CORE for 3.1

            People

            • Assignee:
              rodrygo Rodrygo L. T. Santos
              Reporter:
              rodrygo Rodrygo L. T. Santos
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: