hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Joseph Evans (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-8573) Configuration tries to read from an inputstream resource multiple times.
Date Fri, 06 Jul 2012 16:04:35 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-8573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robert Joseph Evans updated HADOOP-8573:
----------------------------------------

    Status: Patch Available  (was: Open)

I forgot to add in that this patch feels like a hack to me, with loadResource returning the
properties to be added in, but I could not think of a cleaner way to do it without completely
refactoring a lot of that code.  If someone else has a better way to do this I would be very
happy to switch.
                
> Configuration tries to read from an inputstream resource multiple times. 
> -------------------------------------------------------------------------
>
>                 Key: HADOOP-8573
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8573
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: conf
>    Affects Versions: 1.0.2, 0.23.3, 2.0.1-alpha, 3.0.0
>            Reporter: Robert Joseph Evans
>            Assignee: Robert Joseph Evans
>         Attachments: HADOOP-8573.txt
>
>
> If someone calls Configuration.addResource(InputStream) and then reloadConfiguration
is called for any reason, Configruation will try to reread the contents of the InputStream,
after it has already closed it.
> This never showed up in 1.0 because the framework itself does not call addResource with
an InputStream, and typically by the time user code starts running that might call this, all
of the default and site resources have already been loaded.
> In 0.23 mapreduce is now a client library, and mapred-site.xml and mapred-default.xml
are loaded much later in the process.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message