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
FileSource InvalidSourceTap Race Condition #1539
Comments
Yeah here's a small repro, which can be run in non-strict Hdfs mode. This overrides validateTaps to simulate the case that one of the paths became usable. The effect is amplified for Twitter because our internal source definitions can trigger this in strict mode as well. import com.twitter.scalding.source._
val input = new FixedTypedText[String](TypedText.TAB, "foo_bad_path") { override def validateTaps(mode: Mode): Unit = {} }
TypedPipe.from(input).write(NullSink)
|
Whoa, stackoverflow. That should never happen right? Why the infinite loop? |
We've been kind of tackling this internally, but basically |
This is fixed right? |
@isnotinvain Yes it is fixed to my knowledge. Next time I will use "Fixes #..." |
FileSoure.createHdfsReadTap
, when strict mode isfalse
and there are no good paths, will create anInvalidSourceTap
.FileSource.validateTaps
, if a good path has appeared since.createHdfsReadTap
, will not throw. This sounds like a problem, albeit one without using strict mode.The text was updated successfully, but these errors were encountered: