-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
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
Import Error #1316
Comments
@jievince Thanks for your kindly advice! I know the config file format is .yaml, but .yaml file can't upload to this issue, so I change its format. But actually I run it in a correct formal like this... |
some possible solutions: 1 check logcan you paste some log message: 2 check schemathe Can you run the nebula console to verify your schema is correct.
and
to make sure the csv file, the 3 wechat (weixin)You are welcome to add wechat friend |
Thank you for your report. |
Hi @ouzensang , I have checked your configuration file and don't find any syntax errors. So, I guess the problem you are experiencing should be that the order of the props of the schema in configuration file is inconsistent with the order of the data columns in the csv file. |
@whitewum Thanks for your kindly reply! :)
When I first read the doc of nebula-importer, I can't understand the preparation work "Schema is created" whether means I need to create this schema in Nebula shell first, so I didn't create it.
I even change the order of data file in the file, but the same error still exists. =.= |
1. Sorry for the inconvenient.There might be some new changes in the nebula-importer (or the configuration and sample files). So @yixinglu @wilsonyou please check them again ( the code, the md, the csv, etc). 2. possible solutionto open log:
This will help to provide nebula-graphd.LOG. to close log
can you try to import the Answers to your questions:
Yes. there are some reserved keywords to name an attribute. But the namings in your
in your 1.Whether the identified id of data need to be defined in the schema or config file. Actually, I didn't define it. we call identified id as In the Nebula shell schema definition, yes. I must create the schema before you write any data. In the config file: a bit complicated (depending on the csv header) P. S .We're working on a web UI to improve the importer progress. The config.yaml and command line are quite error-prone. I hope the web UI will help for the beginners. You are welcome to contact us by https://user-images.githubusercontent.com/38887077/67449282-4362b300-f64c-11e9-878f-7efc373e5e55.jpg and https://nebulagraph.slack.com/?redir=%2Farchives%2FDJQC9P0H5%2Fp1557815158000200 |
@whitewum Thanks for your help! :) |
@ouzensang Please refer to the following link which provides step-by-step guide to import csv files: |
BTW,can you star Nebula if you like it. :) |
@wilsonyou Thanks for your kindly help! |
@whitewum No problem! I have solved my problem successfully! Thank you again! :) |
You are welcome to contact us for any questions. |
@ouzensang No problem. Glad to hear that you made it! Congratulations! |
Co-authored-by: Sophie <84560950+Sophie-Xie@users.noreply.github.com>
Describe the bug(must be provided)
I deploy Nebula on a cluster of 3 machines(Centos7), when I import data from csv by using https://github.com/vesoft-inc/nebula-importer. I met some error info, but I can't find any solution to solve it.
Your Environments(must be provided)
How To Reproduce(must be provided)
Steps to reproduce the behavior:
Expected behavior
Import csv files successfully
Additional context
![image](https://user-images.githubusercontent.com/30515579/69410766-a5dfc980-0d46-11ea-836f-b6f97aa9d113.png)
My config file:
config.txt
My command:
go run importer.go --config ../example/config.txt
My error:
The text was updated successfully, but these errors were encountered: