NganWave commented on PR #11496:
URL: https://github.com/apache/seatunnel/pull/11496#issuecomment-5158776361

   Thanks for your review and suggestions. I've applied them locally and all 
changes passed my tests, including the multi‑table scenario using `table_list` 
with `table_path` and `use_regex` to handle the JSON‑in‑array case (the first 
screenshot attached below).
   
   However, I'm not pushing the code just yet, because yesterday's CI run 
failed unexpectedly with exactly the same configuration that works fine on my 
machine. I'm currently investigating, but I haven't found the root cause yet. 
   
   **I would really appreciate it if someone could help me look into the CI 
failure together** – any hints about environment differences or known CI quirks 
would be very helpful. I'd like to avoid wasting CI resources on repeated 
failures.  For comparison, I've also pasted the CI error logs and a screenshot 
of the CI failure right after it.
   
   Additionally, there is a remaining issue with the underlying `array‑in‑JSON` 
parsing logic. Since it's closely related to the JSON parameter support, I plan 
to resolve it within this PR if possible; otherwise, I'll open a follow‑up PR 
for it. I'll keep you posted on progress.
   
   Thanks again!
   
   <img width="1824" height="949" alt="b22532e6-dc96-4e8d-a815-30e2c4ff6a6f" 
src="https://github.com/user-attachments/assets/acd5dc38-75ab-4fbe-8e4d-4a61773bc58d";
 />
   
   
   
   <img width="1371" height="787" alt="0ee7059f-92c4-4d80-bd9a-c52a1bd84ebd" 
src="https://github.com/user-attachments/assets/daebeefa-303c-450a-b3f0-c3d3e060a683";
 />
   
   <img width="1425" height="479" alt="image" 
src="https://github.com/user-attachments/assets/74395641-71a6-47fc-baca-0bacc9b13e8c";
 />
   
   
   


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

Reply via email to