anchor.diff:  {:onyx/name :inc
    :onyx/fn :onyx.peer.batch-function-test/my-inc
    :onyx/type :function
  - :onyx/bulk? true
  + :onyx/batch-fn? true
    :onyx/batch-size batch-size}
   ----
   
  
positive.code: available, they will be added to this task to progressively meet the
  `:onyx/min-peers` number of peers concurrently working on this task.
  
  === Bulk Functions
  
  Sometimes you might be able to perform a function more efficiently over
  a batch of segments rather than processing one segment at a time, such
  as writing segments to a database in a non-output task. You can receive
  the entire batch of segments in bulk as an argument to your task by
  setting `:onyx/bulk?` to `true` in your catalog entry for your function.
  Onyx will _ignore_ the output of your function and pass the same
  segments that you received downstream. The utility of this feature is
  that you receive the entire batch in one shot. Onyx ignores your output
  because it would make it impossible to track which specific messages are
  children of particular upstream messages - breaking Onyx's fault
  tolerance mechanism.
  
  Functions with this key enabled may _not_ be used with flow conditions.
  These segments are passed to all immediate downstream tasks.
  
  An example catalog entry:
  
  
negative.code: [source,clojure]
  ----
  (defn my-inc [segments]
    (map #(update-in % [:n] inc) segments))
  ----
  
  The default value for this option is `false`.
  