Wey Gu
**Please check the FAQ documentation before raising an issue** **Describe the bug (__required__)** reported via https://discuss.nebula-graph.com.cn/t/topic/8487/37?u=wey , `boost::filesystem::status()` not implemented was encountered during meta boot. maybe during `boost::filesystem::exists` in follow...
This is an issue talked about in WeChat Group:Earth, synced msg was pasted in the end of the issue. It seems in current idle-release session mechanism was monitored and triggered...
Now it's actually scanning all data for the second MATCH, this is being used now in text2cypher to get schema. ``` (root@nebula) [basketballplayer]> profile MATCH ()-[e:follow]->() WITH e limit 1...
as titled. - [ ] plain n.team.name condition - [ ] AND condition example: ``` (root@nebula) [demo_basketballplayer]> match (n:team) where n.team.name == "a" return n [ERROR (-1005)]: Error found in...
This is needed in some cases i.e. support nebulagraph query in Langchain. From the application layer, sometimes we could leverage meta-client to do so but it's not applicable for all...
As @xs2tarunkukreja helped trigger in https://github.com/vesoft-inc/nebula/discussions/5582 , such optimization rule could be improved to passthrough. `MATCH (i)-[e]->(o) where id(i) == 'foo' or id(o) == 'bar' return e;` See: ``` (root@nebula)...
It seems now it's not reflected in the logs.(assume it's in k8s, where log could be written when data disk full) https://discuss.nebula-graph.com.cn/t/topic/12662
As titled, is it just me? Thanks!
maybe with https://github.com/apache/incubator-opendal (Go binding not yet ready though)