Uploaded image for project: 'Sqoop'
  1. Sqoop
  2. SQOOP-3074

Fix Avro import not to fail with Javac errors in case of non UTF-8 locale

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.4.7
    • Component/s: None
    • Labels:
      None

      Description

      The current implementation of Sqoop will fail to compile the ClassWriter generated Java class in case of UTF-8 characters are available in the database but the running host don't have UTF-8 or not supporting that.

      Meanwhile we'd like to keep up the support of UTF-8 characters for example in Avro schemas.

      A good example for that TestAvroImport#testNonstandardCharactersInColumnName fails if executed form a shell/env with non UTF-8 locale.

      We have to provide an implementation reflects this.

        Attachments

        1. SQOOP-3074.patch
          3 kB
          Attila Szabo

          Issue Links

            Activity

              People

              • Assignee:
                maugli Attila Szabo
                Reporter:
                maugli Attila Szabo
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: