Pig
  1. Pig
  2. PIG-1033

javac warnings: deprecated hadoop APIs

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.4.0
    • Fix Version/s: 0.6.0
    • Component/s: impl
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      Description

      Suppress javac warnings related to deprecated hadoop APIs.

        Issue Links

          Activity

          Hide
          Daniel Dai added a comment -

          Not sure if this blanket suppression of deprecation javac warnings is good. See the same discussion on MAPREDUCE side, link to it for reference.

          Show
          Daniel Dai added a comment - Not sure if this blanket suppression of deprecation javac warnings is good. See the same discussion on MAPREDUCE side, link to it for reference.
          Hide
          Daniel Dai added a comment -

          Patch committed.

          Show
          Daniel Dai added a comment - Patch committed.
          Hide
          Olga Natkovich added a comment -

          +1

          Show
          Olga Natkovich added a comment - +1
          Hide
          Olga Natkovich added a comment -

          I think it is ok to go with the option 1 for now with the understanding that we clean things up as part of the transition to Hadoop 21

          Show
          Olga Natkovich added a comment - I think it is ok to go with the option 1 for now with the understanding that we clean things up as part of the transition to Hadoop 21
          Hide
          Daniel Dai added a comment -

          We have options:
          1. Change build.xml to disable deprecation warnings. BTW, hadoop does not check for deprecation when compiling
          2. Using @SuppressWarnings("deprecation") to suppress specific blocks. The problem is we cannot suppress import block, all import warnings still there
          3. Using @SuppressWarnings("deprecation") and do not import deprecate class. Use full qualified class name for deprecate class when using it. The downside is patch is relatively lengthy.

          Show
          Daniel Dai added a comment - We have options: 1. Change build.xml to disable deprecation warnings. BTW, hadoop does not check for deprecation when compiling 2. Using @SuppressWarnings("deprecation") to suppress specific blocks. The problem is we cannot suppress import block, all import warnings still there 3. Using @SuppressWarnings("deprecation") and do not import deprecate class. Use full qualified class name for deprecate class when using it. The downside is patch is relatively lengthy.

            People

            • Assignee:
              Daniel Dai
              Reporter:
              Daniel Dai
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development