apache/beam · error · java.lang.IllegalArgumentException

flushRowLimit must be greater than 0.

Error message

flushRowLimit must be greater than 0.

What it means

validate() in SnowflakeWriteConfiguration rejects a flushRowLimit that is set but not strictly positive. flushRowLimit controls how many rows are buffered before a flush to Snowflake during streaming (SnowPipe) writes, so zero or negative values are meaningless and would prevent any batching. The check only fires when the value is explicitly configured (null is allowed).

Solutions

1. Set flushRowLimit to a positive integer (e.g. 10000) or leave it unset (null) to use the library default.
2. Fix the config source so 'unset' is represented as null/omitted rather than 0.
3. Guard dynamic computation: only call withFlushRowLimit when the computed value is > 0.

Example fix

// before
.withFlushRowLimit(0)
// after
.withFlushRowLimit(10000)

Integer flushRowLimit = cfg.getFlushRowLimit();
if (flushRowLimit != null && flushRowLimit <= 0) {
  throw new IllegalArgumentException("flushRowLimit must be > 0 or null");
}

try {
  config.validate();
} catch (IllegalArgumentException e) {
  if (e.getMessage().startsWith("flushRowLimit")) { /* set a positive default, e.g. 10000 */ }
  throw e;
}

When it happens

Trigger: Setting flushRowLimit to 0 or a negative integer in SnowflakeWriteConfiguration (e.g. .withFlushRowLimit(0)) or via the corresponding SchemaTransform config before validate() runs.

Common situations: Developers pass a value read from YAML/JSON config where 0 was used as a placeholder for 'unset', or compute the limit dynamically and the computation yields 0 when an upstream list is empty.

Understand the failure class

Background: "Invalid value" and "allowed values are" config errors: what your library rejected and how to fix it — this error's family across 41 libraries.

Related errors

• flushTimeLimitMillis must be greater than 0.
• shardsNumber must be greater than 0.
• snowPipe is required for streaming writes.
• Either table or query must be specified.
• Failed to setLoginTimeout

AI-assisted analysis of apache/beam@12126d8942 (2026-09-13). Data as JSON: /api/errors/615a980f72365c35. Report an issue: GitHub.

Appendix: source

Thrown at sdks/java/io/snowflake/src/main/java/org/apache/beam/sdk/io/snowflake/SnowflakeWriteConfiguration.java:160

    // Parse configured enum values to validate that they are supported.
    String createDisposition = getCreateDisposition();
    if (createDisposition != null) {
      parseCreateDisposition(createDisposition);
    }

    String writeDisposition = getWriteDisposition();
    if (writeDisposition != null) {
      parseWriteDisposition(writeDisposition);
    }

    String debugMode = getDebugMode();
    if (debugMode != null) {
      parseStreamingLogLevel(debugMode);
    }

    Integer flushRowLimit = getFlushRowLimit();
    if (flushRowLimit != null && flushRowLimit <= 0) {
      throw new IllegalArgumentException("flushRowLimit must be greater than 0.");
    }

    Long flushTimeLimitMillis = getFlushTimeLimitMillis();
    if (flushTimeLimitMillis != null && flushTimeLimitMillis <= 0) {
      throw new IllegalArgumentException("flushTimeLimitMillis must be greater than 0.");
    }

    Integer shardsNumber = getShardsNumber();
    if (shardsNumber != null && shardsNumber <= 0) {
      throw new IllegalArgumentException("shardsNumber must be greater than 0.");
    }
  }

  private static void requireNonEmpty(String value, String name) {
    if (value == null || value.isEmpty()) {
      throw new IllegalArgumentException(name + " cannot be empty");
    }
  }

View on GitHub (pinned to 12126d8942)