<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: Central management of connection strings - Sqoop - HDP in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Central-management-of-connection-strings-Sqoop-HDP/m-p/348255#M235348</link>
    <description>&lt;P&gt;As far as I know this is not something that Ambari or SQOOP allow for.&lt;/P&gt;&lt;P&gt;What you could do to achieve your goal is one of the two:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Prepare sh scripts and refer to your jdbc string as a variable&lt;/LI&gt;&lt;LI&gt;Prepare an Oozie Worklfow and pass the jdbc string as a variable&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;At that point you might have an external tool (e.g. Jenkins) maintaining a list of jdbc strings and taking the responsibility to specify the desidred one.&lt;/P&gt;&lt;P&gt;In solution 1, Jenkins should SSH to the node, set the variable to the JDBC string, launch the sh.&lt;/P&gt;&lt;P&gt;In solution 2, Jenkins should use Oozie API to start the workflow while specifying the desired variable value.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Solution 2 is much better than 1, since it relies on a distributed, highly available service (Oozie).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;</description>
    <pubDate>Wed, 20 Jul 2022 15:25:37 GMT</pubDate>
    <dc:creator>amallegni</dc:creator>
    <dc:date>2022-07-20T15:25:37Z</dc:date>
  </channel>
</rss>

