Teon Banek 9071552ce1 Plan Cartesian after a merge point on master plan ...

Summary:
This should fix the issue of having a write followed by a read during
distributed execution. Any kind of merger of plans should behave like a
Cartesian with regards to planning the following ScanAll.

Reviewers: mtomic, mferencevic

Reviewed By: mtomic

Subscribers: pullbot

Differential Revision: https://phabricator.memgraph.io/D1624

2018-10-05 10:09:53 +02:00

..

benchmark

Separate distributed from single node storage

2018-10-05 09:19:33 +02:00

concurrent

Separate distributed from single node storage

2018-10-05 09:19:33 +02:00

distributed

Separate distributed from single node storage

2018-10-05 09:19:33 +02:00

drivers

Integrate driver tests with Apollo

2018-08-22 18:31:37 +02:00

feature_benchmark

Separate distributed from single node storage

2018-10-05 09:19:33 +02:00

integration

Separate distributed from single node storage

2018-10-05 09:19:33 +02:00

macro_benchmark

Separate distributed from single node storage

2018-10-05 09:19:33 +02:00

manual

Separate distributed from single node storage

2018-10-05 09:19:33 +02:00

property_based

Separate distributed from single node storage

2018-10-05 09:19:33 +02:00

public_benchmark

Update LDBC query implementation

2018-07-10 10:08:21 +02:00

qa

Separate distributed from single node storage

2018-10-05 09:19:33 +02:00

stress

Separate distributed from single node storage

2018-10-05 09:19:33 +02:00

unit

Plan Cartesian after a merge point on master plan

2018-10-05 10:09:53 +02:00

apollo_runs.py

Optimize Apollo build process

2018-05-16 14:52:27 +02:00

client-stress.sh

Migrate command line args to gflgs in tests

2017-07-06 13:54:12 +02:00

CMakeLists.txt

Add kafka benchmark

2018-08-29 16:35:31 +02:00