-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Old URL for CLI docs page is showing 404 #10124
Old URL for CLI docs page is showing 404 #10124
Comments
@samuelcolvin Docs for CLI were recently moved to https://arrow.apache.org/datafusion/user-guide/cli/index.html in this PR: #10078 @alamb could we setup a redirect? https://arrow.apache.org/datafusion/user-guide/cli.html is the URL that shows up in search results when looking for datafusion cli. Might confuse users to land on a missing page. |
Thanks. Redirect would be good. |
Thanks -- yes @tinfoil-knight and @samuelcolvin -- a redirect (or even just a page saying the content moved with a link to the new site). Prs most welcome |
@alamb @jayzhan211 |
take |
Thank you @doupache 🙏 |
(I hit this issue when google searching today so figured I would make a PR) This is what I came up with : #10187 |
Closes apache/datafusion#10124 # Rationale See apache/datafusion#10124 -- basically we moved a URL that is bookmarked / comes up in google search. We need to redirect to the new location # Changes Use the `.htaccess` process added in #505 #506 with @kou to redirect to the new location
I double checked the link and it appears to be going to the right place now. Thank you for the report @samuelcolvin -- sorry it took so long to fix |
No problem, seems to be working for me. |
Describe the bug
The CLI docs are down - https://arrow.apache.org/datafusion/user-guide/cli.html they're just showing 404 "Not Found"
To Reproduce
go to https://arrow.apache.org/datafusion/user-guide/cli.html
Work around is to use https://web.archive.org/web/20240227014509/https://arrow.apache.org/datafusion/user-guide/cli.html
Expected behavior
see them
Additional context
No response
The text was updated successfully, but these errors were encountered: