GitHub user vanzin opened a pull request:

    https://github.com/apache/spark/pull/5922

    [SPARK-7378] [core] Handle deep links to unloaded apps.

    The code was treating deep links as if they were attempt IDs, so
    for example if you tried to load "/history/app1/jobs" directly,
    that would fail because the code would treat "jobs" as an attempt id.
    
    This change modifies the code to try both cases - first without an
    attempt id, then with it, so that deep links are handled correctly.
    This assumes that the links in the Spark UI do not clash with the
    attempt id namespace, though, which is the case for YARN at least,
    which is the only backend that currently publishes attempt IDs.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/vanzin/spark SPARK-7378

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/5922.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #5922
    
----
commit b728f08beb2df2a3d6c0eca106e347ed84a34678
Author: Marcelo Vanzin <[email protected]>
Date:   2015-05-05T21:28:33Z

    [SPARK-7378] [core] Handle deep links to unloaded apps.
    
    The code was treating deep links as if they were attempt IDs, so
    for example if you tried to load "/history/app1/jobs" directly,
    that would fail because the code would treat "jobs" as an attempt id.
    
    This change modifies the code to try both cases - first without an
    attempt id, then with it, so that deep links are handled correctly.
    This assumes that the links in the Spark UI do not clash with the
    attempt id namespace, though, which is the case for YARN at least,
    which is the only backend that currently publishes attempt IDs.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

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

Reply via email to