New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kafka: partition id is not always set in fetch response error scenarios #126
Labels
Comments
mmaslankaprv
added a commit
to mmaslankaprv/redpanda
that referenced
this issue
Nov 19, 2020
When fetch response partition error is sent we have to set partition id in the response or client will treat it as unknown partition. Fixes: redpanda-data#126 Signed-off-by: Michal Maslanka <michal@vectorized.io>
mmaslankaprv
added a commit
to mmaslankaprv/redpanda
that referenced
this issue
Nov 20, 2020
When fetch response partition error is sent we have to set partition id in the response or client will treat it as unknown partition. Fixes: redpanda-data#126 Signed-off-by: Michal Maslanka <michal@vectorized.io>
mmaslankaprv
added a commit
to mmaslankaprv/redpanda
that referenced
this issue
Nov 20, 2020
When fetch response partition error is sent we have to set partition id in the response or client will treat it as unknown partition. Fixes: redpanda-data#126 Signed-off-by: Michal Maslanka <michal@vectorized.io>
mmaslankaprv
added a commit
to mmaslankaprv/redpanda
that referenced
this issue
Nov 22, 2020
When fetch response partition error is sent we have to set partition id in the response or client will treat it as unknown partition. Fixes: redpanda-data#126 Signed-off-by: Michal Maslanka <michal@vectorized.io>
mmaslankaprv
added a commit
to mmaslankaprv/redpanda
that referenced
this issue
Nov 23, 2020
When fetch response partition error is sent we have to set partition id in the response or client will treat it as unknown partition. Fixes: redpanda-data#126 Signed-off-by: Michal Maslanka <michal@vectorized.io>
mmaslankaprv
added a commit
to mmaslankaprv/redpanda
that referenced
this issue
Nov 24, 2020
When fetch response partition error is sent we have to set partition id in the response or client will treat it as unknown partition. Fixes: redpanda-data#126 Signed-off-by: Michal Maslanka <michal@vectorized.io>
mmaslankaprv
added a commit
to mmaslankaprv/redpanda
that referenced
this issue
Nov 24, 2020
When fetch response partition error is sent we have to set partition id in the response or client will treat it as unknown partition. Fixes: redpanda-data#126 Signed-off-by: Michal Maslanka <michal@vectorized.io>
mmaslankaprv
added a commit
to mmaslankaprv/redpanda
that referenced
this issue
Nov 24, 2020
When fetch response partition error is sent we have to set partition id in the response or client will treat it as unknown partition. Fixes: redpanda-data#126 Signed-off-by: Michal Maslanka <michal@vectorized.io>
andresaristizabal
pushed a commit
to andresaristizabal/redpanda
that referenced
this issue
Nov 26, 2020
When fetch response partition error is sent we have to set partition id in the response or client will treat it as unknown partition. Fixes: redpanda-data#126 Signed-off-by: Michal Maslanka <michal@vectorized.io>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: