forked from apache/pulsar
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Refactor to support at-least-once processing (apache#54)
* Refactor to support at-least-once processing This change is refactoring the relationship between Spawner, FunctionContainer and JavaInstance to better support various processing semantics. - ThreadFunctionContainerFactory is a "singleton" across multiple functions. - Spawner, FunctionContainer and JavaInstance are per function. Spawner is manging the lifecycle of function container, in the function container it will folks a thread for running java instance, because it has to load classpathes correctly. - Remove subscribermanager and move consumer and producer logic into container. that means in future if we are supporting process based and docker based container, we can just take the thread container and run it directly as a separate process or a separate docker process. There is no extra communication between spawner and containers. * Create pulsar client in thread container factory
- Loading branch information
Showing
12 changed files
with
236 additions
and
573 deletions.
There are no files selected for viewing
118 changes: 0 additions & 118 deletions
118
.../java/org/apache/pulsar/functions/runtime/benchmark/ThreadFunctionContainerBenchmark.java
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.