[feature request] Allow Java Iceberg library to write parquet files with special character column names

[kevinjqliu]

Feature Request / Improvement

Based on discussions from iceberg-python/#584, we found that the Java Iceberg library "sanitizes" and transforms column names with special characters before writing to parquet.

For example, an Iceberg table with TEST:A1B2.RAW.ABC-GG-1-A column is transformed into TEST_x3AA1B2_x2ERAW_x2EABC_x2DGG_x2D1_x2DA which is then used to write the parquet files.
This process is done for both reads and writes. The behavior was introduced in #601

I think Iceberg should (optionally) allow writing column names without the "sanitization" and transformation. This can be made configurable to enable backward compatibility.

Query engine

None

[Fokko]

I can confirm this, when creating a table:

CREATE TABLE default.abc(`a.b+c` string); %%sql
INSERT INTO default.abc VALUES ('a'), ('b')

The field name is sanitized:

parq 00000-0-bd071a55-7d0f-4ecd-b4be-44f55532624d-0-00001.parquet --schema 

 # Schema 
 <pyarrow._parquet.ParquetSchema object at 0x14cf4fdc0>
required group field_id=-1 table {
  required binary field_id=1 a_x2Eb_x2Bc (String);
}

[github-actions]

This issue has been automatically marked as stale because it has been open for 180 days with no activity. It will be closed in next 14 days if no further activity occurs. To permanently prevent this issue from being considered stale, add the label 'not-stale', but commenting on the issue is preferred when possible.

[github-actions]

This issue has been automatically marked as stale because it has been open for 180 days with no activity. It will be closed in next 14 days if no further activity occurs. To permanently prevent this issue from being considered stale, add the label 'not-stale', but commenting on the issue is preferred when possible.

[github-actions]

This issue has been closed because it has not received any activity in the last 14 days since being marked as 'stale'