[GitHub] [zeppelin] VipinRathor commented on pull request #4007: [ZEPPELIN-5180] - Improve Kerberos debug messages

VipinRathor commented on pull request #4007: URL: https://github.com/apache/zeppelin/pull/4007#issuecomment-751964635 Re-based after RAT check hotfix. This is an automated message from the Apache Git Service. To respond to

[GitHub] [zeppelin] VipinRathor commented on pull request #4001: [ZEPPELIN-5176] Kerberos ticket renewal fix in JDBC Interpreter

VipinRathor commented on pull request #4001: URL: https://github.com/apache/zeppelin/pull/4001#issuecomment-751964102 Rebased after RAT check hotfix. This is an automated message from the Apache Git Service. To respond to

[GitHub] [zeppelin] comma337 closed pull request #4008: [ZEPPELIN-5173] Fix the entity name according to the convention

comma337 closed pull request #4008: URL: https://github.com/apache/zeppelin/pull/4008 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

[GitHub] [zeppelin] zjffdu commented on pull request #4008: [ZEPPELIN-5173] Fix the entity name according to the convention

zjffdu commented on pull request #4008: URL: https://github.com/apache/zeppelin/pull/4008#issuecomment-751920232 Thanks @comma337 , looking forward your next PR This is an automated message from the Apache Git Service. To

[GitHub] [zeppelin] comma337 edited a comment on pull request #4008: [ZEPPELIN-5173] Fix the entity name according to the convention

comma337 edited a comment on pull request #4008: URL: https://github.com/apache/zeppelin/pull/4008#issuecomment-751920007 @zjffdu Thanks for the quick review. I agree with you, `hive` is easier to use than `jdbc.hive`. I understand that you intend to change convention. Still

[GitHub] [zeppelin] comma337 commented on pull request #4008: [ZEPPELIN-5173] Fix the entity name according to the convention

comma337 commented on pull request #4008: URL: https://github.com/apache/zeppelin/pull/4008#issuecomment-751920007 @zjffdu Thanks for the quick review. I agree with you, `hive` is easier to use than `jdbc.hive`. I understand that you intend to change convention. Still

[jira] [Created] (ZEPPELIN-5182) Zeppelin authentication with JDBC realm is not working

Suchit gupta created ZEPPELIN-5182: -- Summary: Zeppelin authentication with JDBC realm is not working Key: ZEPPELIN-5182 URL: https://issues.apache.org/jira/browse/ZEPPELIN-5182 Project: Zeppelin

[GitHub] [zeppelin] zjffdu commented on pull request #4008: [ZEPPELIN-5173] Fix the entity name according to the convention

zjffdu commented on pull request #4008: URL: https://github.com/apache/zeppelin/pull/4008#issuecomment-751748151 @comma337 I think using `hive` as entity name is more proper, `jdbc.hive` is a design issue in my opinion. When you create an interpreter `hive`, then `hive` is the new

[GitHub] [zeppelin] Reamer commented on pull request #4002: [ZEPPELIN-5178] notebook search not working on JDK11

Reamer commented on pull request #4002: URL: https://github.com/apache/zeppelin/pull/4002#issuecomment-751643047 @kkalyan Please rebase your branch. We have a hotfix. https://github.com/apache/zeppelin/commit/4acccfcbdf7ba24b4c24cc247a7b192594140edf

[GitHub] [zeppelin] comma337 opened a new pull request #4008: [ZEPPELIN-5173] Fix the entity name according to the convention

comma337 opened a new pull request #4008: URL: https://github.com/apache/zeppelin/pull/4008 ### What is this PR for? JDBC interpreter cannot get the username and password from the credential page. The reason is that the org.apache.zeppelin.jdbc.JDBCInterpreter#getEntityName method