Change log level for driver registration

[buremba]

It looks like the log level is INFO for the driver registration. If you look at most JDBC implementations, they use DEBUG in this exact case since the registration is expected when we load ClickhouseDriver in the runtime.

[github-actions]

Benchmark                           (client)  (statement)   Mode  Cnt     Score     Error  Units
Basic.insertOneRandomNumber  clickhouse-jdbc       normal  thrpt   20   259.206 ±  30.530  ops/s
Basic.insertOneRandomNumber  clickhouse-jdbc     prepared  thrpt   20   261.069 ±  27.115  ops/s
Basic.selectOneRandomNumber  clickhouse-jdbc       normal  thrpt   20  1433.024 ± 203.160  ops/s
Basic.selectOneRandomNumber  clickhouse-jdbc     prepared  thrpt   20  1572.552 ± 240.538  ops/s

[buremba]

@zhicwu any ideas on why the tests are failing?

[zhicwu]

@zhicwu any ideas on why the tests are failing?

I think it's unrelated. I have a large PR on hand, let me merge this one over the weekend.

[buremba]

Thanks @zhicwu !

[buremba]

Hey @zhicwu, I see that latest patch version doesn't include this PR. Is there any timeline on when can we publish this?

[zhicwu]

Hey @zhicwu, I see that latest patch version doesn't include this PR. Is there any timeline on when can we publish this?

It will be released together with 0.3.2. Sorry it's a complete rewrite (unfortunately), so I don't have an exact ETA - maybe a few more weeks?

As to this specific issue, perhaps you can update logging configuration by changing log level for ru.yandex.clickhouse to ERROR? FYI, starting from 0.3.2, transaction APIs like commit(), rollback() and setSavepoint() etc. will be supported, and there'll be annoying warnings keep saying it's fake transaction. Faking transaction support can be turned off for sure, but still I think changing log level to ERROR is a better solution.

[buremba]

OK, thanks for letting me know @zhicwu !