You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@livy.apache.org by GitBox <gi...@apache.org> on 2019/11/19 12:52:11 UTC

[GitHub] [incubator-livy] huianyi opened a new pull request #238: [LIVY-689] Deliver stage process message to the end user using thriftserver

huianyi opened a new pull request #238: [LIVY-689] Deliver stage process message to the end user using thriftserver
URL: https://github.com/apache/incubator-livy/pull/238
 
 
   ## What changes were proposed in this pull request?
   When we use beeline to connect with thriftserver, we must open the spark history server to get the stage process, which is unconvenient, we can deliver process message to the end user.
   
   ## How was this patch tested?
   In our environment, the log to the end user is below,
   
   ```log
   0: jdbc:hive2://localhost:10090> select count(*) from dp_dw.tmp;
   RSC client is executing SQL query: select count(*) from dp_dw.tmp, statementId = 8de21e99-562d-46d9-a9f7-3007f82d5828, session = SessionHandle [89eb625f-ffdc-4dce-b23c-c715f4d6444d]
   2019-11-19 20:34:10.963 percentage:   0% active: 0 completed: 0 failed: 0 all: 0
   2019-11-19 20:34:12.965 percentage:   0% active: 0 completed: 0 failed: 0 all: 294
   2019-11-19 20:34:14.951 percentage:   0% active: 0 completed: 0 failed: 0 all: 294
   2019-11-19 20:34:16.95  percentage:   0% active: 0 completed: 0 failed: 0 all: 294
   2019-11-19 20:34:18.951 percentage:   0% active: 0 completed: 0 failed: 0 all: 294
   2019-11-19 20:34:20.951 percentage:   0% active: 1 completed: 0 failed: 0 all: 294
   2019-11-19 20:34:22.958 percentage:   0% active: 2 completed: 1 failed: 0 all: 294
   2019-11-19 20:34:24.952 percentage:  17% active: 2 completed: 51 failed: 0 all: 294
   2019-11-19 20:34:26.95  percentage:  42% active: 2 completed: 124 failed: 0 all: 294
   2019-11-19 20:34:28.951 percentage:  60% active: 2 completed: 177 failed: 0 all: 294
   2019-11-19 20:34:30.951 percentage:  61% active: 6 completed: 180 failed: 0 all: 294
   2019-11-19 20:34:32.951 percentage:  66% active: 13 completed: 194 failed: 0 all: 294
   2019-11-19 20:34:34.95  percentage:  99% active: 6 completed: 290 failed: 0 all: 294
   2019-11-19 20:34:36.952 percentage:  99% active: 2 completed: 292 failed: 0 all: 294
   2019-11-19 20:34:38.952 percentage:  99% active: 2 completed: 292 failed: 0 all: 294
   2019-11-19 20:34:40.952 percentage:  99% active: 2 completed: 292 failed: 0 all: 294
   2019-11-19 20:34:42.951 percentage:  99% active: 2 completed: 292 failed: 0 all: 294
   2019-11-19 20:34:44.953 percentage:  99% active: 2 completed: 292 failed: 0 all: 294
   2019-11-19 20:34:46.957 percentage:  99% active: 2 completed: 292 failed: 0 all: 294
   2019-11-19 20:34:48.953 percentage:  99% active: 2 completed: 292 failed: 0 all: 294
   2019-11-19 20:34:50.96  percentage:  99% active: 2 completed: 292 failed: 0 all: 294
   2019-11-19 20:34:52.954 percentage:  99% active: 2 completed: 292 failed: 0 all: 294
   2019-11-19 20:34:54.953 percentage:  99% active: 2 completed: 292 failed: 0 all: 294
   2019-11-19 20:34:56.953 percentage:  99% active: 2 completed: 292 failed: 0 all: 294
   2019-11-19 20:34:58.953 percentage:  99% active: 2 completed: 292 failed: 0 all: 294
   2019-11-19 20:35:00.954 percentage:  99% active: 2 completed: 292 failed: 0 all: 294
   2019-11-19 20:35:02.953 percentage:  99% active: 2 completed: 292 failed: 0 all: 294
   2019-11-19 20:35:04.954 percentage:  99% active: 2 completed: 292 failed: 0 all: 294
   2019-11-19 20:35:06.953 percentage:  99% active: 2 completed: 292 failed: 0 all: 294
   2019-11-19 20:35:08.954 percentage: 100% active: 1 completed: 293 failed: 0 all: 294
   2019-11-19 20:35:10.954 percentage: 100% active: 1 completed: 293 failed: 0 all: 294
   RSC client is fetching result schema for statementId = 8de21e99-562d-46d9-a9f7-3007f82d5828
   +------------+
   |  count(1)  |
   +------------+
   | 182138357  |
   +------------+
   1 row selected (61.118 seconds)
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services