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

Export parquet files to RDBMS: don't require .metadata for parquet files

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Won't Fix
    • 1.4.6
    • None
    • metastore

    • sqoop 1.4.6
      export parquet files to Oracle

    Description

      Kite currently requires .metadata.
      Parquet files have their own metadata stored along data files.
      It would be great for Export operation on parquet files to RDBMS not to require .metadata.
      We have most of the files created by Spark and Hive, and they don't create .metadata, it only Kite that does.
      It makes sqoop export of parquet files usability very limited.

      Attachments

        1. SQOOP-2907.patch
          21 kB
          ChenKai
        2. SQOOP-2907.patch1
          12 kB
          Zac Zhou
        3. SQOOP-2907.patch2
          13 kB
          Zac Zhou
        4. SQOOP-2907-3.patch
          13 kB
          Zac Zhou

        Issue Links

          is superceded by

          Improvement - An improvement or enhancement to an existing feature or task. SQOOP-3313 Remove Kite dependency

          • Major - Major loss of function.
          • Resolved
          relates to

          Sub-task - The sub-task of the issue SQOOP-1394 Export data from HDFS back to an RDMS

          • Major - Major loss of function.
          • Closed
          links to

          Web Link KITE-1121

          Web Link review board

          Activity

            People

              sanysandish@gmail.com Sandish Kumar HN
              Tagar Ruslan Dautkhanov
              Votes:
              3 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Slack

                  Issue deployment