[jira] [Commented] (KAFKA-9713) Remove BufferExhausedException
[
https://issues.apache.org/jira/browse/KAFKA-9713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071011#comment-17071011
]
ASF GitHub Bot commented on KAFKA-9713:
---
bdbyrne commented on pull request #8288: KAFKA-9713: Remove dead
BufferExhaustedException, which was deprecate…
URL: https://github.com/apache/kafka/pull/8288
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Remove BufferExhausedException
> --
>
> Key: KAFKA-9713
> URL: https://issues.apache.org/jira/browse/KAFKA-9713
> Project: Kafka
> Issue Type: Task
> Components: producer
>Reporter: Brian Byrne
>Priority: Trivial
>
> BufferExhaustedException was deprecated in 0.9.0.0, and the corresponding
> block.on.buffer.full property has since been removed. The exception should
> follow.
> {quote}Deprecations in 0.9.0.0
> The producer config block.on.buffer.full has been deprecated and will be
> removed in future release. Currently its default value has been changed to
> false. The KafkaProducer will no longer throw BufferExhaustedException but
> instead will use max.block.ms value to block, after which it will throw a
> TimeoutException. If block.on.buffer.full property is set to true explicitly,
> it will set the max.block.ms to Long.MAX_VALUE and metadata.fetch.timeout.ms
> will not be honoured{quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (KAFKA-9713) Remove BufferExhausedException
[
https://issues.apache.org/jira/browse/KAFKA-9713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17070049#comment-17070049
]
Sönke Liebau commented on KAFKA-9713:
-
Is anybody still working on this?
> Remove BufferExhausedException
> --
>
> Key: KAFKA-9713
> URL: https://issues.apache.org/jira/browse/KAFKA-9713
> Project: Kafka
> Issue Type: Task
> Components: producer
>Reporter: Brian Byrne
>Priority: Trivial
>
> BufferExhaustedException was deprecated in 0.9.0.0, and the corresponding
> block.on.buffer.full property has since been removed. The exception should
> follow.
> {quote}Deprecations in 0.9.0.0
> The producer config block.on.buffer.full has been deprecated and will be
> removed in future release. Currently its default value has been changed to
> false. The KafkaProducer will no longer throw BufferExhaustedException but
> instead will use max.block.ms value to block, after which it will throw a
> TimeoutException. If block.on.buffer.full property is set to true explicitly,
> it will set the max.block.ms to Long.MAX_VALUE and metadata.fetch.timeout.ms
> will not be honoured{quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (KAFKA-9713) Remove BufferExhausedException
[
https://issues.apache.org/jira/browse/KAFKA-9713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17069457#comment-17069457
]
Sönke Liebau commented on KAFKA-9713:
-
As [~ijuma] said in the comments to the pull request, there is already an issue
that predates this one (KAFKA-3720) that has seen a few discussions around
this. I think that issue should be used for further discussions.
Also, BufferExhaustedException is part of the public API and has not been
deprecated yet as far as I can tell, so should not simply be removed.
> Remove BufferExhausedException
> --
>
> Key: KAFKA-9713
> URL: https://issues.apache.org/jira/browse/KAFKA-9713
> Project: Kafka
> Issue Type: Task
> Components: producer
>Reporter: Brian Byrne
>Priority: Trivial
>
> BufferExhaustedException was deprecated in 0.9.0.0, and the corresponding
> block.on.buffer.full property has since been removed. The exception should
> follow.
> {quote}Deprecations in 0.9.0.0
> The producer config block.on.buffer.full has been deprecated and will be
> removed in future release. Currently its default value has been changed to
> false. The KafkaProducer will no longer throw BufferExhaustedException but
> instead will use max.block.ms value to block, after which it will throw a
> TimeoutException. If block.on.buffer.full property is set to true explicitly,
> it will set the max.block.ms to Long.MAX_VALUE and metadata.fetch.timeout.ms
> will not be honoured{quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (KAFKA-9713) Remove BufferExhausedException
[
https://issues.apache.org/jira/browse/KAFKA-9713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17058228#comment-17058228
]
ASF GitHub Bot commented on KAFKA-9713:
---
bdbyrne commented on pull request #8288: KAFKA-9713: Remove dead
BufferExhaustedException, which was deprecate…
URL: https://github.com/apache/kafka/pull/8288
…d in 0.9.0.0.
### Committer Checklist (excluded from commit message)
- [ ] Verify design and implementation
- [ ] Verify test coverage and CI build status
- [ ] Verify documentation (including upgrade notes)
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Remove BufferExhausedException
> --
>
> Key: KAFKA-9713
> URL: https://issues.apache.org/jira/browse/KAFKA-9713
> Project: Kafka
> Issue Type: Task
> Components: producer
>Reporter: Brian Byrne
>Priority: Trivial
>
> BufferExhaustedException was deprecated in 0.9.0.0, and the corresponding
> block.on.buffer.full property has since been removed. The exception should
> follow.
> {quote}Deprecations in 0.9.0.0
> The producer config block.on.buffer.full has been deprecated and will be
> removed in future release. Currently its default value has been changed to
> false. The KafkaProducer will no longer throw BufferExhaustedException but
> instead will use max.block.ms value to block, after which it will throw a
> TimeoutException. If block.on.buffer.full property is set to true explicitly,
> it will set the max.block.ms to Long.MAX_VALUE and metadata.fetch.timeout.ms
> will not be honoured{quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
