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

Pipeline Query/Doc Policy Lifecycle

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.0
    • Fix Version/s: 3.5
    • Component/s: None
    • Labels:
      None

      Attachments

        Issue Links

          Activity

          Hide
          juanito Giovanni Stilo added a comment - - edited

          Craig,
          thanks i'm:
          University degli Studi dell'Aquila
          and
          Nestor Laboratory - University of Rome "Tor Vergata"

          many many thanks
          GS.

          Show
          juanito Giovanni Stilo added a comment - - edited Craig, thanks i'm: University degli Studi dell'Aquila and Nestor Laboratory - University of Rome "Tor Vergata" many many thanks GS.
          Hide
          craigm Craig Macdonald added a comment - - edited

          Hi Giovanni, Your affiliation is still University of Rome Tor Vergata, right? Need to credit you in the changes documentation.

          Show
          craigm Craig Macdonald added a comment - - edited Hi Giovanni, Your affiliation is still University of Rome Tor Vergata, right? Need to credit you in the changes documentation.
          Hide
          craigm Craig Macdonald added a comment -

          Committed to trunk for version 3.1 release.

          Show
          craigm Craig Macdonald added a comment - Committed to trunk for version 3.1 release.
          Hide
          juanito Giovanni Stilo added a comment -

          Other side of the coin.

          GS

          Show
          juanito Giovanni Stilo added a comment - Other side of the coin. GS
          Hide
          craigm Craig Macdonald added a comment -

          Hi Stilo,

          Thanks for the quick response. My idea with a reset AFTER is that a TermPipeline instance could buffer some terms, and then only let them out once reset() is called. However, you still want them in the same document, so in this respect, reset() is like a flush().

          About the base classes - I already made a Stemmer base class, which encapsulated most of the changes.

          Show
          craigm Craig Macdonald added a comment - Hi Stilo, Thanks for the quick response. My idea with a reset AFTER is that a TermPipeline instance could buffer some terms, and then only let them out once reset() is called. However, you still want them in the same document, so in this respect, reset() is like a flush(). About the base classes - I already made a Stemmer base class, which encapsulated most of the changes.

            People

            • Assignee:
              craigm Craig Macdonald
              Reporter:
              juanito Giovanni Stilo
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: