treasure-data / perfectqueue / 88

Builds Branch Commit Type Ran Committer Via Coverage
88 master Merge pull request #19 from treasure-data/suppress-warning suppress warning: duplicated key at line 45 ignored: :type push nurse travis-ci pending completion   set done
87 master Merge pull request #18 from treasure-data/use-DO-for-RELEASE_LOCK Use DO Syntax for RELEASE_LOCK() push nurse travis-ci pending completion   set done
86 master suppress warning: duplicated key at line 45 ignored: :type Pull #19 nurse travis-ci pending completion   set done
85 master Introduce new timeout model * Separate the area where a DELETE query locks from the area where acquire query touchs. By this change DELETE query and acquire query can run parallel. ** finished task was SET timeout=now+retention_time, created_... Pull #17 nurse travis-ci pending completion   set done
84 separate-delete-and-acquire-queries Introduce new timeout model * Separate the area where a DELETE query locks from the area where acquire query touchs. By this change DELETE query and acquire query can run parallel. ** finished task was SET timeout=now+retention_time, created_... push nurse travis-ci pending completion   set done
83 use-DO-for-RELEASE_LOCK Use DO Syntax for RELEASE_LOCK() Manual says "The DO statement is convenient to use with RELEASE_LOCK()." https://dev.mysql.com/doc/refman/5.6/en/miscellaneous-functions.html#function_release-lock push nurse travis-ci pending completion   set done
82 suppress-warning suppress warning: duplicated key at line 45 ignored: :type push nurse travis-ci pending completion   set done
80 master Merge pull request #16 from treasure-data/remove-transaction Remove useless transaction push nurse travis-ci pending completion   set done
79 master Remove useless transaction In the old days it uses `SELECT FOR UPDATE` and require transaction. But these days it introduces `LOCK TABLES` and `GET_LOCK()` and don't need transaction. Pull #16 nurse travis-ci pending completion   set done
78 remove-transaction Remove useless transaction In the old days it uses `SELECT FOR UPDATE` and require transaction. But these days it introduces `LOCK TABLES` and `GET_LOCK()` and don't need transaction. push nurse travis-ci pending completion   set done
77 master Add spec to cover disable_resource_limit case Pull #15 nurse travis-ci pending completion   set done
76 use-CONNECTION_ID Add spec to cover disable_resource_limit case push nurse travis-ci pending completion   set done
75 master Use improved query by kamipo https://github.com/treasure-data/perfectqueue/pull/15#discussion_r52893022 Pull #15 nurse travis-ci pending completion   set done
74 use-CONNECTION_ID Use improved query by kamipo https://github.com/treasure-data/perfectqueue/pull/15#discussion_r52893022 push nurse travis-ci pending completion   set done
73 master Use CONNECTION_ID() for finer grained locking To acquire tasks, run UPDATE and SELECT insteadof SELECT and UPDATE. This adds a new column `owner` to identify which connection acquires the task. With this column, RDBCompatBackend#acquire now does... Pull #15 nurse travis-ci pending completion   set done