ZHCGitHub commented on issue #17124:
URL: 
https://github.com/apache/dolphinscheduler/issues/17124#issuecomment-2796262955

   Yes, you are right. i look forward to DS releasing a stable and bug free new 
version as soon as possible, and i also hope that DS can go higher and further. 
Thank you very much 
   
   
   ZHC
   ***@***.***
   
   
   
    
   
   
   
   
   ------------------ 原始邮件 ------------------
   发件人: "Wenjun ***@***.***>; 
   发送时间: 2025年4月11日(星期五) 下午4:36
   收件人: ***@***.***>; 
   抄送: ***@***.***>; ***@***.***>; 
   主题: Re: [apache/dolphinscheduler] [Bug] [ SQL module] passed variable to 
create table, parameter passing error (Issue #17124)
   
   
   
   
   
   
   
   
   
   
   
   
      
   This is a history problem, probably caused by the initialized design of 
SqlTask. We have many datasources, and all of them are using the same task 
plugin instance, so there are existing some cases that is difficultly to adapt 
it. e.g. fetch log, split sql...
    
   The long term solution is to split the SqlTask on the backend to adapt 
different datasource.
    
   Let's back to this case, the main reason is due the the sql task don't 
directly replace the parameter in the sql, but will use ? placeholder, we would 
better keep the simple logic here, directly replace the parameter in sql rather 
than use ?.
   
   —
   Reply to this email directly, view it on GitHub, or unsubscribe.
   You are receiving this because you authored the thread.Message ID: 
***@***.***>
     ruanwenjun left a comment (apache/dolphinscheduler#17124)
    
   This is a history problem, probably caused by the initialized design of 
SqlTask. We have many datasources, and all of them are using the same task 
plugin instance, so there are existing some cases that is difficultly to adapt 
it. e.g. fetch log, split sql...
    
   The long term solution is to split the SqlTask on the backend to adapt 
different datasource.
    
   Let's back to this case, the main reason is due the the sql task don't 
directly replace the parameter in the sql, but will use ? placeholder, we would 
better keep the simple logic here, directly replace the parameter in sql rather 
than use ?.
    
   —
   Reply to this email directly, view it on GitHub, or unsubscribe.
   You are receiving this because you authored the thread.Message ID: 
***@***.***>


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