Sure,
I have a connector that will uses HTTP rest call to 3rd party system to get
some data based on URL and parameters.

Idea is to make it available to Flink SQL in order to use it like
SELECT * FROM T where t.id = 123

I would like to have two streams, one would be from T, and the second one
would be from some other place and I would like to join them.



czw., 4 lis 2021 o 16:18 Ingo Bürk <i...@ververica.com> napisał(a):

> Hi Krzysztof,
>
> the new, unified Source interface can only work as a scan source. Could
> you maybe elaborate a bit on the connector implementation you have and how
> you intend to have it work as a lookup source?
>
>
> Best
> Ingo
>
> On Thu, Nov 4, 2021 at 4:11 PM Krzysztof Chmielewski <
> krzysiek.chmielew...@gmail.com> wrote:
>
>> Thanks Fabian and Ingo,
>> yes I forgot to add the refrence links, so here they are:
>>
>> [1]
>> https://flink.apache.org/2021/09/07/connector-table-sql-api-part1.html
>> [2] https://flink.apache.org/2021/09/07/connector-table-sql-api-part2
>> [3]
>> https://ci.apache.org/projects/flink/flink-docs-master/docs/dev/datastream/sources/
>>
>> In my case I would really need a LookupTableSource and not
>> ScanTableSource since by use-case and source will get data for given
>> parameters and I don't need to scan the entire resource.
>>
>> Cheers,
>>
>> czw., 4 lis 2021 o 15:48 Krzysztof Chmielewski <
>> krzysiek.chmielew...@gmail.com> napisał(a):
>>
>>> Hi,
>>> I was wondering if it is possible to implement a Source Table connector
>>> like it is described in [1][2] with custom source that implements a new
>>> Source interface [3] and not a SourceFunction.
>>>
>>> I already have my custom source but when I'm trying to implement a Table
>>> Source from LookupTableSource or ScanTableSource like it is presented in
>>> [1][2] It seems I need to have a SourceFunction object to To be able to use
>>> ScanRuntimeProvider or LookupRuntimeProvider.
>>>
>>> In other words how can I use Source interface implementation in
>>> TableSource?
>>>
>>> Regards,
>>> Krzysztof Chmielewski
>>>
>>

Reply via email to