[
https://issues.apache.org/jira/browse/BEAM-6335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kenneth Knowles updated BEAM-6335:
----------------------------------
Resolution: Fixed
Status: Resolved (was: Resolved)
Hello! Due to a bug in our Jira configuration, this issue had status:Resolved
but resolution:Unresolved.
I am bulk editing these issues to have resolution:Fixed
If a different resolution is appropriate, please change it. To do this, click
the "Resolve" button (you can do this even for closed issues) and set the
Resolution field to the right value.
> 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
> Fix For: Not applicable
>
> 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)
