-
Notifications
You must be signed in to change notification settings - Fork 1
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
add hotness queries and materializer (#25) #127
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Ignored Deployment
|
a45f75d
to
8e9c764
Compare
8e9c764
to
3f5694a
Compare
08b1d7c
to
62dc1dc
Compare
40a6f88
to
2dd6967
Compare
2dd6967
to
6437ea8
Compare
6437ea8
to
d33f5b4
Compare
d33f5b4
to
3185591
Compare
3185591
to
d8cca76
Compare
d8cca76
to
f00b179
Compare
f00b179
to
755ccd6
Compare
755ccd6
to
dd21faa
Compare
dd21faa
to
c99b044
Compare
c99b044
to
44d85f5
Compare
also reformatted some sql
44d85f5
to
c79e441
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So this strategy looks good - but I do wonder if scoring the posts in Go rather than SQL might give us more flexibility in adding new Algos - but I can equally see this sucking from a perf aspect. My gut feeling is to run with what you've done here and we can always move it to Go in future if we want to.
also reformatted some sql