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

Kent Yao reassigned SPARK-49944:
--------------------------------

    Assignee: Neil Ramaswamy

> Fix Javascript and image imports in the documentation site
> ----------------------------------------------------------
>
>                 Key: SPARK-49944
>                 URL: https://issues.apache.org/jira/browse/SPARK-49944
>             Project: Spark
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 4.0.0
>            Reporter: Neil Ramaswamy
>            Assignee: Neil Ramaswamy
>            Priority: Major
>              Labels: pull-request-available
>
> In [SPARK-49378|https://github.com/apache/spark/pull/47864/], we introduced a 
> change to break apart the Structured Streaming programming guide. This 
> created several pages under `/streaming`.
> To make this change work, we had to modify some file-paths in script files; 
> previously, they used to rely on the fact that every page were siblings. But 
> after the nesting of `/streaming` was added, this assumption was broken. We 
> introduced the `rel_path_to_root` Jekyll variable to make this work, and we 
> used it in most places.
> However, we [inadvertently 
> modified|https://github.com/apache/spark/pull/47864/files#diff-729ad9c4e852768f70b7c45195e7e5f8271a7f3146df73045e441d024b907819R201-R202]
>  the paths to our main Javascript file and AnchorJS import to be absolute. 
> These should instead be prefixed with `rel_path_to_root`. (The net effect is 
> that the language-specific code blocks aren't rendering properly on any of 
> the pages.)
> Also, the images in the Structured Streaming programming guide use `/img`, 
> which is not correct. Those also need `rel_path_to_root`.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to