[Fix][Connector-V2] Fix kafka parse datetime value throw NPE

[LeonYoah]

Purpose of this pull request

#7079

• Fixed null pointer issue when kafka uses json to read datetime type encountering null values
• Fixed partition file path issue where path concatenation key=null if partition value was null

Does this PR introduce any user-facing change?

How was this patch tested?

Check list

• If any new Jar binary package adding in your PR, please add License Notice according
  New License Guide
• If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs
• If you are contributing the connector code, please check that the following files are updated:
  1. Update change log that in connector document. For more details you can refer to connector-v2
  2. Update plugin-mapping.properties and add new connector information in it
  3. Update the pom file of seatunnel-dist
• Update the release-note.

[Hisoka-X]

Thanks @LeonYoah created this PR! Could you add test case?

[LeonYoah]

Thanks @LeonYoah created this PR! Could you add test case?
Receive!

[Hisoka-X]

I want to confirm one thing first, is the data in kafka "" or null? If it is null, we should continue. If it is "", I think it is normal to report an error. Please refer #7181

[LeonYoah]

I want to confirm one thing first, is the data in kafka "" or null? If it is null, we should continue. If it is "", I think it is normal to report an error. Please refer #7181

I have read your pr, your design is very good, it is no problem to throw wrong theory, but there is another scenario you need to consider, that is, a batch of data sent from upstream, for example, {"date_field":"2023-02-01"},{"date_field":""}, should we return empty strings or pass null to the downstream database instead of parsing them?

[LeonYoah]

I want to confirm one thing first, is the data in kafka "" or null? If it is null, we should continue. If it is "", I think it is normal to report an error. Please refer #7181
I task this batch of tasks can not be due to an empty string caused by the task error directly quit

[Hisoka-X]

I think we can add an option to control this behavior. If a field cannot be parsed, return null or throw an error. Just like hive. Not just datetime type, this rule is suitable for any type of parsing. cc @hailin0

[LeonYoah]

I think we can add an option to control this behavior. If a field cannot be parsed, return null or throw an error. Just like hive. Not just datetime type, this rule is suitable for any type of parsing. cc @hailin0

Good idea. You can control whether to throw an exception or return null with parameters