{"push_id":762045956,"size":3,"distinct_size":1,"ref":"refs/heads/2.2","head":"05ccfc044c66cfdb373f76477f60dd9315460384","before":"3a5506951a97e1441146ed7eee7109fcaf06a425","commits":[{"sha":"da636ae93706dac1c019c83a4ddbcad43fe0ac8b","author":{"email":"7a5e6f27299d2bbd9d04b59d9e8e4f8eab83d8cb@neotechnology.com","name":"Mats Rydberg"},"message":"Fix a rule planner bug related to unique indexes\n\nPreviously, the rule planner planned a normal index seek, regardless of whether\nthere existed a uniqueness constraint for the label/property pair. This caused\nthe index reader to not be refreshed at every read, leading to concurrency\nissues in some circumstances.\n\nTests were in place, but they asserted the SchemaIndex would plan AnyIndex and\nnot UniqueIndex.","distinct":false,"url":"https://api.github.com/repos/neo4j/neo4j/commits/da636ae93706dac1c019c83a4ddbcad43fe0ac8b"},{"sha":"9c9ea7c1ff7019b025a964b3e5b557814cecfab2","author":{"email":"51254f2883f7df281fd31f6afca2b9b7d14bb94d@c-base.org","name":"Stefan Plantikow"},"message":"Merge pull request #5169 from Mats-SX/2.1-rule-planner-unique-index\n\nFix a rule planner bug related to unique indexes","distinct":false,"url":"https://api.github.com/repos/neo4j/neo4j/commits/9c9ea7c1ff7019b025a964b3e5b557814cecfab2"},{"sha":"05ccfc044c66cfdb373f76477f60dd9315460384","author":{"email":"7a5e6f27299d2bbd9d04b59d9e8e4f8eab83d8cb@neotechnology.com","name":"Mats Rydberg"},"message":"Merge remote-tracking branch 'origin/2.1-maint' into 2.2","distinct":true,"url":"https://api.github.com/repos/neo4j/neo4j/commits/05ccfc044c66cfdb373f76477f60dd9315460384"}]}