dpcollins-google commented on a change in pull request #13470:
URL: https://github.com/apache/beam/pull/13470#discussion_r539841781



##########
File path: 
sdks/java/io/google-cloud-platform/src/main/java/org/apache/beam/sdk/io/gcp/pubsublite/PubsubLiteIO.java
##########
@@ -64,8 +64,8 @@ private PubsubLiteIO() {}
    *     .build()), "read");
    * }</pre>
    */
-  public static Read.Unbounded<SequencedMessage> read(SubscriberOptions 
options) {
-    return Read.from(new PubsubLiteUnboundedSource(options));
+  public static PTransform<PBegin, PCollection<SequencedMessage>> 
read(SubscriberOptions options) {

Review comment:
       Yeah I don't agree. Reading from multiple subscriptions to process the 
same data is a niche use-case: especially given that we try to commit to not 
only never breaking API but the internal structure to prevent from breaking 
dataflow refreshing, I think we should keep the API surface as small as 
possible. Given how niche this is and how easy it is (5 LOC), I see no benefit 
in adding noise to the API surface of PubsubLiteIO.




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to