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
One of the frustrating problems I've been running into is that if I
have "print statements" in code called by my mapper/reducer this will
break the pipe used by my streaming job.
It seems like a simple change to dumbo can fix this.
In core.py change
typedbytes.PairedOutput(sys.stdout).writes(outputs)
to
typedbytes.PairedOutput(sys.stdout).writes(outputs)
This way all we have to do is redirect stdout to stderr and extraneous
print statements will no longer cause problems.
I've tried this out and it seems to work for me.
The text was updated successfully, but these errors were encountered:
One of the frustrating problems I've been running into is that if I
have "print statements" in code called by my mapper/reducer this will
break the pipe used by my streaming job.
It seems like a simple change to dumbo can fix this.
In core.py change
typedbytes.PairedOutput(sys.stdout).writes(outputs)
to
typedbytes.PairedOutput(sys.stdout).writes(outputs)
This way all we have to do is redirect stdout to stderr and extraneous
print statements will no longer cause problems.
I've tried this out and it seems to work for me.
The text was updated successfully, but these errors were encountered: