We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Insert data throw error: Error found in optimization stage: The depth of plan tree has exceeded the max 512 level
I deployed nebula with https://github.com/vesoft-inc/nebula-docker-compose. How can I change the limit setting?
The text was updated successfully, but these errors were encountered:
It's controlled by max_plan_depth, but not sure if it's configurable(else, we have to change it and redo the build of nebulagraph).
@jievince , could we add this as a configuration to be reasonable?
#5050
Sorry, something went wrong.
@wey-gu 您好,这个问题我通过分批插入数据解决。目前看来是单次插入数据过多导致。PS:我这里之前是一次插入300条关系数据报错,我改成分三次插入,每次插入100条,现在已经成功。
@terwer 它可能和你的机器配置是有关系的,如果是 HDD 的话,建议每次少量地插入数据。
@terwer 这个 issue 超过一个月没有更新内容了,这边先行关闭了。如果你有任何更新的内容,可以再打开这个 issue 哈。
谢谢你的反馈 😊
update: it's actually already configurable as they are gflags...
This in graphd will help:
--max_plan_depth=2048
No branches or pull requests
Insert data throw error:
Error found in optimization stage: The depth of plan tree has exceeded the max 512 level
I deployed nebula with https://github.com/vesoft-inc/nebula-docker-compose. How can I change the limit setting?
The text was updated successfully, but these errors were encountered: