[zeppelin] branch master updated: ZEPPELIN-3331: Fix the default interpreter lifecycle documentation

[pd...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

pdallig pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/zeppelin.git


The following commit(s) were added to refs/heads/master by this push:
     new 26321da  ZEPPELIN-3331: Fix the default interpreter lifecycle documentation
26321da is described below

commit 26321da0d973d93a7d4c95febdefd754e18f1cf6
Author: Jocelyn Turcotte <tu...@gmail.com>
AuthorDate: Mon Nov 2 17:12:00 2020 +0100

    ZEPPELIN-3331: Fix the default interpreter lifecycle documentation
    
    ### What is this PR for?
    Fix the default interpreter lifecycle documentation following https://github.com/apache/zeppelin/pull/2878#issuecomment-720456126.
    
    ### What type of PR is it?
    Documentation
    
    ### What is the Jira issue?
    https://issues.apache.org/jira/browse/ZEPPELIN-3331
    
    Author: Jocelyn Turcotte <tu...@gmail.com>
    
    Closes #3962 from jturcotte/patch-1 and squashes the following commits:
    
    7337b7cc2 [Jocelyn Turcotte] ZEPPELIN-3331: Fix the default interpreter lifecycle documentation
---
 docs/usage/interpreter/overview.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/usage/interpreter/overview.md b/docs/usage/interpreter/overview.md
index 7584abf..9087877 100644
--- a/docs/usage/interpreter/overview.md
+++ b/docs/usage/interpreter/overview.md
@@ -110,10 +110,10 @@ For more information, please consult [Interpreter Binding Mode](./interpreter_bi
 ## Interpreter Lifecycle Management
 
 Before 0.8.0, Zeppelin doesn't have lifecycle management for interpreters. Users had to shut down interpreters explicitly via the UI. Starting from 0.8.0, Zeppelin provides a new interface
-`LifecycleManager` to control the lifecycle of interpreters. For now, there are two implementations: `NullLifecycleManager` and `TimeoutLifecycleManager` which is the default. 
+`LifecycleManager` to control the lifecycle of interpreters. For now, there are two implementations: `NullLifecycleManager` and `TimeoutLifecycleManager`. 
 
 `NullLifecycleManager` will do nothing, i.e., the user needs to control the lifecycle of interpreter by themselves as before. `TimeoutLifecycleManager` will shut down interpreters after an interpreter remains idle for a while. By default, the idle threshold is 1 hour.
-Users can change this threshold via the `zeppelin.interpreter.lifecyclemanager.timeout.threshold` setting. `TimeoutLifecycleManager` is the default lifecycle manager, and users can change it via `zeppelin.interpreter.lifecyclemanager.class`.
+Users can change this threshold via the `zeppelin.interpreter.lifecyclemanager.timeout.threshold` setting. `NullLifecycleManager` is the default lifecycle manager, and users can change it via `zeppelin.interpreter.lifecyclemanager.class`.
 
 
 ## Inline Generic Configuration