[Java][Vector] Always-true precondition check in LargeListVector.setValueCount allows silent data corruption

[LuciferYang]

Describe the bug

In LargeListVector.setValueCount(), the precondition check that validates childValueCount before casting from long to int uses || instead of &&, making the condition always evaluate to true:

Preconditions.checkArgument(
    childValueCount <= Integer.MAX_VALUE || childValueCount >= Integer.MIN_VALUE,
    "LargeListVector doesn't yet support 64-bit allocations: %s",
    childValueCount);

For any long value x, at least one of x <= Integer.MAX_VALUE or x >= Integer.MIN_VALUE is always true (their union covers the entire long range), so the check never rejects any value.

This means:

• A childValueCount exceeding Integer.MAX_VALUE silently truncates when cast to (int), causing data corruption
• A negative childValueCount (from corrupted offset data) is silently passed through

Expected behavior

The check should use && with a lower bound of 0 (since childValueCount represents element count and must be non-negative):

Preconditions.checkArgument(
    childValueCount <= Integer.MAX_VALUE && childValueCount >= 0,
    "LargeListVector doesn't yet support 64-bit allocations: %s",
    childValueCount);

This is consistent with the correct implementation in LargeListViewVector.setValueCount() (line 887-890).

Component(s)

Java