| @daviottenheimer | +1-415-271-6259
blog: http://www.flyingpenguin.com/
-Original Message-
From: shaposh...@gmail.com [mailto:shaposh...@gmail.com] On Behalf
Of
Roman Shaposhnik
Sent: Monday, August 26, 2013 10:50 AM
To: common-dev@hadoop.apache.org
Subject: Re: Coverity Scan (MAPREDUCE-5032
: Ottenheimer, Davi [mailto:davi.ottenhei...@emc.com]
Sent: Monday, August 26, 2013 1:11 PM
To: common-dev@hadoop.apache.org
Subject: RE: Coverity Scan (MAPREDUCE-5032)
Perhaps open the JIRA with only a reference/link to the Coverity report,
and
limit access to only those working on the issues
I've been working with DataStax on their use of Coverity with Cassandra, and
decided to give the Hadoop 1.2.1 source tarball a run through our analyzer. I
found some interesting issues, and noticed that some of them are integer
overflow defects that align with the open MAPREDUCE-5032 issue.
On Mon, Aug 26, 2013 at 8:21 AM, Jon Jarboe jjar...@coverity.com wrote:
I've been working with DataStax on their use of Coverity with Cassandra, and
decided to give the Hadoop 1.2.1 source tarball a run through our analyzer.
I found some interesting issues, and noticed that some of them are
Can you file a JIRA and attach the report there? That is the best way to move
this forward.
Thanks,
+Vinod Kumar Vavilapalli
On Aug 26, 2013, at 8:21 AM, Jon Jarboe wrote:
I've been working with DataStax on their use of Coverity with Cassandra, and
decided to give the Hadoop 1.2.1 source
On Mon, Aug 26, 2013 at 10:43 AM, Vinod Kumar Vavilapalli
vino...@apache.org wrote:
Can you file a JIRA and attach the report there? That is the best way to move
this forward.
Last time I was involved in a Coverity scan was when they scanned another
project I'm committer on (FFmpeg). The
blog: http://www.flyingpenguin.com/
-Original Message-
From: shaposh...@gmail.com [mailto:shaposh...@gmail.com] On Behalf Of
Roman Shaposhnik
Sent: Monday, August 26, 2013 10:50 AM
To: common-dev@hadoop.apache.org
Subject: Re: Coverity Scan (MAPREDUCE-5032)
On Mon, Aug 26, 2013
them into a single JIRA anyway.
Jon
(214) 531-3496
-Original Message-
From: shaposh...@gmail.com [mailto:shaposh...@gmail.com] On Behalf Of
Roman Shaposhnik
Sent: Monday, August 26, 2013 12:50 PM
To: common-dev@hadoop.apache.org
Subject: Re: Coverity Scan (MAPREDUCE-5032)
On Mon
: Coverity Scan (MAPREDUCE-5032)
Perhaps open the JIRA with only a reference/link to the Coverity report, and
limit access to only those working on the issues.
Full disclosure, update the JIRA, after fix.
--
Davi Ottenheimer
Senior Director of Trust
EMC Corporation
davi.ottenhei...@emc.com
