rwzdk commented on PR #13020:
URL: https://github.com/apache/seatunnel/pull/13020#issuecomment-6514897743
Issue 1 is a fair coverage gap, so `bb27e280` adds it at the existing HTTP
IT boundary:
- `connector-http-e2e/src/test/resources/mockserver-config.json` — a new
`/jsonpath/ragged` expectation returning `{"a":[1],"b":[10,20]}`.
-
`connector-http-e2e/src/test/resources/http_ragged_jsonpath_to_assert.conf` —
`Http` source with `json_filed_missed_return_null = true` and `json_field = { a
= "$.a", b = "$.b[*]" }`, so the first path is list-valued without `[*]` and
the factory routes through `JsonPathProcessorImpl`; the `Assert` sink pins
`MIN_ROW = 2` / `MAX_ROW = 2` (one row per element of the longest path, the
case that used to fail with `IndexOutOfBoundsException`) plus `NOT_NULL` on `b`
so the padded second row cannot arrive with the second column dropped. The `a`
column deliberately gets no per-field rule: its two rows are `"1"` and `null`,
and the Assert rules are per field over all rows, so no single rule expresses
that pair — the row count plus the exit code is what pins it.
- `HttpIT.testSourceToAssertSink` — executes that conf and asserts exit code
0. The factory and matrix unit tests stay as they are.
Verification stated plainly: this machine has no Docker and none can be
installed here, so I could not run `HttpIT` locally — `mvn -o -pl
...connector-http-e2e test-compile` also stops at dependency resolution because
the e2e helper module is not in the local cache and I do not build with `-am`.
So I am not claiming a local red/green for this commit: the evidence will be
the fork `Build`'s `updated-modules-integration-test` jobs for the new head
`bb27e280`, which I will report and fix if they come back red. Everything that
could be checked locally stays green (`connector-http-base`: `Tests run: 74,
Failures: 0, Errors: 0` on JDK 17).
Prepared with an AI coding agent.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
