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

MySQL fetch-size behavior changed with SQOOP-1400

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • 1.4.6
    • 1.4.6
    • connectors/mysql
    • None

    Description

      SQOOP-1400 changed the default behavior for the connector to load everything in memory. The only working way to get the old streaming back is to use --fetch-size -2147483648 (Integer.MIN_VALUE)

      It would be nice if that could be changed and/or documented that mysql does not support a fetch size and does only support row-by-row or loading everything in memory.

      The issue is discussed for example here:

      http://community.cloudera.com/t5/Data-Ingestion-Integration/Sqoop-GC-overhead-limit-exceeded-after-CDH5-2-update/td-p/20604

      Attachments

        1. SQOOP-1617.patch
          1 kB
          Jarek Jarcec Cecho

        Issue Links

          Activity

            People

              jarcec Jarek Jarcec Cecho
              juergen_thomann J├╝rgen Thomann
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: