Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[LIVY-990][SERVER] Persisting Livy Statements #423

Closed
wants to merge 1 commit into from

Conversation

askhatri
Copy link
Contributor

What changes were proposed in this pull request?

Persisting Livy Statements into files to generate statement history logs for auditing purpose.

JIRA: https://issues.apache.org/jira/browse/LIVY-990

How was this patch tested?

Tested manually by creating statements in Livy interactive session.

@codecov-commenter
Copy link

Codecov Report

Merging #423 (527a273) into master (8b2e29f) will decrease coverage by 36.90%.
The diff coverage is 47.22%.

@@              Coverage Diff              @@
##             master     #423       +/-   ##
=============================================
- Coverage     65.48%   28.59%   -36.90%     
+ Complexity      950      382      -568     
=============================================
  Files           103      104        +1     
  Lines          6062     6098       +36     
  Branches        916      920        +4     
=============================================
- Hits           3970     1744     -2226     
- Misses         1541     3997     +2456     
+ Partials        551      357      -194     
Files Coverage Δ
...rver/src/main/scala/org/apache/livy/LivyConf.scala 95.30% <100.00%> (+1.01%) ⬆️
...e/livy/server/interactive/InteractiveSession.scala 71.32% <100.00%> (+9.10%) ⬆️
...pache/livy/server/interactive/StatementStore.scala 34.48% <34.48%> (ø)

... and 84 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@askhatri askhatri closed this Jun 24, 2024
@askhatri askhatri deleted the LIVY-990 branch June 24, 2024 09:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants