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
Right now the flush function has no way of signaling error. As @pulltab noted the InfluxDB sink flush will loop infinitely without an influxdb to report to, which is... not great. #353 is caused by an inability to signal error upward.
This can be repaired by having Result kicked out of the function, or some other kind of failure.
The text was updated successfully, but these errors were encountered:
As of 0.20.6 ES it's possible for a bulk request to time out,
which we unwrapped on like goofs. This commit removes that
unwrap and fails the flush in the event of a timeout bubbling up.
This resolves#353 and elastic-rs/elastic#286.
Related to #355.
Signed-off-by: Brian L. Troutwine <blt@postmates.com>
blt
pushed a commit
that referenced
this issue
Dec 5, 2017
As of 0.20.6 ES it's possible for a bulk request to time out,
which we unwrapped on like goofs. This commit removes that
unwrap and fails the flush in the event of a timeout bubbling up.
This resolves#353 and elastic-rs/elastic#286.
Related to #355.
Signed-off-by: Brian L. Troutwine <blt@postmates.com>
As of 0.20.6 ES it's possible for a bulk request to time out,
which we unwrapped on like goofs. This commit removes that
unwrap and fails the flush in the event of a timeout bubbling up.
This resolves#353 and elastic-rs/elastic#286.
Related to #355.
Signed-off-by: Brian L. Troutwine <blt@postmates.com>
Right now the flush function has no way of signaling error. As @pulltab noted the InfluxDB sink flush will loop infinitely without an influxdb to report to, which is... not great. #353 is caused by an inability to signal error upward.
This can be repaired by having
Result
kicked out of the function, or some other kind of failure.The text was updated successfully, but these errors were encountered: