[Bug] not handle negative values when process the accuracy range of datetime

[IKAZUCHI-Akira]

Search before asking

• I had searched in the issues and found no similar issues.

Version

Apache Doris: 2.1.6
Flink: 1.20
flink-doris-connector: 1.20-25.1.0-SNAPSHOT

What's Wrong?

When using Flink to read Doris' datetime type field, if the long value of the datetime is negative, an exception will occur because accuracy has not been processed.
Expection:java.time.DateTimeException: Instant exceeds minimum or maximum instant

What You Expected?

Properly handle datetime accuracy

How to Reproduce?

No response

Anything Else?

No response

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[JNSimba]

When will negative numbers appear?

[IKAZUCHI-Akira]

When will negative numbers appear?

When datetime before 1970-01-01 08:00:00(ZoneId is Asia/Shanghai)

[JNSimba]

This seems to be the minimum value in java.time.Instant?

    private static final long MIN_SECOND = -31557014167219200L;

    private static Instant create(long seconds, int nanoOfSecond) {
        if ((seconds | nanoOfSecond) == 0) {
            return EPOCH;
        }
        if (seconds < MIN_SECOND || seconds > MAX_SECOND) {
            throw new DateTimeException("Instant exceeds minimum or maximum instant");
        }
        return new Instant(seconds, nanoOfSecond);
    }

[IKAZUCHI-Akira]

This seems to be the minimum value in java.time.Instant?

private static final long MIN_SECOND = -31557014167219200L;
private static Instant create(long seconds, int nanoOfSecond) {
    if ((seconds | nanoOfSecond) == 0) {
        return EPOCH;
    }
    if (seconds < MIN_SECOND || seconds > MAX_SECOND) {
        throw new DateTimeException("Instant exceeds minimum or maximum instant");
    }
    return new Instant(seconds, nanoOfSecond);
}

Yes, job failed caused by dirty data DATETIME(6):0012-11-15 00:00:00.000000, its actual value is -61_760_995_200_000_000L