yeti-web
yeti-web copied to clipboard
[ WARN]: Scoped order is ignored, it's forced to be batch order.
Jun 6 20:26:01 host YETI-admin[697]: [20:26:01.181145 ] [ INFO]: Processing by Api::Rest::System::JobsController#run as JSON
Jun 6 20:26:01 host YETI-admin[697]: [20:26:01.181203 ] [ INFO]: Parameters: {"id"=>"EventProcessor"}
Jun 6 20:26:01 host YETI-admin[697]: [20:26:01.182542 ] [ INFO]: Starting scheduler EventProcessor
Jun 6 20:26:01 host YETI-admin[697]: [20:26:01.187960 ] [ WARN]: Scoped order is ignored, it's forced to be batch order.
Jun 6 20:26:01 host YETI-admin[697]: [20:26:01.188536 ] [ INFO]: Job EventProcessor processed 0/0 events.
Jun 6 20:26:01 host YETI-admin[697]: [20:26:01.191294 ] [ INFO]: Completed 204 No Content in 10ms (ActiveRecord: 6.4ms)
https://apidock.com/rails/v5.2.3/ActiveRecord/Batches/in_batches
NOTE: It’s not possible to set the order. That is automatically set to ascending on the primary key (“id ASC”) to make the batch ordering consistent. Therefore the primary key must be orderable, e.g. an integer or a string.