[
https://issues.apache.org/jira/browse/KAFKA-9071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16985675#comment-16985675
]
Matthias J. Sax edited comment on KAFKA-9071 at 12/1/19 8:45 PM:
-----------------------------------------------------------------
[~despondency], thanks for your interest. Just a quick clarification: you are
not a _committer_ as this term has a special meaning in the Apache world
([https://www.apache.org/foundation/how-it-works.html#committers]). If you are
interested, you can find the list of Kafka committers and PMC members on the
project web page: [https://kafka.apache.org/committers]
However, I added you to the list of _contributors_
([https://www.apache.org/foundation/how-it-works.html#developers]) on Jira, and
you can now self-assign tickets. Please check out
[https://kafka.apache.org/contributing] to get started.
Please open a PR against `trunk` and the committer who merges your PR will
cherry-pick it to older branches if required. \cc [~hachikuji] who might be the
best person to review and make a call here.
was (Author: mjsax):
[~despondency], thanks for your interest. Just a quick clarification: you are
not a _committer_ as this term has a special meaning in the Apache world
([https://www.apache.org/foundation/how-it-works.html#committers]). If you are
interested, you can find the list of Kafka committers and PMC members on the
project web page: [https://kafka.apache.org/committers]
However, I added you to the list of _contributors_
([https://www.apache.org/foundation/how-it-works.html#developers]) on Jira, and
you can now self-assign tickets.
Please open a PR against `trunk` and the committer who merges your PR will
cherry-pick it to older branches if required. \cc [~hachikuji] who might be the
best person to review and make a call here.
> transactional.id.expiration.ms config value should be implemented as a Long
> ---------------------------------------------------------------------------
>
> Key: KAFKA-9071
> URL: https://issues.apache.org/jira/browse/KAFKA-9071
> Project: Kafka
> Issue Type: Improvement
> Components: config
> Affects Versions: 2.3.0
> Reporter: Joost van de Wijgerd
> Priority: Major
>
> Currently the value of this config parameter is limited to MAX_INT
> effectively limiting the transactional id expiration to ~ 25 days. This is
> causing some issues for us on our Acceptance environment (which is not used
> that often / heavily) where our transactional services will start failing
> because if this issue.
> I believe best practice for millisecond values should be to implement them as
> a Long and not as an Integer
> this is currently the max value: transactional.id.expiration.ms=2147483647
> while I would like to set it to: transactional.id.expiration.ms=31540000000
> (i.e. 1 year)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
