[
https://issues.apache.org/jira/browse/SQOOP-2318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14506279#comment-14506279
]
Jarek Jarcec Cecho commented on SQOOP-2318:
-------------------------------------------
I believe that we're getting the {{/etc/hadoop/conf}} directory from [default
configuration
file|https://github.com/apache/sqoop/blob/sqoop2/dist/src/main/server/conf/sqoop.properties#L137]
which seems reasonable for released artifacts, but might not be that
reasonable for local build. Perhaps we might want to add a profile or something
that will copy in different configuration file to solve the problem of forcing
users to create the empty configuration directory?
> Use hadoop configuration defaults for MapReduceSubmissionEngine
> ---------------------------------------------------------------
>
> Key: SQOOP-2318
> URL: https://issues.apache.org/jira/browse/SQOOP-2318
> Project: Sqoop
> Issue Type: Bug
> Components: sqoop2-framework
> Reporter: Szehon Ho
> Assignee: Szehon Ho
> Attachments: SQOOP-2318.patch
>
>
> Found this while trying to run a local job runner out of the box for
> development testing.
> The MapReduceSubmissionEngine looks in /etc/hadoop/conf for hadoop
> configurations. When trying to run a local job runner without an actual
> hadoop install, this forces the user to create an /etc/hadoop/conf directory,
> and then put a lot of configs in there to get local job runner to work.
> Proposing a change to use hadoop defaults (comes with Hadoop Configuration
> object), which will make local job runner work out of the box. Though, empty
> /etc/hadoop/conf directory still needs to be created.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
