You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by zjffdu <gi...@git.apache.org> on 2018/12/13 08:24:46 UTC

[GitHub] zeppelin pull request #3263: ZEPPELIN-3907. Add code statement into Spark Jo...

GitHub user zjffdu opened a pull request:

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

    ZEPPELIN-3907. Add code statement into Spark JobGroup Id for SparkInterpreter

    
    ### What is this PR for?
    Straightforward change to add code statement into Spark JobGroupId, so that we can find the associated spark job in spark ui easier. 
    
    
    ### What type of PR is it?
    [ Improvement ]
    
    ### Todos
    * [ ] - Task
    
    ### What is the Jira issue?
    * https://jira.apache.org/jira/browse/ZEPPELIN-3907
    
    ### How should this be tested?
    * Manually tested.
    
    ### Screenshots (if appropriate)
    ![image](https://user-images.githubusercontent.com/164491/49925345-92e83680-fef3-11e8-949c-1b97ea55724b.png)
    
    
    ### 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/zjffdu/zeppelin ZEPPELIN-3907

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

    https://github.com/apache/zeppelin/pull/3263.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 #3263
    
----
commit 9c1d3ccd25287259578785ea23e329fdcedab700
Author: Jeff Zhang <zj...@...>
Date:   2018-12-13T08:22:33Z

    ZEPPELIN-3907. Add code statement into Spark JobGroup Id for SparkInterpreter

----


---

[GitHub] zeppelin issue #3263: ZEPPELIN-3907. Add code statement into Spark JobGroup ...

Posted by FireArrow <gi...@git.apache.org>.
Github user FireArrow commented on the issue:

    https://github.com/apache/zeppelin/pull/3263
  
    While this is a really nice feature to have, it does introduce some risk of information leakage in an organization. Take for example `select * from tableofsecrets where secretcolumn = 'supersecret'`.
    What about adding a configuration parameter for activating this feature?


---