akka/akka-core

Generalize Split strategies

Open

#19,253 opened on Dec 21, 2015

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Scala (3,547 forks)batch import
1 - triagedhelp wantedt:stream

Repository metrics

Stars
 (13,277 stars)
PR merge metrics
 (Avg merge 8d 19h) (10 merged PRs in 30d)

Description

Split currently only supports one of SplitBefore and SplitAfter where all elements ultimately land in one of the to substreams.

A combination of both could emit more than two substreams where elements outside of these start and end markers are dropped.

This could render StreamUtils.sliceBytesTransformer redundant which is currently used in RangeDirectives.

Contributor guide

Research direction
Study the current SplitBefore and SplitAfter implementations, then design a combined split strategy that can emit multiple substreams and drop elements outside markers. See StreamUtils.sliceBytesTransformer for reference.
Tech stack
scala
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
ScalaAkka Streams
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50