Terrier Core

StructureMerger: new termids for terms only in 2nd lexicon are not used

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Trivial Trivial
  • Resolution: Fixed
  • Affects Version/s: 3.0
  • Fix Version/s: 3.0
  • Component/s: .structures
  • Description:
    Hide

    In the StructureMerger, new termids have to be assigned for terms that only occur in the 2nd source index. These are assigned as termids greater than the number of terms in the first partition. However, an improved unit test has shown that these are not being used. I.e. largestTermId != NUMBER_UNIQUE_TERMS -1
    Show
    In the StructureMerger, new termids have to be assigned for terms that only occur in the 2nd source index. These are assigned as termids greater than the number of terms in the first partition. However, an improved unit test has shown that these are not being used. I.e. largestTermId != NUMBER_UNIQUE_TERMS -1

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Craig Macdonald added a comment - 10/Mar/10 12:48 PM

Fix is trivial, lee2.getValue().setTermId(newCode); wss missing.

Show
Craig Macdonald added a comment - 10/Mar/10 12:48 PM Fix is trivial, lee2.getValue().setTermId(newCode); wss missing.

People

Dates

  • Created:
    10/Mar/10 12:47 PM
    Updated:
    10/Mar/10 12:48 PM
    Resolved:
    10/Mar/10 12:48 PM
Atlassian JIRA (v4.1#519) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Univ of Glasgow. Try JIRA - bug tracking software for your team.