GitHub user cloverhearts reopened a pull request:

    https://github.com/apache/zeppelin/pull/988

    ZEPPELIN-985 ] Fixed bug in the Pyspark completion

    ### What is this PR for?
    Currently, does not work 'pyspark completion'.
    
    ### What type of PR is it?
    Bug Fix
    
    ### Todos
    - [x] - change standard output for completion to interpreter outer.
    
    ### What is the Jira issue?
    https://issues.apache.org/jira/browse/ZEPPELIN-985
    
    ### How should this be tested?
    Try keyword completion for pyspark interpreter.
    
    ### Screenshots (if appropriate)
    #### Before
    
![pycompletion_err2](https://cloud.githubusercontent.com/assets/10525473/15961476/ed5eae40-2f3f-11e6-8e22-e0df6b7012c9.gif)
    
    #### After
    
![pycompletion](https://cloud.githubusercontent.com/assets/10525473/15961433/b60d534c-2f3f-11e6-84f1-cd828f7db9e0.gif)
    
    ### Questions:
    * Does the licenses files need update? no
    * Is there breaking changes for older versions? no
    * Does this needs documentation? no


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

    $ git pull https://github.com/cloverhearts/zeppelin hotfix/nwPyspark

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

    https://github.com/apache/zeppelin/pull/988.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 #988
    
----
commit 7c09a7a1b2f5913b7f7ea654cf3c8e8d54e22dc1
Author: CloverHearts <[email protected]>
Date:   2016-06-10T09:57:16Z

    fixed pyspark completion.

----


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

Reply via email to