Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1360
Thanks LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1360
Addressed upgrade.md
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1360
Finished rebase. Ci failure is unrelated. Merging if there's no more
discussion.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1360
@jongyoul Then can we use JDBC interpreter as described in [How to
use](http://zeppelin.apache.org/docs/0.7.0-SNAPSHOT/interpreter/jdbc.html#how-to-use)
section like before? I just wondered :D
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1360
@bzz @Leemoonsoo Thanks, I don't know the proper location to describe the
changes actually. I'll also update upgrade.md. And about changing a behaviour
of JDBC, in case of `%jdbc(mysql)`, I
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1360
I think it changes way of configuration. From single jdbc interpreter
setting manages multiple jdbc connection, to individual interpreter setting
manage single jdbc connection.
How
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1360
LGTM.
> Is there breaking changes for older versions? Yes
Do we have a change-log or something where we can keep track of breaking
changes to highlight them in the release?
