[
https://issues.apache.org/jira/browse/GIRAPH-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maja Kabiljo updated GIRAPH-315:
--------------------------------
Description:
While running some tests I noticed that on the master I get different values of
some configuration parameters in the beginning of the execution than later on.
It turned out that giraph-site.xml gets added as default resource a bit later
than it should.
This only happens when running tests.
was:While running some tests I noticed that on the master I get different
values of some configuration parameters in the beginning of the execution than
later on. It turned out that giraph-site.xml gets added as default resource a
bit later than it should.
Priority: Trivial (was: Major)
Yes, since it only happens when running tests (benchmarks are good as it is)
it's not a big deal. I am leaving it open but decreasing its priority (is that
the right thing to do?)
> giraph-site.xml isn't read on time
> ----------------------------------
>
> Key: GIRAPH-315
> URL: https://issues.apache.org/jira/browse/GIRAPH-315
> Project: Giraph
> Issue Type: Bug
> Reporter: Maja Kabiljo
> Assignee: Maja Kabiljo
> Priority: Trivial
> Attachments: GIRAPH-315.patch
>
>
> While running some tests I noticed that on the master I get different values
> of some configuration parameters in the beginning of the execution than later
> on. It turned out that giraph-site.xml gets added as default resource a bit
> later than it should.
> This only happens when running tests.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
