Github user randerzander commented on the issue:
https://github.com/apache/zeppelin/pull/2396
@jongyoul I fixed the Appveyor test, but having problems with the Jenkins
Python tests.
I don't believe these are related to my changes.. can you suggest what I
can try next?
---
Github user tinkoff-dwh commented on the issue:
https://github.com/apache/zeppelin/pull/2396
@randerzander
autocommit is already in JDBCInterpreter.
```
finally {
//In case user ran an insert/update/upsert statement
if (connection != null) {
Github user randerzander commented on the issue:
https://github.com/apache/zeppelin/pull/2396
@jongyoul I'm having trouble with CI.
Jenkins tests pass except 3 that relate to Python interpreter, I believe
unrelated to these small JDBC interpreter changes. Are the Python tests
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2396
You'd better rebase from current master to make your branch newer.
---
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2396
@randerzander Can you fix the failure of CI?
---
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2396
LGTM
---
Github user tzolov commented on the issue:
https://github.com/apache/zeppelin/pull/2396
The `JDBC interpreter` uses Connection's auto-commit status to decide
whether forceful to commit the connection. As it as pointed above `commit` is
not supported by many `NoSql` Jdbc
Github user randerzander commented on the issue:
https://github.com/apache/zeppelin/pull/2396
retest
---
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 if
