Edward Capriolo 2013-09-12, 14:19
Sanjay Subramanian 2013-09-12, 17:52
-Re: Interesting claims that seem untrue
Dean Wampler 2013-09-12, 20:42
I'd be more impressed with who's deleted the most lines of code...
On Thu, Sep 12, 2013 at 11:52 AM, Sanjay Subramanian <
[EMAIL PROTECTED]> wrote:
> I have not read the full blogs but in the year 2013 , IMHO , LOC is a
> very old metric that defines good software any more...
> From: Edward Capriolo <[EMAIL PROTECTED]>
> Reply-To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> Date: Thursday, September 12, 2013 7:19 AM
> To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>, "<
> [EMAIL PROTECTED]>" <[EMAIL PROTECTED]>
> Subject: Interesting claims that seem untrue
> I was reading the horton-works blog and found an interesting article.
> There is a very interesting graphic which attempts to demonstrate lines
> of code in the 12 release.
> Although I do not know how they are calculated, they are probably
> counting code generated by tests output, but besides that they are wrong.
> One claim is that Cloudera contributed 4,244 lines of code.
> So to debunk that claim:
> In https://issues.apache.org/jira/browse/HIVE-4675 Brock Noland from
> cloudera, created the ptest2 testing framework. He did all the work for
> ptest2 in hive 12, and it is clearly more then 4,244
> This consists of 84 java files
> [edward@desksandra ptest2]$ find . -name "*.java" | wc -l
> and by itself is 8001 lines of code.
> [edward@desksandra ptest2]$ find . -name "*.java" | xargs cat | wc -l
> [edward@desksandra hive-trunk]$ wc -l HIVE-4675.patch
> 7902 HIVE-4675.patch
> This is not the only feature from cloudera in hive 12.
> There is also a section of the article that talks of a "ROAD MAP" for
> hive features. I did not know we (hive) had a road map. I have advocated
> switching to feature based release and having a road map before, but it was
> suggested that might limit people from itch-scratching.
> CONFIDENTIALITY NOTICE
> =====================> This email message and any attachments are for the exclusive use of the
> intended recipient(s) and may contain confidential and privileged
> information. Any unauthorized review, use, disclosure or distribution is
> prohibited. If you are not the intended recipient, please contact the
> sender by reply email and destroy all copies of the original message along
> with any attachments, from your computer system. If you are the intended
> recipient, please be advised that the content of this message is subject to
> access, review and disclosure by the sender's Email System Administrator.
Dean Wampler, Ph.D.
Navis류승우 2013-09-13, 01:09
Carl Steinbach 2013-09-16, 05:34
Carter Shanklin 2013-09-16, 20:58
Konstantin Boudnik 2013-09-17, 17:57
Edward Capriolo 2013-09-17, 19:15
Lefty Leverenz 2013-09-17, 20:22