Comments (4)
What the bulked versions will return if only a subset of records succeeded?
from skafka.
Also I like the "FF"
versions more because otherwise I think most people will go with sync and don't look for how is it different from produceAsync
. And flattening it is not a big deal if you need meta
from skafka.
I would say that it the expected behaviour is to either produce all records or fail all records.
I think both variants make sense because:
- They better express intent
- They give the user both options
Forcing people to go with double FF creates some confusion to some people, they do not quite understand why it is like it is and they will just flatten anyway. For that, might as well expose a sync method. Async is not that often useful anyway, only if you really want to leverage that ability to "block" waiting for the ack later on in your application.
from skafka.
the expected behaviour is to either produce all records or fail all records.
For that you need to go with transactional producer, which I would not expect from plain produce
Async is not that often useful anyway, only if you really want to leverage that ability to "block" waiting for the ack later on in your application
My experience is quite opposite – I don't need to read meta in my app and the only "recovering" action is logging, which does not require blocking
from skafka.
Related Issues (20)
- consumer.offsetsForTimes - consider using Instant as query types instead of Offset
- add metrics for subscribe with RebalanceListener1
- [Discussion] Derive ToTry timeout based on ConsumerConfig.maxPollInterval
- Document ToTry timeout importance in README
- add logging for subscribe with RebalanceListener1
- Support error handling in RebalanceCallback
- Extract FiberWithBlockingCancel to cats-helper
- Potential StackOverflowError in mapK of RebalanceCallback HOT 1
- Improve documentation HOT 2
- Remove Kafka SASL configuration warnings
- Definition of client.rack at CommonConfig level causes kafka ProducerConfig to complain HOT 1
- Kafka has `KafkaProducer#metrics` - why skafka doesn't expose those metrics?
- Circular dependency between skafka and smetrics HOT 5
- in `1.1.0`, the metrics are not shared
- Incompatible with kafka-clients 3.7.0 due to usage of NoOpConsumerRebalanceListener
- Add sbt-version-policy
- Please provide a way to send "tombstone" message HOT 1
- Improve configuration for producer and consumer regarding bytes HOT 1
- Consumer.poll metrics do not work in case of assign/seek flow
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from skafka.