[
https://issues.apache.org/jira/browse/SAMZA-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14018941#comment-14018941
]
Martin Kleppmann commented on SAMZA-224:
----------------------------------------
bq. if samza.offset.default resolves to an offset that's null, we use the
"upcoming" offset (which will always be non-null) instead
Is it really safe to assume that? KafkaSystemAdmin leaves "upcoming" at 0 if
the topic is empty, but the [javadocs for
SystemStreamPartitionMetadata|http://samza.incubator.apache.org/learn/documentation/0.7.0/api/javadocs/org/apache/samza/system/SystemStreamMetadata.SystemStreamPartitionMetadata.html#getUpcomingOffset()]
say that "upcoming" should also be null for an empty stream.
bq. Feel free to open a second ticket.
Done: SAMZA-273
> TestStatefulTask.testShouldStartAndRestore fails intermittently
> ---------------------------------------------------------------
>
> Key: SAMZA-224
> URL: https://issues.apache.org/jira/browse/SAMZA-224
> Project: Samza
> Issue Type: Bug
> Components: test
> Affects Versions: 0.6.0
> Reporter: Martin Kleppmann
> Assignee: Martin Kleppmann
> Fix For: 0.7.0
>
>
> [~closeuris] reported the following issue on SAMZA-185. I'm now
> intermittently seeing this problem too, so I'm opening a new issue for it (as
> I'm not sure the issue has anything to do with the Kafka 0.8.1 upgrade).
> {noformat}
> org.apache.samza.test.integration.TestStatefulTask >
> testShouldStartAndRestore FAILED
> java.lang.AssertionError at TestStatefulTask.scala:356
> 2 tests completed, 1 failed
> :samza-test_2.10:test FAILED
> {noformat}
> Logs provided by Yan (mine look similar):
> Failed tests: http://pastebin.com/3nEDw9jC
> Standard output: http://pastebin.com/20vZbk7c
> Standard error: http://pastebin.com/gU6cTNAr
--
This message was sent by Atlassian JIRA
(v6.2#6252)
