Uploaded image for project: 'Sqoop (READ-ONLY)'
  1. Sqoop (READ-ONLY)
  2. SQOOP-190

Sqoop shouldn't use generated SqoopRecord.toString in text output cases.

          Details

          • Type: New Feature
          • Status: Open
          • Priority: Major
          • Resolution: Unresolved
          • Affects Version/s: 1.2.0
          • Fix Version/s: None
          • Component/s: None
          • Labels:
            None

            Description

            SqoopRecords uses the a generated toString to convert a SqoopRecord to a line of text suitable for the TextimportMapper. This then forces delimiting and other reformatting transformations to be injected into generated code.

            From a design perspective, it seems that treating the SqoopRecord as merely a data container with regards to the toString method, it would be easier to extend and test when handling other potential output text formatting features.

              Attachments

                Issue Links

                relates to

                Improvement - An improvement or enhancement to an existing feature or task. SQOOP-129 Newlines in RDBMS Fields Break Hive

                • Major - Major loss of function.
                • Resolved

                Improvement - An improvement or enhancement to an existing feature or task. SQOOP-187 Generated records should allow toString() that does not append end-of-record delimiter

                • Major - Major loss of function.
                • Resolved

                  Activity

                    People

                    • Assignee:
                      Unassigned
                      Reporter:
                      jon Jonathan Hsieh
                    • Votes:
                      0 Vote for this issue
                      Watchers:
                      1 Start watching this issue

                      Dates

                      • Created:
                        Updated: