Sqoop
  1. Sqoop
  2. SQOOP-469

Can we fire the trigger in SQL Server after exporting the data from HIVE using SQOOP

    Details

    • Type: New Feature New Feature
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 1.3.0
    • Fix Version/s: None
    • Component/s: connectors/sqlserver
    • Labels:
    • Environment:

      Operating System - Ubuntu-11.10
      Softwares Used - Sqoop, Hive, Hadoop, (SQL Server in Window 7)

      Description

      I have implemented some task in Hive and wanted to export a table from Hive into SQL Server using SQOOP.
      When table gets exported from Hive to SQL Server, I want to fire the trigger in SQL Server.
      Is it possible to fire the trigger in SQL Server?

        Activity

        Hide
        Abhijeet Gaikwad added a comment -

        This is not related to SQOOP. You will have to write a trigger in SQL Server which will execute when you perform any of the desired operations (INSERT/UPDATE query in this scenario). Let me know if that answers your question.

        Show
        Abhijeet Gaikwad added a comment - This is not related to SQOOP. You will have to write a trigger in SQL Server which will execute when you perform any of the desired operations (INSERT/UPDATE query in this scenario). Let me know if that answers your question.
        Hide
        Jarek Jarcec Cecho added a comment -

        Actually I also do have a need to execute some code (stored procedure) on database side before and after each sqoop import.

        I'm currently doing that by additional actions in my oozie workflow that is driving the import. It might be beneficial to put something like "callbacks" into sqoop that user could use to execute arbitrary code as he needs at given points (for example "before import", "after import").

        Jarcec

        Show
        Jarek Jarcec Cecho added a comment - Actually I also do have a need to execute some code (stored procedure) on database side before and after each sqoop import. I'm currently doing that by additional actions in my oozie workflow that is driving the import. It might be beneficial to put something like "callbacks" into sqoop that user could use to execute arbitrary code as he needs at given points (for example "before import", "after import"). Jarcec

          People

          • Assignee:
            Unassigned
            Reporter:
            Bhavesh Shah
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Time Tracking

              Estimated:
              Original Estimate - 168h
              168h
              Remaining:
              Remaining Estimate - 168h
              168h
              Logged:
              Time Spent - Not Specified
              Not Specified

                Development