Built and tested src zip and tar all tests passed
Ran through several options for each classification and clustering
example script in pseudo-cluster mode using the src tar build without
any unexpected incident.
Tested the shell in pseudo-cluster mode.
+1 (binding)
On 08/04/2015 12:23 AM, Suneel Marthi wrote:
> Built and Tested {src} * {zip,tar} and all tests pass
>
> +1 (binding)
>
> On Tue, Aug 4, 2015 at 12:03 AM, Andrew Musselman <
> [email protected]> wrote:
>
>> Looks good on EMR with the 3.8 AMI, which contains Amazon's Hadoop 2.4-v5
>> and Spark 1.3.1.
>>
>> All examples that worked in the 0.10 release still work, with breakage
>> happening on the cluster-reuters option 1, like last time, which is still
>> not a blocker in my view. Need to lose the random forest stuff in 11.1
>> (recorded in https://issues.apache.org/jira/browse/MAHOUT-1759).
>>
>> +1 binding
>>
>> On Mon, Aug 3, 2015 at 11:35 AM, Andrew Musselman <
>> [email protected]> wrote:
>>
>>> Getting this error running classify-20newsgroups.sh #3 in distributed
>> mode:
>>> 15/08/03 18:27:09 INFO rdd.SequenceFileRDDFunctions: Saving as sequence
>>> file of type (IntWritable,VectorWritable)
>>> Exception in thread "main" java.lang.RuntimeException:
>>> java.lang.RuntimeException: java.lang.ClassNotFoundException: Class
>>> org.apache.hadoop.mapred.DirectFileOutputCommitter not found
>>> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:1927)
>>> at org.apache.hadoop.mapred.JobConf.getOutputCommitter(JobConf.java:722)
>>> at
>>>
>> org.apache.spark.rdd.PairRDDFunctions.saveAsHadoopFile(PairRDDFunctions.scala:948)
>>> at
>>>
>> org.apache.spark.rdd.SequenceFileRDDFunctions.saveAsSequenceFile(SequenceFileRDDFunctions.scala:103)
>>> at
>>>
>> org.apache.mahout.sparkbindings.drm.CheckpointedDrmSpark.dfsWrite(CheckpointedDrmSpark.scala:163)
>>> at
>>>
>> org.apache.mahout.classifier.naivebayes.NBModel.dfsWrite(NBModel.scala:105)
>>> at
>>> org.apache.mahout.drivers.TrainNBDriver$.process(TrainNBDriver.scala:107)
>>> at
>>>
>> org.apache.mahout.drivers.TrainNBDriver$$anonfun$main$1.apply(TrainNBDriver.scala:77)
>>> at
>>>
>> org.apache.mahout.drivers.TrainNBDriver$$anonfun$main$1.apply(TrainNBDriver.scala:75)
>>> at scala.Option.map(Option.scala:145)
>>> at org.apache.mahout.drivers.TrainNBDriver$.main(TrainNBDriver.scala:75)
>>> at org.apache.mahout.drivers.TrainNBDriver.main(TrainNBDriver.scala)
>>> Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException:
>>> Class org.apache.hadoop.mapred.DirectFileOutputCommitter not found
>>> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:1895)
>>> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:1919)
>>> ... 11 more
>>> Caused by: java.lang.ClassNotFoundException: Class
>>> org.apache.hadoop.mapred.DirectFileOutputCommitter not found
>>> at
>>>
>> org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:1801)
>>> at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:1893)
>>> ... 12 more
>>>
>>>
>>> On Mon, Aug 3, 2015 at 7:31 AM, Stevo Slavić <[email protected]> wrote:
>>>
>>>> Sorry for confusion, I thought it was for all artifacts. Suneel
>> clarified,
>>>> it was just about not-merged change for distribution archives from
>> 0.10.x
>>>> to 0.11.x/master branch. Will verify releases and cast my vote later
>>>> today.
>>>>
>>>> Kind regards,
>>>> Stevo Slavic.
>>>>
>>>> On Mon, Aug 3, 2015 at 4:26 PM, Pat Ferrel <[email protected]>
>> wrote:
>>>>> Is this Apache wide? It’s silly if not. We shouldn’t make this
>> decision
>>>> in
>>>>> a vacuum. Seems like the defacto standard is not to include “Apache"
>> in
>>>> the
>>>>> artifact, I can’t think of anyone else who does.
>>>>>
>>>>> On Aug 3, 2015, at 3:29 AM, Suneel Marthi <[email protected]>
>>>> wrote:
>>>>> We made that change on 0.10.x branch but was not merged in master,
>>>> that's
>>>>> all that was there to be done.
>>>>>
>>>>> Otherwise I agree with what u r saying.
>>>>>
>>>>> Sent from my iPhone
>>>>>
>>>>>> On Aug 3, 2015, at 4:48 AM, Stevo Slavić <[email protected]> wrote:
>>>>>>
>>>>>> This keeps coming up often in recent releases, and I keep referring
>> to
>>>>>> https://issues.apache.org/jira/browse/MAHOUT-1680 where it was
>>>> decided
>>>>> only
>>>>>> to have distribution artifact/acrhive have "apache" prefix. Did
>>>> something
>>>>>> change since then?
>>>>>>
>>>>>> None of the Apache projects, java libraries, that I use, have apache
>>>>> prefix
>>>>>> in their artifact name. It's though part of their groupId.
>>>>>>
>>>>>> If artifactId changes, people depending transitively and directly to
>>>>> Mahout
>>>>>> modules might get classpath issues - same class, two different
>>>>>> versions/APIs, and depending on class loader different one may be
>>>> loaded
>>>>> in
>>>>>> different context, or even fail to load.
>>>>>>
>>>>>> Kind regards,
>>>>>> Stevo Slavic.
>>>>>>
>>>>>>> On Mon, Aug 3, 2015 at 7:01 AM, Suneel Marthi <[email protected]>
>>>>> wrote:
>>>>>>> Rolling back this release, there's a discrepancy in the artifact
>>>> naming
>>>>>>> that needs to be addressed; will send an update when a new Release
>>>>>>> candidate is available.
>>>>>>>
>>>>>>>> On Sun, Aug 2, 2015 at 7:42 PM, Suneel Marthi <[email protected]
>>>>> wrote:
>>>>>>>> This is the vote for release 0.11.0 of Apache Mahout.
>>>>>>>>
>>>>>>>> The vote will be going for at least 72 hours and will be closed on
>>>>>>>> Wednesday,
>>>>>>>> August 5th, 2015. Please download, test and vote with
>>>>>>>>
>>>>>>>> [ ] +1, accept RC as the official 0.11.0 release of Apache Mahout
>>>>>>>> [ ] +0, I don't care either way,
>>>>>>>> [ ] -1, do not accept RC as the official 0.11.0 release of Apache
>>>>> Mahout,
>>>>>>>> because...
>>>>>>>>
>>>>>>>>
>>>>>>>> Maven staging repo:
>>>>>>>>
>>>>>>>>
>> https://repository.apache.org/content/repositories/orgapachemahout-1012
>>>>>>>> <
>> https://repository.apache.org/content/repositories/orgapachemahout-1012/org/apache/mahout/mahout-distribution/0.11.0/
>>>>>>>> <
>> https://repository.apache.org/content/repositories/orgapachebigtop-1001
>>>>>>>>
>>>>>>>> The git tag to be voted upon is release-0.11.0
>>>>>
>>>
