zhicwu commented on PR #18774: URL: https://github.com/apache/pulsar/pull/18774#issuecomment-1354234777
> What's the behavior if we pass null to a non-nullable column previously? Before v0.3.2, it depends on table structure(whether the column has default value) and server setting(whether `input_format_null_as_default` is `1`, which is the default). Starting from v0.3.2, you'll end up with a SQLException complaining you should not insert null into non-nullable column, unless client option `nullAsDefault` is set to `2`. > Is there a CHANGELOG for the details how the mapping and handling change? Unfortunately the answer is no. We use to have a CHANGELOG but it did not cover details like that. As I mentioned above, the impact to JDBC driver should be mainly about timestamp with timezone. @tisonkun & @nlu90, with no doubt that adding tests is needed. However, I'd suggest to start with acceptance tests from pulsar's point of view, instead of being distracted by compatibility issue of specific driver ;) -- 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 to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
