GitHub user liancheng opened a pull request:

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

    [SPARK-15550][SQL][WIP] Dataset.show() should show contents nested products 
as rows

    ## What changes were proposed in this pull request?
    
    This PR addresses two related issues:
    
    1. `Dataset.showString()` should show case classes/Java beans at all levels 
as rows, while master code only handles top level ones.
    
    2. `Dataset.showString()` should show full contents produced the underlying 
query plan
    
       Dataset is only a view of the underlying query plan. Columns not 
referred by the encoder are still reachable using methods like `Dataset.col`. 
So it probably makes more sense to show full contents of the query plan.
    
    (This is still in WIP status because I'd expect multiple test failures from 
those test cases that depend on output of `Dataset.showString()`.)
    
    ## How was this patch tested?
    
    Two new test cases are added in `DatasetSuite` to check `.showString()` 
output.

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

    $ git pull https://github.com/liancheng/spark spark-15550-ds-show

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

    https://github.com/apache/spark/pull/13331.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 #13331
    
----
commit a1baec5a3adbdfdc6fd5e414c89b05d0c97924a6
Author: Cheng Lian <[email protected]>
Date:   2016-05-26T17:51:04Z

    Dataset.show() should show contents nested products as rows

----


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