No snow use com.fasterxml json

[sfc-gh-bzabek]

Overview

NO-SNOW

I need to have standard com.fasterxml to be compatible with IcebergUtils when parsing a KafkaRecord into Iceberg Type. Entire connector uses net.snowflake.client.jdbc.internal.fasterxml.

It's because snowflake JDBC driver uses "shading" in its pom.xml. Even though the driver uses standard com.fasterxml after compiling it into a jar the package is net.snowflake.client.jdbc.internal.fasterxml.
JDBC driver exposed telemetry method that requires net.snowflake.client.jdbc.internal.fasterxml as an argument - TelemetryUtil.buildJobData(ObjectNode obj). As a result the whole connector is bounded to the type inherited from the driver.

There are to approaches two solve it:

• change imports in the entire connector and map com.fasterxml -> net.snowflake.client.jdbc.internal.fasterxml in SnowflakeTelemetryService.send method which I made in a first commit (see: link)
• leave net.snowflake.client.jdbc.internal.fasterxml as it is only in telemetry related services (second commit)

Or I can do hacks before parsing a json to Iceberg.

Pre-review checklist

• This change should be part of a Behavior Change Release. See go/behavior-change.
• This change has passed Merge gate tests
• Snowpipe Changes
• Snowpipe Streaming Changes
• This change is TEST-ONLY
• This change is README/Javadocs only
• This change is protected by a config parameter <PARAMETER_NAME> eg snowflake.ingestion.method.
  • Yes - Added end to end and Unit Tests.
  • No - Suggest why it is not param protected
• Is his change protected by parameter <PARAMETER_NAME> on the server side?
  • The parameter/feature is not yet active in production (partial rollout or PrPr, see Changes for Unreleased Features and Fixes).
  • If there is an issue, it can be safely mitigated by turning the parameter off. This is also verified by a test (See go/ppp).

[sfc-gh-mbobowski]

Kafka Connector and snowflake-jdbc use the same 2.17.2 version of Jackson so it shouldn't be a problem to replace it.

Could you ask JDBC team what is the reason for using shaded library in the public interface? Maybe they can provide more convenient api for us?

[sfc-gh-bzabek]

Kafka Connector and snowflake-jdbc use the same 2.17.2 version of Jackson so it shouldn't be a problem to replace it.

Could you ask JDBC team what is the reason for using shaded library in the public interface? Maybe they can provide more convenient api for us?

Yes I will ask them.

[sfc-gh-bzabek]

Kafka Connector and snowflake-jdbc use the same 2.17.2 version of Jackson so it shouldn't be a problem to replace it.
Could you ask JDBC team what is the reason for using shaded library in the public interface? Maybe they can provide more convenient api for us?

Yes I will ask them.

I tried to use snowflake-jdbc-thin however it failed becouse ingest-sdk is still bouded with jdbc-driver internals.