goranc

Tested with 3.2 version of nebula-importer and behavior is the same, after some time session is dropped. Here are timeouts and interesting graphd config lines used on cluster ``` #...

Just thinking about nebula-go driver used in importer, it is 3.0, should it be 3.2 according to compatibility list ?

Just to put info here after discussion on Slack channel. You can use NULL value instead of standard \N in CSV file to be able to import it into Nebula.

Maybe it can be just marked as deleted, to not show history records for new runs with the same name, but with a flag/switch to show history, to see what...

I've tried with latest version and it seams that it is working more stable. I have workaround with python wrapper which detects stall and restarts loader, but that shouldn't happen...

Yes, it is just control script which monitor responses from main script about data processing progress, and restarts loader if no progress is detected.

I'll try to use new 4.0 version of nebula-importer and if there is still issue, will open new issue report. Let's close this one.

Should I open a new one or can we list another one here :) - When I use a filter for schema tables from the source peer select all should...