[jira] [Created] (ZEPPELIN-6017) Revert changes about ZEPPELIN_IDENT_STRING
Manhua Jiang created ZEPPELIN-6017:
--
Summary: Revert changes about ZEPPELIN_IDENT_STRING
Key: ZEPPELIN-6017
URL: https://issues.apache.org/jira/browse/ZEPPELIN-6017
Project: Zeppelin
Issue Type: Improvement
Reporter: Manhua Jiang
#5421 delete the definition check about ZEPPELIN_IDENT_STRING in case of
surefire version upgrade but it will make the log file names become:
zeppelin--SERVER.log
zeppelin--SERVER.out
zeppelin-interpreter-jdbc-shared_process–SERVER.log
in the defintion of:
zeppelin-${ZEPPELIN_IDENT_STRING}-${HOSTNAME}.log
zeppelin-${ZEPPELIN_IDENT_STRING}-${HOSTNAME}.out
zeppelin-interpreter-%INTERPRETER_ID%-%ZEPPELIN_IDENT_STRING%-%HOSTNAME%.log
so, we revert changes about ZEPPELIN_IDENT_STRING
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ZEPPELIN-6003) Log detail info of SQL in JDBCInterpreter
Manhua Jiang created ZEPPELIN-6003: -- Summary: Log detail info of SQL in JDBCInterpreter Key: ZEPPELIN-6003 URL: https://issues.apache.org/jira/browse/ZEPPELIN-6003 Project: Zeppelin Issue Type: Improvement Reporter: Manhua Jiang Currently we can monitor running SQL in JDBCInterpreter but unable to know who/which note fire the SQL, especially a couple of users using zeppelin at the same time. Bond the SQL with additional info, we can inform the user with user/noteid/paragragh info if needed -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ZEPPELIN-6002) Fix completer NPE
Manhua Jiang created ZEPPELIN-6002:
--
Summary: Fix completer NPE
Key: ZEPPELIN-6002
URL: https://issues.apache.org/jira/browse/ZEPPELIN-6002
Project: Zeppelin
Issue Type: Bug
Reporter: Manhua Jiang
NPE occur when adding the driver specific SQL completions. Some
driver(hive-jdbc-uber-2.6.5.0-292.jar in my case) does not implement method
{{DatabaseMetaData.getDriverName()}} well and cause exception , then fail to
initialize {{{}keywordCompleter{}}}.
Since it is optional, we should avoid such driver interfere the default one,
and log it for the profession
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
