Rob Povey

This seems to be a broader issue with any incorrectly returning true when it's used over something returned from the main query, then subsequently used to filter the input of...

From some tests today, I believe this is probably related to null handling if connectionTableTargetDiagramName is null in the original query, the Any returns true any(i IN ids WHERE i...

Just to add to the inconsistency this returns two empty lists ``` OPTIONAL MATCH (x:DOG) CALL { OPTIONAL MATCH (d:DOG) RETURN COLLECT(DISTINCT d) AS dogs } RETURN COLLECT(DISTINCT(x)), dogs ```

Yes but this doesn't return any data ``` OPTIONAL MATCH (x:DOG) CALL { MATCH (d:DOG) RETURN COLLECT(DISTINCT d) AS dogs } RETURN COLLECT(DISTINCT(x)), dogs ``` Despite both the optional Match...

It just happened again, let me see what I can get for you. Because it's a customer cluster, and we haven't been able to reproduce it locally, I'm limited in...

The replica was unavailable when that happened, it froze about 6 hours earlier, so there was no replication happening. We're going to try and reproduce in a more controlled environment.

Thankyou, I think that likely is related, on one of the use cases I know it would have sent 10's of thousands of small writes, and in the other it...

I have a bit more detail on the workload that causes this. Were writing about 30,000 to 100,000 edges to the database in blocks of 100 per call. we're basically...

I've verified the issue doesn't need the Set at all MERGE is setting the relationship properties on the wrong relationship

I think I have something of a handle on what's happening. My metrics were apparently incomplete, missing some writes to the DB. What seems to cause this is updating about...