Uploaded image for project: 'Apache Tez'
  1. Apache Tez
  2. TEZ-690 Tez API Ease of Use
  3. TEZ-857

Split Input/Output interfaces into Framework / User components

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 0.5.0
    • None
    • None

    Description

      Inputs / Outputs have several methods which are not meant for user interaction - initialize(Tez*Context), close(), TEZ-844 is adding another.

      There has been confusion in the past on whether the framework will call close, or whether it's the user's responsibility.

      The framework specific methods and the Processor usable methods can be split into a separate interface. Input/Output writers would need to implement both, Processor writers would only see the Input part of the interface.

      TEZ-782, TEZ-827 introduced some requirements on Inputs which are not enforced at compile time (must request mem). These could potentially be added to the framework part of the interface to force Inputs/Outputs to be aware of them at compile time, while not polluting the Processor interface.

      Attachments

        1. TEZ-857.2.txt
          36 kB
          Siddharth Seth
        2. TEZ-857.1.txt
          36 kB
          Siddharth Seth

        Activity

          People

            sseth Siddharth Seth
            sseth Siddharth Seth
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: