Harris.Chu
Harris.Chu
why this? console just connect to `FIRST` graph, no need to wait other graphds. prefer a loop like: https://github.com/vesoft-inc/nebula-python/blob/master/tests/docker-compose.yaml
``` for i in `seq 1 60`;do var=`nebula-console -addr graphd0 -port 9669 -u root -p nebula -e 'ADD HOSTS "172.28.2.1":9779,"172.28.2.2":9779,"172.28.2.3":9779;'`; if [[ $$? == 0 ]];then break; fi; sleep 1;...
BTW v3 is the latest version for v3.x. i.e. it's same with v3.0.1 now. maybe we could just create a v3 branch
hold on nebula-console is not consistent with nebula. i.e. nebula is v3.0.2 but nebula-console won't release v3.0.2.
> seems it's ok
+1 for index id
for issue 2, refer https://github.com/vesoft-inc/nebula/issues/3958 we have two times: * ::time(NULL); * time::WallClock::fastNowInSec(); `now()` uses the first, and `checkDataExpiredForTTL` uses the second. how to reduce: 1. start storage 2. change...
BTW, could we make the checkpoint automatically? and then no need for users to backup the original data manually. cc @randomJoe211
in neo4j 
you should re-generate the certs, you could refer https://github.com/vesoft-inc/nebula-go/tree/master/nebula-docker-compose/secrets for generation and https://github.com/vesoft-inc/nebula-go/blob/master/nebula-docker-compose/docker-compose-ssl.yaml, https://github.com/vesoft-inc/nebula-go/blob/master/nebula-docker-compose/.env for usage in nebula