apache/seatunnel · error · UnsupportedOperationException

Unsupported byte value '${value}' for row kind.

Error message

Unsupported byte value '${value}' for row kind.

What it means

RowKind.fromByteValue maps the wire bytes 0..3 (INSERT, UPDATE_BEFORE, UPDATE_AFTER, DELETE) to RowKind values. Any other byte has no defined row kind, so UnsupportedOperationException is thrown to catch corrupt or protocol-violating data.

Source

Thrown at seatunnel-api/src/main/java/org/apache/seatunnel/api/table/type/RowKind.java:113

    /**
     * Creates a {@link RowKind} from the given byte value. Each {@link RowKind} has a byte value
     * representation.
     *
     * @see #toByteValue() for mapping of byte value and {@link RowKind}.
     */
    @SuppressWarnings("MagicNumber")
    public static RowKind fromByteValue(byte value) {
        switch (value) {
            case 0:
                return INSERT;
            case 1:
                return UPDATE_BEFORE;
            case 2:
                return UPDATE_AFTER;
            case 3:
                return DELETE;
            default:
                throw new UnsupportedOperationException(
                        "Unsupported byte value '" + value + "' for row kind.");
        }
    }
}

View on GitHub (pinned to cf67b549a7)

Solutions

1. Verify the producing format: only bytes 0-3 are valid SeaTunnel row kinds
2. Log and inspect the offending byte to identify the corrupt source or version mismatch
3. Upgrade reader/writer versions so both sides use the same row-kind encoding
4. Validate the byte before calling: if (value >= 0 && value <= 3) RowKind.fromByteValue(value);

Example fix

// before
RowKind kind = RowKind.fromByteValue(rawByte); // throws on 4+
// after
if (rawByte < 0 || rawByte > 3) {
    throw new IOException("Corrupt row kind byte: " + rawByte);
}
RowKind kind = RowKind.fromByteValue(rawByte);

if (value < 0 || value > 3) {
    throw new IOException("Invalid row kind byte: " + value);
}
RowKind kind = RowKind.fromByteValue(value);

try {
    RowKind kind = RowKind.fromByteValue(value);
} catch (UnsupportedOperationException e) {
    // skip record, increment corrupt-record metric, or route to DLQ
}

When it happens

Trigger: Deserializing CDC/binlog-like payloads where the row-kind byte is corrupted, comes from an unsupported protocol version, or a caller passes an arbitrary byte (e.g. 4, 0x7F) to fromByteValue.

Common situations: Reading records from an incompatible or newer producer that encodes extra row kinds; bit-manipulation bugs packing flags into the kind byte; hand-written serializers writing wrong byte values.

Related errors

• Json parse object exception!
• Json parse list exception!
• json to map exception!
• Json parse object exception.
• String json deserialization exception.<content>

AI-assisted analysis of apache/seatunnel@cf67b549a7 (2026-09-10). Data as JSON: /api/errors/bf8e6f08654a45f3. Report an issue: GitHub.