[ 
https://issues.apache.org/jira/browse/GIRAPH-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16496937#comment-16496937
 ] 

Hudson commented on GIRAPH-299:
-------------------------------

SUCCESS: Integrated in Jenkins build Giraph-trunk-Commit #1752 (See 
[https://builds.apache.org/job/Giraph-trunk-Commit/1752/])
GIRAPH-299 (dionysios: 
[http://git-wip-us.apache.org/repos/asf?p=giraph.git&a=commit&h=505c98d9a807d92640e6a2ac8fba410a700d4d58])
* (edit) 
giraph-core/src/main/java/org/apache/giraph/master/BspServiceMaster.java


> Remove unused field in BspServiceMaster
> ---------------------------------------
>
>                 Key: GIRAPH-299
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-299
>             Project: Giraph
>          Issue Type: Improvement
>          Components: graph
>    Affects Versions: 1.0.0
>            Reporter: Eli Reisman
>            Assignee: Dionysios Logothetis
>            Priority: Trivial
>              Labels: newbie
>             Fix For: 1.0.0
>
>         Attachments: GIRAPH-299-2.patch, GIRAPH-299-3.patch, GIRAPH-299.patch
>
>
> GIRAPH-275 was a victim of this weekend's outage of the JIRA site. When I 
> rebased the patch, I did it from a version that was not the last one I 
> uploaded before said outage. 
> When I rebased the patch today, my most current version was not available to 
> work from. So I forgot to perform the last fix it needed: to take the 
> "localityLimit" constant on line 138 (used on line 536) of 
> BspServiceMaster.java and make it static, and to change the name to 
> LOCALITY_LIMIT to match proper convention.
> For those that already know how to create and upload a patch, please let this 
> wait, its a perfect chance for someone new to submitting patches (and to 
> Giraph) to test drive the process. Thanks!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to