Tags: org-spinnaker/keiko
Tags
Changing the default for fillExecutorEachCycle to true (spinnaker#151) A couple of blogs already propose to have the QueueProcessor behavior to fill up the worker thread pool every poll cycle, rather than processing a single message every interval. Co-authored-by: Rob Zienert <[email protected]>
fix(sql): PostgreSQL compatibility for keiko-sql (spinnaker#176) This change includes the following: - Removing bigint display qualifiers - these are MySQL specific, and display-only - A number of queries used MySQL-specific upsert features. These have been expanded with PostgreSQL-compatible varieties. - A small helper has been added to handle the dynamic Keiko queue table creation for PostgreSQL - A helper has been added to make use of Postgres's "excluded" conflict feature for inserts Co-authored-by: Adam Jordens <[email protected]>
chore(dependencies): Autobump korkVersion (spinnaker#169) Co-authored-by: root <root@d9d580d9b3c0>
chore(dependencies): Autobump korkVersion (spinnaker#164) Co-authored-by: root <root@59d9c736198e>
chore(dependencies): Autobump korkVersion (spinnaker#140) Co-authored-by: root <root@f9f2be0e9d83>
chore(dependencies): Autobump korkVersion (spinnaker#140) Co-authored-by: root <root@f9f2be0e9d83>
fix(sql): fix typo in `withPool` (spinnaker#124) We obviously want to refer to this queue's poolName, not the literal "poolName"...
chore(queue): add an informative toString() in SqlQueue (spinnaker#120) The QueueProcessor will now display something like `Using queue SqlQueue(queueName=default, poolName=default)`, which can be useful when there are multiple SqlQueue beans around connected to different sql pools
PreviousNext