[Fix] Fix clickhouse local generate file has <0x00> (#6089)

[zhanggougou]

Purpose of this pull request

fix clickhouse local generate file has <0x00>,it will cause

Does this PR introduce any user-facing change?

no

How was this patch tested?

after fix，i success transfer 300KW records from hive to ck

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]

Hi @zhanggougou , thanks for contribute this. Could you explain the reason of change?

[zhanggougou]

Hi @zhanggougou , thanks for contribute this. Could you explain the reason of change?

you can see this issue #6089
when 【buffer.position() + byteData.length > buffer.capacity()】，a new MappedByteBuffer will generate,but last MappedByteBuffer also has some space ,because the bufferSize is fixed

so i compute fileChannel.position，when buffer is not enough,the next will continue previous position,so the local_data will not contains unnecessary <0x00>

Is my problem？but when i fixed it，i succesed transfer data 【OR higher version ck local can ignore <0x00>?】

Looking forward to your reply，thanks

[EricJoy2048]

Can you add e2e to test this pr?

[zhanggougou]

Can you add e2e to test this pr?

sorry，i am a newcomer in this project，e2e means？

now，i suspect if this is a bug，give me some time，i will transfer data again to test