Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created 12-18-2016 05:37 AM
Created 12-18-2016 10:54 AM
When connecting to a database using JDBC, you can optionally specify extra JDBC parameters via a property file using the option --connection-param-file The contents of this file are parsed as standard Java properties and passed into the driver while creating a connection.
sqoop import --driver some_jdbc_driver --connect <connect-string> --connection-param-file
The parameters specified via the optional property file are only applicable to JDBC connections.
--options-file
Option files can be specified anywhere in the command line as long as the options within them follow the otherwise prescribed rules of options ordering. For instance, regardless of where the options are loaded from, they must follow the ordering such that generic options appear first, tool specific options next, finally followed by options that are intended to be passed to child programs
sqoop --options-file database.props --table <table> --target-dir <target_dir>
//database.props
import
--connect jdbc:mysql://localhost:5432/test_db
--username root
--password password
Created 12-18-2016 10:54 AM
When connecting to a database using JDBC, you can optionally specify extra JDBC parameters via a property file using the option --connection-param-file The contents of this file are parsed as standard Java properties and passed into the driver while creating a connection.
sqoop import --driver some_jdbc_driver --connect <connect-string> --connection-param-file
The parameters specified via the optional property file are only applicable to JDBC connections.
--options-file
Option files can be specified anywhere in the command line as long as the options within them follow the otherwise prescribed rules of options ordering. For instance, regardless of where the options are loaded from, they must follow the ordering such that generic options appear first, tool specific options next, finally followed by options that are intended to be passed to child programs
sqoop --options-file database.props --table <table> --target-dir <target_dir>
//database.props
import
--connect jdbc:mysql://localhost:5432/test_db
--username root
--password password
Created 12-19-2016 05:54 AM
@Rajendra Kalepu could you please spare some time and accept the answer if it clarify your confusion. Thanks