Open jamesrgrinter opened 8 years ago
You have solved this problem?
the work around is to increase the polling time out. I agree that it should not be an error
On Thu, Jan 19, 2017 at 2:49 AM, Chris AuYeung notifications@github.com wrote:
You have solved this problem?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/caroljmcdonald/mapr-streams-sparkstreaming-hbase/issues/1#issuecomment-273704215, or mute the thread https://github.com/notifications/unsubscribe-auth/ADMEZJ_mflfQmkAvtqhthSFXNCiOXltoks5rTxWDgaJpZM4Jbt7e .
After updating the version of mapr-spark in the MapR 5.1.0 GA Sandbox from v1.5.2 to v1.6.1.201607242143, the Scala-based Spark-streaming consumers no longer run.
I've also tried applying the MapR 5.1.0 June 2016 Patch, but that hasn't made a difference.
Here's what I get:
I don't understand why an assertion was added in MapR's 1.6.1 version of KafkaRDD.scala.fetchBatch (seems to have come with a commit for MAPR-23854)- with my limited Kafka/MapR streams knowledge it seems plausible for a read to return 0 bytes.