GitHub user smurakozi opened a pull request:

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

    [SPARK-21672][CORE] Remove SHS-specific application / attempt data …

    …structures
    
    ## What changes were proposed in this pull request?
    
    In general, the SHS pages now use the public API types to represent 
applications. Some internal code paths still used its own view of what 
applications and attempts look like (`ApplicationHistoryInfo` and 
`ApplicationAttemptInfo`), declared in ApplicationHistoryProvider.scala.
    
    This pull request removes these classes and updates the rest of the code to 
use `status.api.v1.ApplicationInfo` and `status.api.v1.ApplicationAttemptInfo` 
instead.
    
    Furthermore `status.api.v1.ApplicationInfo` and 
`status.api.v1.ApplicationAttemptInfo` were changed to case class to 
    - facilitate copying instances
    - equality checking in test code
    - nicer toString() 
    
    To simplify the code a bit `v1.` prefixes were also removed from 
occurrences of v1.ApplicationInfo and v1.ApplicationAttemptInfo as there is no 
more ambiguity between classes in history and status.api.v1.
    
    ## How was this patch tested?
    
    By running existing automated tests.
    
    Please review http://spark.apache.org/contributing.html before opening a 
pull request.


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

    $ git pull https://github.com/smurakozi/spark SPARK-21672

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

    https://github.com/apache/spark/pull/19920.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 #19920
    
----
commit a457acf3faeba94bb1473d2496b8a7126e4f8b1d
Author: Sandor Murakozi <[email protected]>
Date:   2017-12-06T16:34:28Z

    [SPARK-21672][CORE] Remove SHS-specific application / attempt data 
structures

----


---

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

Reply via email to