This message was deleted.
# generals
Slackbot
06/07/2023, 12:16 PMThis message was deleted.
e
Enrico Olivelli
06/07/2023, 1:27 PMare you talking about “functions”/“sinks”/“sources” ?
t
Tom (Xiatech)
06/09/2023, 7:28 AMhey Enrico yes
Tom (Xiatech)
06/09/2023, 7:29 AMDo each of these instances handle 1 message at a time, or can they be made concurrent - do you know this
e
Enrico Olivelli
06/09/2023, 7:45 AMA connector (that is a function) can handle parallelism.
In a function you can return CompletableFuture.
In a Sink you can call record.ack in any thread and in any order (you should use a shared subscription then)
Enrico Olivelli
06/09/2023, 7:45 AMIt's up to the implementation
Enrico Olivelli
06/09/2023, 7:46 AMRegarding the autoscaler, Pulsar functions do not have autoscaler ability and you cannot use keda.
Enrico Olivelli
06/09/2023, 7:46 AMKeda works well with Pulsar Consumer applications
Enrico Olivelli
06/09/2023, 7:47 AMI have contributed a few fixes (with my team mates) last year
t
Tom (Xiatech)
06/09/2023, 7:47 AMYou sound like know what you are talking about - thanks Enrico, i have asked another question (in the main thread) which if you have time, do you mind looking over it and providing feedback
Tom (Xiatech)
06/09/2023, 7:47 AMthese points you raise - important to know thank you, we were considering using keda
Tom (Xiatech)
06/09/2023, 7:48 AMwhy can't we use keda for pulsar functions - is that only possible for sinks and source?
e
Enrico Olivelli
06/09/2023, 7:48 AMSorry, I just received a notification on this thread.
t
Tom (Xiatech)
06/09/2023, 7:48 AMi'll @ you - if you don't mind me doing that
e
Enrico Olivelli
06/09/2023, 7:49 AMWe cannot because basically Pulsar is like an Operator and it controls the statefulsets
Enrico Olivelli
06/09/2023, 7:49 AMSure, feel free to connect