Gabriel39 opened a new pull request, #68466:
URL: https://github.com/apache/doris/pull/68466
### What problem does this PR solve?
Several ADBC regression suites fail when their drivers are available because
their fixtures and expectations no longer match the current type semantics, or
depend on the machine running the tests.
- Validate `SHOW CREATE CATALOG` against the configured driver and fixture
paths instead of a developer-specific golden DDL.
- Explicitly select the Doris dialect for Doris loopback catalogs so failed
vendor discovery cannot fall back to ANSI identifier quoting.
- Regenerate DATETIME and floating-point baselines, assert DATETIME
predicate pushdown, and compare timestamps directly with the source without
casts that hide type changes.
- Parse JSON explicitly when constructing VARIANT objects, retaining the
object baseline and adding a native serialization comparison.
The DOUBLE maximum, subnormal values, timestamp precision, NULLs,
export/reload checks, and source-table comparisons remain covered. No product
code is changed.
### Release note
None
### Check List (For Author)
- Test
- [x] Regression test
- [ ] Unit Test
- [x] Manual test (details below)
- Behavior changed:
- [x] No product behavior change.
- Does this need documentation?
- [x] No.
### Testing
- Reproduced the existing outfile, type-mapping, predicate-pushdown and
VARIANT failures before the fix.
- Regenerated the four changed `.out` files by running the regression
framework with `-forceGenOut` against an isolated local Doris instance and ADBC
drivers 1.12.0: four suites, zero failures.
- Full ADBC directory run (`-g p0 -d external_table_p0/adbc`): 20 suites,
zero failures. Nineteen suites executed; `test_adbc_multi_backend` explicitly
skipped because the isolated cluster has one BE. The ASAN BE was configured
with a 32 GB memory limit.
Validation uses existing Doris CI binaries at `a581d264bf`, with an isolated
FE/BE and the regression framework; the product was not rebuilt for these
test-only changes.
--
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
