This is a meta issue about some important Pipeline Java Execution issues.

Priority Issues

• Java execution may start inputs before compilation of filters and outputs has completed Java execution may start inputs before compilation of filters and outputs has completed. #11170 - Fixed in start inputs only when all WorkerLoop are fully initialized #11492
• Java execution reorders events even with 1 pipeline worker Java execution reorders events even with 1 pipeline worker #10938
  • Abandoned tentative fix Preserve input event ordering with single pipeline worker #11020
  • Incomplete POC [POC][DISCUSS] preserve batched events order #11099 (does not solve the [complex aggregate filter scenario]
    (https://gist.github.com/yaauie/82e199687c490a2e04fe1f0c9d9a7fee))
  • New solution PR Add support for pipeline.ordered setting for java execution #11524
• Java execution startup is potentially slower for some configurations
• fix for regression introduced by Move class caching from ComputeStepSyntaxElement to CompiledPipeline #11482 with revert #11482 and fix redundant code generation #11564

Followup Issues

• improve pipeline.ordered setting to rebatch before outputs improve pipeline.ordered setting to rebatch before outputs #11550 - Fixed in Rebatch after filters when using pipeline.ordered #11710
• Document event ordering guaranties or lack thereof with multiple worker versus single worker - [Doc]Add section for conceptual info #11715
• Add integration harness around the expected compilation time which should be similar between single or multiple workers. Add integration test on JEE expected compilation time  #12476

Other issues

• quoted plugin options crashes logstash When using Java Execution Engine, using quoted plugin directives crashes Logstash #11222 - Fixed in support quoted plugin option keys #11688