kyle.cao

> the first one have each of the rows of the second one multiplied by the number of team nodes. ACK, I misunderstood. > We do some optimizations for some...

I found some information on the ldbc official website: https://ldbcouncil.org/benchmarks/snb/LDBC_SNB_I_20220816_SF30-100-300_tugraph.pdf

https://github.com/nebula-contrib/DataX

Fwiw, some simple aggregations like `count(*)` can be considered pushed down to the storage layer(Scan or Traverse operator). This may greatly improve the performance of statements like the above.

This error(`[ERROR (-1005)]: Scan vertices or edges need to specify a limit number, or limit number can not push down.`) will only be raised when no available index and no...

Closed because retesting the above behavior is expected.

Part of the core stack is as follows: ``` #0 0x0000000004c290a6 in nebula::Value::toString[abi:cxx11]() const (this=0x0) at /home/kyle.cao/workspace/fork/nebula/src/common/datatypes/Value.cpp:1709 #1 0x0000000003880266 in nebula::operator

> not sure whether it's related to #4424 , which contains two matches. Please describe this issue in detail, I did not get a reproduced statement. Are there some error...

After my verification, it has nothing to do with issue #4424 .

@Sophie-Xie