[ 
https://issues.apache.org/jira/browse/SPARK-6063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Griffiths updated SPARK-6063:
-------------------------------------
    Description: 
On Windows 8.1, trying to build Spark from source (latest Github pull) produces 
a failure during MLlib build. The cause appears similar to SPARK-3372: unicode 
characters in a Scala file.

*Affected file*
LDAModel.scala:133
   * This is often called “theta” in the literature.

Note the two \u201D marks around *theta*.

Replacing the \u201D with a standard single apostrophe (\x27) resolves the 
issue.

  was:
On Windows 8.1, trying to build Spark from source (latest Github pull) produces 
a failure during MLlib build. The cause appears similar to SPARK-3372: unicode 
characters in a Scala file.

**Affected file**
LDAModel.scala:133
   * This is often called “theta” in the literature.

Note the two \u201D marks around *theta*.

Replacing the \u201D with a standard single apostrophe (\x27) resolves the 
issue.


> MLlib doesn't pass mvn scalastyle check due to UTF chars in LDAModel.scala
> --------------------------------------------------------------------------
>
>                 Key: SPARK-6063
>                 URL: https://issues.apache.org/jira/browse/SPARK-6063
>             Project: Spark
>          Issue Type: Bug
>          Components: MLlib
>    Affects Versions: 1.2.1
>            Reporter: Michael Griffiths
>            Priority: Blocker
>
> On Windows 8.1, trying to build Spark from source (latest Github pull) 
> produces a failure during MLlib build. The cause appears similar to 
> SPARK-3372: unicode characters in a Scala file.
> *Affected file*
> LDAModel.scala:133
>    * This is often called “theta” in the literature.
> Note the two \u201D marks around *theta*.
> Replacing the \u201D with a standard single apostrophe (\x27) resolves the 
> issue.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to