-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-47434][WEBUI] Fix statistics link in StreamingQueryPage
#45527
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
Conversation
dongjoon-hyun
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for making a PR, @HuwCampbell . Please create a new JIRA issue because you cannot make a follow-up PR for the released JIRA issue. Your new JIRA needs to have different Fix Versions.
|
Thank you, @HuwCampbell . |
|
Could you enable GitHub Action on your repository? It seems that CI is not running. |
|
Also, cc @yaooqinn too. |
Related to [Spark-24553] This causes redirect issues when one is using proxy settings.
statistics link in StreamingQueryPage
Would you mind providing before-and-after screenshots in the PR desc? |
|
Ya, we understand. That's enough. Please attach them to the PR description, @HuwCampbell . |
|
In addition, you can add another screenshot which shows that the previous link doesn't work. |
|
Ok |
dongjoon-hyun
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1, LGTM. Thank you, @HuwCampbell and @yaooqinn .
Merged to master/3.5/3.4.
### What changes were proposed in this pull request? Like SPARK-24553, this PR aims to fix redirect issues (incorrect 302) when one is using proxy settings. Change the generated link to be consistent with other links and include a trailing slash ### Why are the changes needed? When using a proxy, an invalid redirect is issued if this is not included ### Does this PR introduce _any_ user-facing change? Only that people will be able to use these links if they are using a proxy ### How was this patch tested? With a proxy installed I went to the location this link would generate and could go to the page, when it redirects with the link as it exists. Edit: Further tested by building a version of our application with this patch applied, the links work now. ### Was this patch authored or co-authored using generative AI tooling? No. Page with working link <img width="913" alt="Screenshot 2024-03-18 at 4 45 27 PM" src="https://github.com/apache/spark/assets/5205457/dbcd1ffc-b7e6-4f84-8ca7-602c41202bf3"> Goes correctly to <img width="539" alt="Screenshot 2024-03-18 at 4 45 36 PM" src="https://github.com/apache/spark/assets/5205457/89111c82-b24a-4b33-895f-9c0131e8acb5"> Before it would redirect and we'd get a 404. <img width="639" alt="image" src="https://github.com/apache/spark/assets/5205457/1adfeba1-a1f6-4c35-9c39-e077c680baef"> Closes #45527 from HuwCampbell/patch-1. Authored-by: Huw Campbell <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]> (cherry picked from commit 9b466d3) Signed-off-by: Dongjoon Hyun <[email protected]>
### What changes were proposed in this pull request? Like SPARK-24553, this PR aims to fix redirect issues (incorrect 302) when one is using proxy settings. Change the generated link to be consistent with other links and include a trailing slash ### Why are the changes needed? When using a proxy, an invalid redirect is issued if this is not included ### Does this PR introduce _any_ user-facing change? Only that people will be able to use these links if they are using a proxy ### How was this patch tested? With a proxy installed I went to the location this link would generate and could go to the page, when it redirects with the link as it exists. Edit: Further tested by building a version of our application with this patch applied, the links work now. ### Was this patch authored or co-authored using generative AI tooling? No. Page with working link <img width="913" alt="Screenshot 2024-03-18 at 4 45 27 PM" src="https://github.com/apache/spark/assets/5205457/dbcd1ffc-b7e6-4f84-8ca7-602c41202bf3"> Goes correctly to <img width="539" alt="Screenshot 2024-03-18 at 4 45 36 PM" src="https://github.com/apache/spark/assets/5205457/89111c82-b24a-4b33-895f-9c0131e8acb5"> Before it would redirect and we'd get a 404. <img width="639" alt="image" src="https://github.com/apache/spark/assets/5205457/1adfeba1-a1f6-4c35-9c39-e077c680baef"> Closes #45527 from HuwCampbell/patch-1. Authored-by: Huw Campbell <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]> (cherry picked from commit 9b466d3) Signed-off-by: Dongjoon Hyun <[email protected]>
|
Welcome to the Apache Spark community, @HuwCampbell . I added you to the Apache Spark Contributor group and assigned SPARK-47434 to you. Thank you again. |


What changes were proposed in this pull request?
Like SPARK-24553, this PR aims to fix redirect issues (incorrect 302) when one is using proxy settings. Change the generated link to be consistent with other links and include a trailing slash
Why are the changes needed?
When using a proxy, an invalid redirect is issued if this is not included
Does this PR introduce any user-facing change?
Only that people will be able to use these links if they are using a proxy
How was this patch tested?
With a proxy installed I went to the location this link would generate and could go to the page, when it redirects with the link as it exists.
Edit: Further tested by building a version of our application with this patch applied, the links work now.
Was this patch authored or co-authored using generative AI tooling?
No.
Page with working link

Goes correctly to

Before it would redirect and we'd get a 404.