pjfanning commented on code in PR #1535:
URL: https://github.com/apache/pekko-connectors/pull/1535#discussion_r3004731007


##########
slick/src/main/scala/org/apache/pekko/stream/connectors/slick/javadsl/Slick.scala:
##########
@@ -310,6 +353,41 @@ object Slick {
       .asJava
   }
 
+  /**
+   * Java API: creates a Flow that takes a stream of elements of
+   *           type T, transforms each element to a SQL statement
+   *           using the specified function, then executes
+   *           those statements against the specified Slick database
+   *           and allows to combine the statement result and element into a 
result type R.
+   *
+   * @param session The database session to use.
+   * @param executor Executor used to run mapper function in.
+   *                 E.g. the dispatcher of the ActorSystem.
+   * @param parallelism How many parallel asynchronous streams should be
+   *                    used to send statements to the database. Use a
+   *                    value of 1 for sequential execution.
+   * @param toStatement A function that creates the SQL statement to
+   *                    execute from the current element. Any DML or
+   *                    DDL statement is acceptable.
+   * @param mapper A function to create a result from the incoming element T
+   *               and the database statement result.
+   */
+  def flowWithPassThrough[T, R](
+      session: SlickSession,
+      executor: ExecutionContextExecutor,

Review Comment:
   it's an overloaded method so it is better to keep the params in the same 
order as the the existing methods



-- 
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.

To unsubscribe, e-mail: [email protected]

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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to