You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by GitBox <gi...@apache.org> on 2020/12/22 08:24:26 UTC

[GitHub] [incubator-dolphinscheduler] masterable opened a new issue #4287: [Sub-Task][Service] The sqoop workflow adds a new target path for hive table creation

masterable opened a new issue #4287:
URL: https://github.com/apache/incubator-dolphinscheduler/issues/4287


   ***For** better global communication, please give priority to using English description, thx! *
   
   *Please review https://dolphinscheduler.apache.org/en-us/docs/development/issue.html when describe an issue.*
   
   **Describe the question**
   When we use sqoop to import data to hive, after choosing the  create new table configuration, can we provide a configuration item that specifies the storage location of the new table?
   Simply put, I want to specify the path of the create new table in the sqoop workflow, can we provide this configuration item?
   Thanks.
   
   **What are the current deficiencies and the benefits of improvement**
   - A clear and concise description of the current deficiencies and the benefits of this improvement.
   - Now that the table-to-table data synchronization is selected, can we specify the path of the new table to let the user omit the process of creating a new table in **hive**?
   - benefits :1. Allows users to more easily specify the storage location to create a new table  2. Omit the user's table creation process and time in hive  3. Increase user usage frequency and product adhesion
   
   **Which version of DolphinScheduler:**
    -[1.3.3-preview]
   
   **Describe alternatives you've considered**
   A clear and concise description of any alternative improvement solutions you've considered.
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org