You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2019/04/29 18:59:58 UTC

[GitHub] [pulsar] srkukarni commented on issue #4127: [Issue#4110] [component/functions] Adding message as source or input of Function

srkukarni commented on issue #4127: [Issue#4110] [component/functions] Adding message as source or input of Function
URL: https://github.com/apache/pulsar/pull/4127#issuecomment-487702370
 
 
   My biggest concern is about adding pulsar-client dep to functions interface. My inclination would be to keep the interfaces seperate as much as possible. 
   @sijie just thinking aloud here:- there might be specialization interfaces that might have closer pulsar integration. Just like windowing, we could have your MessageFunction api, but keep it at a user layer?

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services