GitHub user debugger87 opened a pull request:

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

    [SPARK-21395][SQL] Spark SQL hive-thriftserver doesn't register operation 
log before execute sql statement

    ## What changes were proposed in this pull request?
    
    - Add a private method `registerCurrentOperationLog` in 
SparkExecuteStatementOperation
    - Call `registerCurrentOperationLog` before `execute()` and unregister it 
after `execute()`  like implementation in 
[SQLOperation.java#L204](https://github.com/apache/spark/blob/master/sql/hive-thriftserver/src/main/java/org/apache/hive/service/cli/operation/SQLOperation.java#L204)
    
    ## How was this patch tested?
    Add unittest in HiveThriftBinaryServerSuite
    
    ```
    build/mvn  -Phive-thriftserver -Dtest=none 
-DwildcardSuites=org.apache.spark.sql.hive.thriftserver.HiveThriftBinaryServerSuite
 test
    ```
    HiveThriftBinaryServerSuite tests passed
    


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

    $ git pull https://github.com/debugger87/spark master

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

    https://github.com/apache/spark/pull/18649.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 #18649
    
----
commit b5c963fec11b87cc43f542483d71422b79867750
Author: debugger87 <[email protected]>
Date:   2017-07-16T20:07:48Z

    [SPARK-21395][SQL] Spark SQL hive-thriftserver doesn't register operation 
log before execute sql statement

----


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