@java.lang.Override
        public VertexCustomConfig parsePartialFrom(
            com.google.protobuf.CodedInputStream input,
            com.google.protobuf.ExtensionRegistryLite extensionRegistry)
            throws com.google.protobuf.InvalidProtocolBufferException {
          Builder builder = newBuilder();
          try {
            builder.mergeFrom(input, extensionRegistry);
          } catch (com.google.protobuf.InvalidProtocolBufferException e) {
            throw e.setUnfinishedMessage(builder.buildPartial());
          } catch (com.google.protobuf.UninitializedMessageException e) {
            throw e.asInvalidProtocolBufferException().setUnfinishedMessage(builder.buildPartial());
          } catch (java.io.IOException e) {
            throw new com.google.protobuf.InvalidProtocolBufferException(e)
                .setUnfinishedMessage(builder.buildPartial());
          }
          return builder.buildPartial();
        }
<pre>
Optional. By setting the configuration_input_topic, processor will
subscribe to given topic, only pub/sub topic is supported now. Example
channel:
//pubsub.googleapis.com/projects/visionai-testing-stable/topics/test-topic
message schema should be:
message Message {
// The ID of the stream that associates with the application instance.
string stream_id = 1;
// The target fps. By default, the custom processor will *not* send any
data to the Vertex Prediction container. Note that once the
dynamic_config_input_topic is set, max_prediction_fps will not work and be
preceded by the fps set inside the topic.
int32 fps = 2;
}
</pre>

<code>
optional string dynamic_config_input_topic = 6 [(.google.api.field_behavior) = OPTIONAL];
</code>

@param value The bytes for dynamicConfigInputTopic to set.
@return This builder for chaining.
java-visionai/proto-google-cloud-visionai-v1/src/main/java/com/google/cloud/visionai/v1/VertexCustomConfig.java