[ 
https://issues.apache.org/jira/browse/SPARK-10662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901460#comment-14901460
 ] 

Jacek Laskowski commented on SPARK-10662:
-----------------------------------------

It's [~jlaskowski] not [~jlewandowski] in Assignee. We've got very similar 
names, but he's much better at Spark, Cassandra, and all the things (a 
DataStax'er, after all) . Mind fixing it, [~sowen]? Thanks!

> Code snippets are not properly formatted in tables
> --------------------------------------------------
>
>                 Key: SPARK-10662
>                 URL: https://issues.apache.org/jira/browse/SPARK-10662
>             Project: Spark
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 1.5.0
>            Reporter: Jacek Laskowski
>            Assignee: Jacek Lewandowski
>            Priority: Trivial
>             Fix For: 1.6.0
>
>         Attachments: spark-docs-backticks-tables.png
>
>
> Backticks (markdown) in tables are not processed and hence not formatted 
> properly. See 
> http://people.apache.org/~pwendell/spark-nightly/spark-master-docs/latest/running-on-yarn.html
>  and search for {{`yarn-client`}}.
> As per [Sean's 
> suggestion|https://github.com/apache/spark/pull/8795#issuecomment-141019047] 
> I'm creating the JIRA task.
> {quote}
> This is a good fix, but this is another instance where I suspect the same 
> issue exists in several markup files, like configuration.html. It's worth a 
> JIRA since I think catching and fixing all of these is one non-trivial 
> logical change.
> If you can, avoid whitespace changes like stripping or adding space at the 
> end of lines. It just adds to the diff and makes for a tiny extra chance of 
> merge conflicts.
> {quote}



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org

Reply via email to