optimizing-subgraph-queries-combining-binary-and-worst-case-optimal-joins
optimizing-subgraph-queries-combining-binary-and-worst-case-optimal-joins copied to clipboard
Published
20 hours ago •
queryproc
queryproc
Query results do not match
The number of tuples output is often 1 or 2 less than there actually are.
Reproduce:
- edges.csv:
9,1,3
9,4,3
12,1,0
9,1,2
9,6,4
2,1,3
5,1,2
9,6,3
12,1,2
11,2,4
-vertices.csv:
0,1
1,1
2,0
3,1
4,2
5,1
6,1
7,1
8,1
9,1
10,2
11,0
12,2
commands:
root@dc124d4957e7:~# rm -r /root/data/graphflow/
root@dc124d4957e7:~# mkdir /root/data/graphflow/
root@dc124d4957e7:~# python3 eva_graphflow_stream/scripts/serialize_dataset.py /root/data/edges.csv /root/data/graphflow/ -v /root/data/vertices.csv
[INFO ][2023-07-04 16:11:17.845] KeyStore: Serializing the types and labels key store.
[INFO ][2023-07-04 16:11:17.853] Graph: Serializing the data graph.
root@dc124d4957e7:~# JAVA_OPTS='-Xmx500G' python3 eva_graphflow_stream/scripts/serialize_catalog.py /root/data/graphflow/ -v 2
[INFO ][2023-07-04 16:12:07.315] Catalog: serializing the data graph's catalog.
root@dc124d4957e7:~# python3 eva_graphflow_stream/scripts/execute_query.py "(a:1)-[3]->(b:1)" /root/data/graphflow/
(a:1)-[3]->(b:1)
[INFO ][2023-07-04 16:12:18.357] OptimizerExecutor: Dataset loading run time: 115.204859 (ms)
[INFO ][2023-07-04 16:12:18.370] OptimizerExecutor: Optimizer run time: 10.196823 (ms)
[INFO ][2023-07-04 16:12:18.372] OptimizerExecutor: Plan initialization before exec run time: 10.196823 (ms)
[INFO ][2023-07-04 16:12:18.374] OptimizerExecutor: Query execution run time: 0.0371 (ms)
[INFO ][2023-07-04 16:12:18.374] OptimizerExecutor: Number output tuples: 2
[INFO ][2023-07-04 16:12:18.375] OptimizerExecutor: Number intermediate tuples: 0
[INFO ][2023-07-04 16:12:18.375] OptimizerExecutor: Plan: SCAN (a)->(b)
number of output tuples: expected 3 actual 2.
