[TR-112] "Term Not Found" log message should not be a warning Created: 06/Apr/10  Updated: 18/Feb/11  Resolved: 18/Feb/11

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

Type: Improvement Priority: Trivial
Reporter: Richard Eckart de Castilho Assignee: Craig Macdonald
Resolution: Fixed  
Labels: None

BaseMatching issues a "Term Not Found" message at WARN level. OldBasicMatching issues the same message at INFO level. I would suggest logging these messages at INFO or even DEBUG level in both cases.

Comment by Craig Macdonald [ 06/Apr/10 ]

What's the case for each?

Here are my opinions:

  • WARN - its normal that terms arent found, so WARN isnt appropriate
  • INFO - is term not found too regular that it warrants an INFO message
  • DEBUG - might be suppressed and could useful to know when lots of terms are not found.

My preference is leaning towards DEBUG.

Comment by Richard Eckart de Castilho [ 06/Apr/10 ]

I follow that argumentation and second DEBUG.

Comment by Craig Macdonald [ 18/Feb/11 ]

Tagging for 3.1

Comment by Craig Macdonald [ 18/Feb/11 ]

Committed to trunk.

Generated at Thu Jul 16 03:41:46 BST 2020 using JIRA 7.1.1#71004-sha1:d6b2c0d9b7051e9fb5e4eb8ce177ca56d91d7bd8.