Uploaded image for project: 'Sqoop (Retired)'
  1. Sqoop (Retired)
  2. SQOOP-652

Improve error message generated in DataDrivenDBInputFormat when no splitter is available

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Trivial
    • Resolution: Fixed
    • 1.4.2
    • 1.4.3
    • None

    Description

      Currently DataDrivenDBInputFormat will throw following exception in case that there is no available Splitter:

      DBSplitter splitter = getSplitter(sqlDataType);
      if (null == splitter) {
        throw new IOException("Unknown SQL data type: " + sqlDataType);
      }
      

      Text of the exception is very confusing as it's not describing what has actually happened. Would be great if this message would be improved by saying that Sqoop do not have splitter for given sql type and therefore user should either use different split column (argument --split-by) or lower number of mappers to 1 (splitters are not used in such case).

      Attachments

        1. DataDrivenDBInputFormat.patch
          0.8 kB
          Linden Hillenbrand

        Activity

          People

            lhillenbrand Linden Hillenbrand
            jarcec Jarek Jarcec Cecho
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: