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

Daniel Becker updated IMPALA-11825:
-----------------------------------
    Description: 
We recently updated the upstream Impala docs in 
[https://gerrit.cloudera.org/#/c/19367/]
The doc build system introduced a new directory with CSS formatted html but 
also renamed the old 'html' directory to 'plain-html'.
The problem is that changing the directory name from 'html' to 'plain-html' 
breaks web search results which still point to the old links.

Broken links may damage SEO ranking so we should come up with a quick solution.

  was:
We recently updated the upstream Impala docs in 
https://gerrit.cloudera.org/#/c/19367/
The doc build system introduced a new directory with CSS formatted html but 
also renamed the old 'html' directory to 'plain-html'.
The problem is that changing the directory name from 'html' to 'plain-html' 
breaks web search results which still point to the old links.


> Doc update 4.2.0 breaks web search results 
> -------------------------------------------
>
>                 Key: IMPALA-11825
>                 URL: https://issues.apache.org/jira/browse/IMPALA-11825
>             Project: IMPALA
>          Issue Type: Documentation
>            Reporter: Daniel Becker
>            Assignee: Daniel Becker
>            Priority: Critical
>
> We recently updated the upstream Impala docs in 
> [https://gerrit.cloudera.org/#/c/19367/]
> The doc build system introduced a new directory with CSS formatted html but 
> also renamed the old 'html' directory to 'plain-html'.
> The problem is that changing the directory name from 'html' to 'plain-html' 
> breaks web search results which still point to the old links.
> Broken links may damage SEO ranking so we should come up with a quick 
> solution.



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