[
https://issues.apache.org/jira/browse/BEAM-6335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17173689#comment-17173689
]
Beam JIRA Bot commented on BEAM-6335:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> GroupByKey uses data insertion pipeline in streaming tests
> ----------------------------------------------------------
>
> Key: BEAM-6335
> URL: https://issues.apache.org/jira/browse/BEAM-6335
> Project: Beam
> Issue Type: Sub-task
> Components: testing
> Reporter: Kasia Kucharczyk
> Priority: P2
> Labels: beam-fixit, stale-P2
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Uses prepared Java Data Insertion Pipeline to update GroupByKey in Python to
> load test streaming.
> This task contains following steps:
> # Create GroupByKey streaming test that accepts bytes
> # To stop test after arrived messages it is required to add a matcher. The
> matcher should work on number of messages because in case of load testing it
> would be difficult to compare big load of bytes (also casting bytes to string
> to compare load would be difficult).
> # All data is generated by SyntheticDataPublisher.java, which is sending
> bytes produced by synthetic source to PubSub. PubSub is used as a streaming
> source for the Python test.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
