Franz Eichhorn
Franz Eichhorn
Adds some system tests that were used to verify expected behavior for issue #369 Won't hurt to have those tests merged
if the group table already exists, it is not checked for copartitioning with the input topics - which is dangerous. This needs to be checked when starting the processor
the processor integration test is unclean and has many commented test cases. Implement them or remove them: https://github.com/lovoo/goka/blob/master/integrationtest/processor_test.go#L227
In most cases, when multiple processors in the same application (system test, in this case), are shut down at the same time by closing the runner-`ctx` - one of them...
in rare cases, topic creation can get delayed, so the topic manager should retry when verifying a topic, like this: ```go func (m *topicManager) getTopicConfigMap(topic string) (map[string]sarama.ConfigEntry, error) { var...
If two views use the same storage folder for any reason: ```error setting up partition table: error building storage: error opening leveldb: resource temporarily unavailable``` That might be confusing, because...
Without running Kafka we have different failure behavior between Processors and Views. Current behavior: * NewView returns an error Intended behavior * NewView succeeds * view.Run returns either an error...
## Work in Progress This is a draft for evaluating the efficiency and consequences of adding (memory) pooling to the goka API. ### How it works When processing messages with...