You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@seatunnel.apache.org by TaoZex <26...@qq.com.INVALID> on 2022/10/28 02:15:20 UTC
RE： [Proposal] Access frequently used api by config not url
In the last weekly meeting we discussed the related issue that this method is more generic . I agree with your suggestion.
Best Regards,
TaoZex
------------------ 原始邮件 ------------------
发件人: "dev" <gaojun2048@apache.org>;
发送时间: 2022年10月28日(星期五) 上午10:03
收件人: "dev"<dev@seatunnel.apache.org>;
主题: Re: [Proposal] Access frequently used api by config not url
For those Http API connectors, I suggest that we add the "url" and "schema"
parameters in jobconfig instead of writing the "url" and "schema" into the
connector code. Because the "url" and "schema" can change. We are planning
to add a data source management module to SeaTunnel. In the future, we can
create an api in the data source management module_ Name, and add the url,
schema and api_ Name binding. In this way, users can directly select the
api on the SeaTunnel page_ Name to manually fill in the url and schema.
JUN GAO <gaojun2048@apache.org> 于2022年10月24日周一 22:37写道：
> Sorry, I'm not very clear about your scenario. Maybe you can illustrate it
> with a simple example？
>
> TaoZex <2633363995@qq.com.invalid> 于2022年10月23日周日 11:10写道：
>
>> Hi, everyone.
>>
>> In the SeaTunnel Connector V2 Tracking Table, many of the unfinished
>> connectors are based on Http requests. It would be troublesome for users to
>> provide only url to access the api.
>>
>>
>> So I suggest for frequently used api, access it through the config
>> configuration. At the same time, for the less frequently used api, the user
>> can access it by way of url.
>>
>>
>> If you have any suggestions or concerns, you are very welcome to comment
>> in&nbsp;this email thread.
>>
>> Best Regards,
>> TaoZex
>
>
>
> --
>
> Best Regards
>
> ------------
>
> EricJoy2048
> gaojun2048@gmail.com
>
>
--
Best Regards
------------
EricJoy2048
gaojun2048@gmail.com