hello-stephen opened a new pull request, #68470:
URL: https://github.com/apache/doris/pull/68470

   ### What problem does this PR solve?
   
   Issue Number: None
   
   The External Regression environment now installs the Flight SQL and SQLite 
ADBC drivers, so the ADBC suites run instead of returning early. That exposed 
five assertions which had drifted since the suites were added:
   
   - floating-point extrema were compared through unstable decimal text in a 
golden file;
   - Doris Flight SQL now exposes `DATETIME` as a timezone-naive Arrow 
timestamp, so the old offset-bearing output and no-push expectation are stale;
   - `SHOW CREATE CATALOG` pinned one developer checkout's absolute driver path;
   - Variant V2 no longer implicitly parses a VARCHAR assigned to VARIANT, so 
the fixture created string scalars rather than JSON objects.
   
   The failures reproduce across unrelated PRs and none of their source 
revisions changes the ADBC suites.
   
   This change keeps the coverage while making the assertions semantic and 
portable:
   
   - compare floating-point values inside Doris, bit for bit, instead of 
comparing decimal spellings;
   - format the wall-clock timestamp explicitly and expect the now-valid 
timestamp predicate pushdown;
   - validate the runtime catalog path and properties directly;
   - construct object-valued VARIANT fixtures with `parse_to_variant`.
   
   ### Release note
   
   None. Regression-test-only change.
   
   ### Check List
   
   - Test
     - [x] Regression test
       - All five modified Groovy suites compile successfully with Groovy 
4.0.19.
       - `git diff --check` passes.
       - Focused External Regression execution is required because the local 
checkout does not contain the built ADBC drivers or third-party Thrift compiler.
   - Behavior changed:
     - [x] No production behavior changes.
   - Does this need documentation?
     - [x] No.
   


-- 
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]

Reply via email to