According to me, the first line is redundant (checking for future.isDone()). future.get() will alone serve the purpose. The snippet of code that I had attached was from the latest revision of mahout. -- View this message in context: http://lucene.472066.n3.nabble.com/Possible-multi-thread-issue-in-AbstractDifferenceRecommenderEvaluator-tp1571411p1571781.html Sent from the Mahout User List mailing list archive at Nabble.com.
- Possible multi thread issue in AbstractDifferenceRecommende... Stanley Ipkiss
- Re: Possible multi thread issue in AbstractDifferenceR... Stanley Ipkiss
- Re: Possible multi thread issue in AbstractDiffere... Ted Dunning
- Re: Possible multi thread issue in AbstractDif... Stanley Ipkiss
- Re: Possible multi thread issue in Abstrac... Ted Dunning
- Re: Possible multi thread issue in AbstractDifferenceR... Sean Owen
- Re: Possible multi thread issue in AbstractDiffere... Sean Owen
- Re: Possible multi thread issue in AbstractDiffere... Ted Dunning
- Re: Possible multi thread issue in AbstractDif... Sean Owen
- Re: Possible multi thread issue in Abstrac... Stanley Ipkiss
- Re: Possible multi thread issue in Ab... Ted Dunning
- Re: Possible multi thread issue i... Stanley Ipkiss
- Re: Possible multi thread iss... Sean Owen
- Re: Possible multi thread iss... Stanley Ipkiss
