I opened an issue for this: https://issues.apache.org/jira/browse/FLINK-7605
On Wed, Sep 6, 2017 at 4:24 PM, Flavio Pompermaier
wrote:
> Maybe this should be well documented also...is there any dedicated page to
> Flink and JDBC connectors?
>
> On Wed, Sep 6, 2017 at 4:12 PM, Fabian Hueske wrot
Maybe this should be well documented also...is there any dedicated page to
Flink and JDBC connectors?
On Wed, Sep 6, 2017 at 4:12 PM, Fabian Hueske wrote:
> Great!
>
> If you want to, you can open a PR that adds
>
> if (!conn.getAutoCommit()) {
> conn.setAutoCommit(true);
> }
>
> to JdbcOutput
Great!
If you want to, you can open a PR that adds
if (!conn.getAutoCommit()) {
conn.setAutoCommit(true);
}
to JdbcOutputFormat.open().
Cheers, Fabian
2017-09-06 15:55 GMT+02:00 Flavio Pompermaier :
> Hi Fabian,
> thanks for the detailed answer. Obviously you are right :)
> As stated by h
Hi Fabian,
thanks for the detailed answer. Obviously you are right :)
As stated by https://phoenix.apache.org/tuning.html auto-commit is disabled
by default in Phoenix, but it can be easily enabled just appending
AutoCommit=true to the connection URL or, equivalently, setting the proper
property in
Hi,
According to the JavaDocs of java.sql.Connection, commit() will throw an
exception if the connection is in auto commit mode which should be the
default.
So adding this change to the JdbcOutputFormat seems a bit risky.
Maybe the Phoenix JDBC connector does not enable auto commits by default
(o
Hi to all,
I'm writing a job that uses Apache Phoenix.
At first I used the PhoenixOutputFormat as (hadoop) OutputFormat but it's
not well suited to work with Table API because it cannot handle generic
objects like Rows (it need a DBWritable Object that should be already
present at compile time). S