Flow.Processor for Operation submission

Douglas Surber douglas.surber at oracle.com
Wed Oct 11 20:05:00 UTC 2017

I have found what at first glance appears to be a non-hacky way to use Flow to channel Operations to an OperationGroup. It’s not perfect. The limitation that published Operations must be member Operations of the Operation group is unfortunate but absolutely necessary. Otherwise I think it is ok.

Delete Connection.onSubscribe.

Add the following to OperationGroup:

   * Returns a Flow.Processor that subscribes to a sequence of Operations and
   * publishes a sequence of corresponding Submissions. The Operations must
   * be members of this OperationGroup. Calling Subscription.onNext with any
   * Operation that is not a member of this OperationGroup, that is 
   * was not created by calling one of the Operation factory methods on this
   * OperationGroup, will throw IllegalArgumentException. The method
   * Subscription.onNext will call submit on each Operation it is passed
   * and publish the resulting Submission. Since an Operation can only be
   * submitted once, submitting an Operation and calling onNext with that 
   * submitted Operation will throw IllegalStateException.
   * Each call to this method returns a new Flow.processor. The Submissions 
   * published to each Processor are exactly those generated by calling
   * submit on the Operations passed as arguments to onNext on the same Processor.
   * Note: If any Operation is submitted directly, that is by calling submit
   * rather than passing it to onNext, the Submission returned by the submit
   * call will not be published.
   * @return a Flow.Processor that accepts Operations and generates Submissions
  public Flow.Processor<Operation<T>, Submission<T>> operationProcessor();


Still thinking about how to publish rows.


More information about the jdbc-spec-discuss mailing list