Re: [VOTE] introduce Python as build-time and run-time dependency for Hadoop and throughout Hadoop stack
+1, +1, +1 (non-binding) On Sat, Nov 24, 2012 at 12:13 PM, Matt Foley wrote: > For discussion, please see previous thread "[PROPOSAL] introduce Python as > build-time and run-time dependency for Hadoop and throughout Hadoop stack". > > This vote consists of three separate items: > > 1. Contributors shall be allowed to use Python as a platform-independent > scripting language for build-time tasks, and add Python as a build-time > dependency. > Please vote +1, 0, -1. > > 2. Contributors shall be encouraged to use Maven tasks in combination with > either plug-ins or Groovy scripts to do cross-platform build-time tasks, > even under ant in Hadoop-1. > Please vote +1, 0, -1. > > 3. Contributors shall be allowed to use Python as a platform-independent > scripting language for run-time tasks, and add Python as a run-time > dependency. > Please vote +1, 0, -1. > > Note that voting -1 on #1 and +1 on #2 essentially REQUIRES contributors to > use Maven plug-ins or Groovy as the only means of cross-platform build-time > tasks, or to simply continue using platform-dependent scripts as is being > done today. > > Vote closes at 12:30pm PST on Saturday 1 December. > - > Personally, my vote is +1, +1, +1. > I think #2 is preferable to #1, but still has many unknowns in it, and > until those are worked out I don't want to delay moving to cross-platform > scripts for build-time tasks. > > Best regards, > --Matt >
Re: [PROPOSAL] introduce Python as build-time and run-time dependency for Hadoop and throughout Hadoop stack
If we decide to go with Maven then there's no point to complicate the picture with jython. This time I will keep the offensive about *yton to myself ;) Cos On Sat, Nov 24, 2012 at 10:26PM, Radim Kolar wrote: > we have not discussed advantages of stand alone python vs > jython-in-maven pom > > http://code.google.com/p/jy-maven-plugin/ > > language is about same, and it does not needs to have installed, > which is advantage on windows.
[jira] [Created] (HADOOP-9088) Add Murmur3 hash
Radim Kolar created HADOOP-9088: --- Summary: Add Murmur3 hash Key: HADOOP-9088 URL: https://issues.apache.org/jira/browse/HADOOP-9088 Project: Hadoop Common Issue Type: Improvement Reporter: Radim Kolar faster and better then murmur2 -- 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
Re: [PROPOSAL] introduce Python as build-time and run-time dependency for Hadoop and throughout Hadoop stack
we have not discussed advantages of stand alone python vs jython-in-maven pom http://code.google.com/p/jy-maven-plugin/ language is about same, and it does not needs to have installed, which is advantage on windows.
Re: [PROPOSAL] introduce Python as build-time and run-time dependency for Hadoop and throughout Hadoop stack
Please see new [VOTE] thread. On Fri, Nov 23, 2012 at 3:40 PM, Radim Kolar wrote: > discussion seems to ended, lets start vote. >
[VOTE] introduce Python as build-time and run-time dependency for Hadoop and throughout Hadoop stack
For discussion, please see previous thread "[PROPOSAL] introduce Python as build-time and run-time dependency for Hadoop and throughout Hadoop stack". This vote consists of three separate items: 1. Contributors shall be allowed to use Python as a platform-independent scripting language for build-time tasks, and add Python as a build-time dependency. Please vote +1, 0, -1. 2. Contributors shall be encouraged to use Maven tasks in combination with either plug-ins or Groovy scripts to do cross-platform build-time tasks, even under ant in Hadoop-1. Please vote +1, 0, -1. 3. Contributors shall be allowed to use Python as a platform-independent scripting language for run-time tasks, and add Python as a run-time dependency. Please vote +1, 0, -1. Note that voting -1 on #1 and +1 on #2 essentially REQUIRES contributors to use Maven plug-ins or Groovy as the only means of cross-platform build-time tasks, or to simply continue using platform-dependent scripts as is being done today. Vote closes at 12:30pm PST on Saturday 1 December. - Personally, my vote is +1, +1, +1. I think #2 is preferable to #1, but still has many unknowns in it, and until those are worked out I don't want to delay moving to cross-platform scripts for build-time tasks. Best regards, --Matt
Re: commit access to hadoop
On 21 November 2012 15:03, Radim Kolar wrote: > what it takes to gain commit access to hadoop? > good question. I've put some of my thoughts on the topic into a presentation I gave last month: http://www.slideshare.net/steve_l/inside-hadoopdev That isn't so much about commit/non-commit status, because it was more focused about getting your code in -which is normally what matters. Even committers have to go through RTC -you don't get any special privileges from commit rights, the task of keeping patches up to date and having to remind others to review it. The main "feature" is that when you get the +1 vote you yourself get to deal with the grunge work of apply patches to one or more svn branches, resyncing that with the git branches you inevitably do your own work on. And it also gives you more responsibilty to review and commit others' works, which is something that some of (I point to myself here) are lax at. I can't help wondering if we need to be a bit more formal about that too, have one day a month "review sundays"(*) where we do go through and review the outstanding works, so they don't fall by the wayside. -steve (*) Yes, a sunday. I know everyone is too busy to dedicate a weekday to this.
