-
Notifications
You must be signed in to change notification settings - Fork 322
Fix InProcessPipelineRunner to handle a null subscription #547
Fix InProcessPipelineRunner to handle a null subscription #547
Conversation
@@ -320,4 +327,14 @@ public void readManyMessages() throws IOException { | |||
assertTrue(dataToMessageNum.isEmpty()); | |||
reader.close(); | |||
} | |||
|
|||
@Test | |||
public void testNullTopic() throws Exception { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Null subscription, right? We probably also want to show that we created a subscription.
For verifying the subscription, is the least-bad way I can see is to make an additional factory method that includes a verifyCreateSubscription toggle. Anything nicer than that? |
Is this fixing the same bug as apache/beam@4406414 ? Thoughts on a more direct backport? |
better link: apache/beam#1817 |
I think this is a different issue (not present in Beam), made obsolete by
the new structure of the function in question.
…On Tue, Feb 14, 2017 at 9:31 AM, Daniel Halperin ***@***.***> wrote:
better link: apache/beam#1817 <apache/beam#1817>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#547 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACQVgeOymSRIOAwP6UwqlIR-XJhMM597ks5rceTdgaJpZM4L1p5d>
.
|
I don't think there's anything nicer than that, but I'm not particularly bothered (given that it's a |
Done, please take another look. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
R: @tgroh