Skip to content
This repository has been archived by the owner on Nov 11, 2022. It is now read-only.

Fix InProcessPipelineRunner to handle a null subscription #547

Merged

Conversation

sammcveety
Copy link
Contributor

R: @tgroh

@@ -320,4 +327,14 @@ public void readManyMessages() throws IOException {
assertTrue(dataToMessageNum.isEmpty());
reader.close();
}

@Test
public void testNullTopic() throws Exception {
Copy link
Contributor

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.

@sammcveety
Copy link
Contributor Author

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?

@dhalperi
Copy link
Contributor

Is this fixing the same bug as apache/beam@4406414 ?

Thoughts on a more direct backport?

@dhalperi
Copy link
Contributor

better link: apache/beam#1817

@sammcveety
Copy link
Contributor Author

sammcveety commented Feb 14, 2017 via email

@tgroh
Copy link
Contributor

tgroh commented Feb 14, 2017

I don't think there's anything nicer than that, but I'm not particularly bothered (given that it's a PubsubTestClientFactory)

@sammcveety
Copy link
Contributor Author

Done, please take another look.

Copy link
Contributor

@tgroh tgroh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@tgroh tgroh merged commit 9b9ee0b into GoogleCloudPlatform:master Feb 15, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants