Skip to content
This repository has been archived by the owner on Jun 9, 2020. It is now read-only.

Easier way for multi node types? #4

Closed
bemurphy opened this issue Aug 19, 2012 · 3 comments
Closed

Easier way for multi node types? #4

bemurphy opened this issue Aug 19, 2012 · 3 comments

Comments

@bemurphy
Copy link

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?

@jexp
Copy link
Owner

jexp commented Aug 19, 2012

Just put them all into one nodes file, you can have any attribute not having a value in a certain row, it will then just be skipped.

@jexp
Copy link
Owner

jexp commented Aug 19, 2012

Can you share your setup for movielens anywhere? E.g. in a blog post or github project?

Thanks!

@bemurphy
Copy link
Author

Thanks for the answer, that's helpful.

Once I've sorted my way though things, I'll post a gist or repo. I'll let you know!

@jexp jexp closed this as completed Nov 29, 2012
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants