[
https://issues.apache.org/jira/browse/KAFKA-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15323697#comment-15323697
]
Peter Davis commented on KAFKA-2934:
------------------------------------
After upgrading to 0.10, discovered that this fix causes
`offset.storage.file.filename` to be a *required* property, even if a
FileOffsetBackingStore is not used. We are consuming from JMS (which has no
need to store offsets as acknowledged messages are removed from the source) so
we are using a MemoryOffsetBackingStore.
https://github.com/apache/kafka/pull/734 argues there are only two sensible
choices for a backing store but I think my use case shows that is not true!
Would you be willing to revisit the pull request to make the offset backing
store class configurable, and make the file optional?
> Offset storage file configuration in Connect standalone mode is not included
> in StandaloneConfig
> ------------------------------------------------------------------------------------------------
>
> Key: KAFKA-2934
> URL: https://issues.apache.org/jira/browse/KAFKA-2934
> Project: Kafka
> Issue Type: Bug
> Components: KafkaConnect
> Affects Versions: 0.9.0.0
> Reporter: Ewen Cheslack-Postava
> Assignee: Ewen Cheslack-Postava
> Fix For: 0.10.0.0
>
>
> The config is coded directly in FileOffsetBackingStore rather than being
> listed (and validated) in StandaloneConfig. This also means it wouldn't be
> included if we autogenerated docs from the config classes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
