You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 9, 2020. It is now read-only.
Leaving this here because I'm wondering if I'm missing something obvious, plus it might help somebody in the same boat.
I used the importer for pulling in MovieLens data. It's way faster than what I was doing before pumping it in over the wire!
I wanted to have differing properties for users and movies, so the reference line needs to be different. So I parsed the user and movie data into separate node files. The first pass I imported the user nodes with a blank rels file, and then I import the movie nodes with real rels data (I'd calculated the node id with a counter shared across users and movies).
This worked ok left me wondering, is there a better way than this two pass approach with the current implementation?
The text was updated successfully, but these errors were encountered:
Leaving this here because I'm wondering if I'm missing something obvious, plus it might help somebody in the same boat.
I used the importer for pulling in MovieLens data. It's way faster than what I was doing before pumping it in over the wire!
I wanted to have differing properties for users and movies, so the reference line needs to be different. So I parsed the user and movie data into separate node files. The first pass I imported the user nodes with a blank rels file, and then I import the movie nodes with real rels data (I'd calculated the node id with a counter shared across users and movies).
This worked ok left me wondering, is there a better way than this two pass approach with the current implementation?
The text was updated successfully, but these errors were encountered: