fix(jdbc): remove postgres jdbc sink schema if not specified

[chenzl25]

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

• Currently, we use public as the default schema for postgres jdbc sink sql. However, some of database like questdb doesn't support schema. I think we can just remove the schema from the dml if users haven't specified.

Checklist

• I have written necessary rustdoc comments.
• I have added necessary unit tests and integration tests.
• I have added test labels as necessary.
• I have added fuzzing tests or opened an issue to track them.
• My PR contains breaking changes.
• My PR changes performance-critical code, so I will run (micro) benchmarks and present the results.
• My PR contains critical fixes that are necessary to be merged into the latest release.

Documentation

• My PR needs documentation updates.

Release note

[tabVersion]

I think the fix may affect the existing jobs?
If a user rely on the behavior to connect to downstream, the fix can make the job fail after upgrade.

[chenzl25]

I think the fix may affect the existing jobs? If a user rely on the behavior to connect to downstream, the fix can make the job fail after upgrade.

I think it is fine, because public should be the default schema.

[github-actions]

Hi, there.

📝 Telemetry Reminder:
If you're implementing this feature, please consider adding telemetry metrics to track its usage. This helps us understand how the feature is being used and improve it further.
You can find the function report_event of telemetry reporting in the following files. Feel free to ask questions if you need any guidance!

• src/frontend/src/telemetry.rs
• src/meta/src/telemetry.rs
• src/stream/src/telemetry.rs
• src/storage/compactor/src/telemetry.rs
  Or calling report_event_common (src/common/telemetry_event/src/lib.rs) as if finding it hard to implement.
  ✨ Thank you for your contribution to RisingWave! ✨

---

This is an automated comment created by the peaceiris/actions-label-commenter. Responding to the bot or mentioning it won't have any effect.

[lmatz]

looks like questdb is not alone

let's label this as a breaking change

[lmatz]

wonder if it is urgently required by a known customer?
If time allows, it is better to give a 1-version notice in advance before making a breaking change

[chenzl25]

wonder if it is urgently required by a known customer? If time allows, it is better to give a 1-version notice in advance before making a breaking change

I think it is not that urgent.

[lmatz]

Got it,
as release-2.3 is cutoff, let's merge now and make it effective in v2.4