[
https://issues.apache.org/jira/browse/HIVE-7615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dong Chen updated HIVE-7615:
----------------------------
Attachment: HIVE-7615.2.patch
Hi [~thejas], I have updated the patch based on your comments. I agree that we
should minimize the exposed public API to avoid confusion for users. This is a
precious comment to make the interface design better.
In the patch, I remove the QueryState, and use a private boolean
isExecuteStatementFailed to let getQueryLog() method specify the throwed
exceptions. Caller could know what exactly happened according to the exceptions.
The reason I did not use a boolean isRunning is that, I think when it is false,
the state not Running actually could be divided into two state: not Running
before the statement is executed, and not Running after the statement is
executed successfully. If we use this boolean to control getQueryLog and make
it failed for not Running, jdbc user may not get log after query is done.
Could you please take a look at it and see how does that sound? :)
> Beeline should have an option for user to see the query progress
> ----------------------------------------------------------------
>
> Key: HIVE-7615
> URL: https://issues.apache.org/jira/browse/HIVE-7615
> Project: Hive
> Issue Type: Improvement
> Components: CLI
> Reporter: Dong Chen
> Assignee: Dong Chen
> Attachments: HIVE-7615.1.patch, HIVE-7615.2.patch, HIVE-7615.patch,
> complete_logs, simple_logs
>
>
> When executing query in Beeline, user should have a option to see the
> progress through the outputs.
> Beeline could use the API introduced in HIVE-4629 to get and display the logs
> to the client.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
