You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mahout.apache.org by "Andrew Palumbo (JIRA)" <ji...@apache.org> on 2017/01/26 02:50:26 UTC

[jira] [Created] (MAHOUT-1911) Fix Create Mahout Context after VCL Merge

Andrew Palumbo created MAHOUT-1911:
--------------------------------------

             Summary: Fix Create Mahout Context after VCL Merge
                 Key: MAHOUT-1911
                 URL: https://issues.apache.org/jira/browse/MAHOUT-1911
             Project: Mahout
          Issue Type: Bug
            Reporter: Andrew Palumbo
            Priority: Blocker


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.:

{code}
   // 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

{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)