[
https://issues.apache.org/jira/browse/MAPREDUCE-750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Douglas updated MAPREDUCE-750:
------------------------------------
Status: Open (was: Patch Available)
bq. I should point out - I'm all for not cluttering up the mapred-, hdfs- and
core-\* config files with extraneous parameters. Is there a better place to put
this? Can/should we have a contrib-default and contrib-site? (Or, inevitably,
per-contrib-module config files?)
There are plenty of counterexamples- the contrib schedulers have taken plenty
of liberties, here- but contrib modules shouldn't add to the core config. If
required, please add a per-module conf dir (e.g. hdfsproxy).
> Extensible ConnManager factory API
> ----------------------------------
>
> Key: MAPREDUCE-750
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-750
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: contrib/sqoop
> Reporter: Aaron Kimball
> Assignee: Aaron Kimball
> Attachments: MAPREDUCE-750.patch
>
>
> Sqoop uses the ConnFactory class to instantiate a ConnManager implementation
> based on the connect string and other arguments supplied by the user. This
> allows per-database logic to be encapsulated in different ConnManager
> instances, and dynamically chosen based on which database the user is
> actually importing from. But adding new ConnManager implementations requires
> modifying the source of a common ConnFactory class. An indirection layer
> should be used to delegate instantiation to a number of factory
> implementations which can be specified in the static configuration or at
> runtime.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
