-
Notifications
You must be signed in to change notification settings - Fork 43
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
Replay Stream Support #51
Comments
@jcodagnone You can see the full thing at https://github.com/Traackr/gnip4j/blob/powertrack-v2/core/src/main/java/com/zaubersoftware/gnip4j/api/impl/PowerTrackV2ReplayUriStrategy.java The empty constructor is for adding/removing Rules, and the one accepting A few questions/options:
|
One other requirement for Replay Streams - when a replay stream finishes it sends a message that looks like (See the docs for more information): {
"info": {
"message": "Replay Request Completed",
"sent": "2016-05-27T22:15:50+00:00",
"activity_count": 8874
}
} when successful and {
"info": {
"message": "Replay Request Completed with Errors",
"sent": "2016-05-27T16:00:02+00:00",
"activity_count": 56333,
"minutes_failed": [
"2013-02-20T00:05:00+00:00",
"2013-02-20T00:06:00+00:00"
]
}
} when there was an error We've used a very naive solution of closing the stream once there is no more content for replay streams, but this could be smarter if it actually deserialized the payload, realized it wasn't an |
Would it make sense to have a ReplayUriStrategy?
Looking at PowerTrack 2.0 Replay, it would mostly be a copy-paste of PowerTrackV2UriStrategy, but with a few changes:
Instead of
it would have something like
The text was updated successfully, but these errors were encountered: