Tracking(sink datatype mapping): Type missing when sink to MySQL, PostgreSQL or TiDB

[wugouzi]

Currently, there are some types in RisingWave that don't have counterparts in MySQL, PostgreSQL or TiDB, and we need some workaround for Debezium sink and jdbc sink:

• Interval for MySQL and TiDB
• struct for MySQL, and TiDB
• List for MySQL and TiDB
• Bytea for MySQL and TiDB
• Serial for MySQL and TiDB
• Int256 for MySQL, PostgreSQL and TiDB (reject sink for this type)

[neverchanje]

b19e651

DataType::Int16
    | DataType::Int32
    | DataType::Int64
    | DataType::Float32
    | DataType::Float64
    | DataType::Boolean
    | DataType::Decimal
    | DataType::Timestamp
    | DataType::Varchar

As shown in this commit, we are supposed to support more data types than you initially commented. I guess it has nothing to do with the specific sink. Whatever they are, we will need to handle the types instead of rejecting them in the validation phase:

• Date
• Time
• Timestamp
• TimestampTz
• Interval
• Jsonb
• Bytea
• List/Array
• Struct
• Int256 (unnecessary)

@wugouzi

[github-actions]

This issue has been open for 60 days with no activity.

If you think it is still relevant today, and needs to be done in the near future, you can comment to update the status, or just manually remove the no-issue-activity label.

You can also confidently close this issue as not planned to keep our backlog clean.
Don't worry if you think the issue is still valuable to continue in the future.
It's searchable and can be reopened when it's time. 😄