[MAHOUT-1911] Fix Create Mahout Context after VCL Merge

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 0.13.0
• Epic Link: Native Integration
• Sprint: 0.14.0 Release
• Assignee: Andrew Palumbo
• Reporter: Andrew Palumbo
• Created: 26/Jan/17 02:49
• Updated: 04/Mar/18 02:43
• Resolved: 02/Feb/17 23:12

Description

While the VCL bindings were under development I commented out a large section of getMahoutContext() in SparkBindings/package.scala

This code has been changed slightly so need to make sure it is replaced and working after rebasing and merging VCL.

I.e.:

   // context specific jars
        val mcjars = findMahoutContextJars(closeables)

        if (log.isDebugEnabled) {
          log.debug("Mahout jars:")
          mcjars.foreach(j => log.debug(j))
        }

        sparkConf.setJars(jars = mcjars.toSeq ++ customJars)
        if (!(customJars.size > 0)) sparkConf.setJars(customJars.toSeq)

      } else {
        // In local mode we don't care about jars, do we?
        sparkConf.setJars(customJars.toSeq

Issue Links

• is superceded by: MAHOUT-1934 OpenMP jars aren't being picked up in distributed Spark