KAFKA-18026: KIP-1112, document new config and update the Streams upgrade guide #17906
Conversation
| </tr> | ||
| <tr> | ||
| <td>2.2.1 and<br>2.3.x and<br>2.4.x and<br>2.5.x and<br>2.6.x and<br>2.7.x and<br>2.8.x and<br>3.0.x and<br>3.1.x and<br>3.2.x and<br>3.3.x and<br>3.4.x and<br>3.5.x and<br>3.6.x and<br>3.7.x</td> | ||
| <td>2.2.1 and<br>2.3.x and<br>2.4.x and<br>2.5.x and<br>2.6.x and<br>2.7.x and<br>2.8.x and<br>3.0.x and<br>3.1.x and<br>3.2.x and<br>3.3.x and<br>3.4.x and<br>3.5.x and<br>3.6.x and<br>3.7.x and<br>3.8.x and<br>3.9.x</td> | ||
| <td></td> | ||
| <td></td> | ||
| <td>compatible; requires message format 0.11 or higher;<br>enabling exactly-once v2 requires 2.4.x or higher</td> |
There was a problem hiding this comment.
@mjsax is this right? I always thought eosv2 needed brokers to be 2.5 or higher, not 2.4. Am I misremembering this or is the matrix wrong?
| </tr> | ||
| <tr> | ||
| <td>0.10.0.x</td> | ||
| <td>compatible</td> | ||
| <td>compatible</td> | ||
| <td>compatible</td> | ||
| <td>compatible</td> |
There was a problem hiding this comment.
@ijuma just to confirm my reading of KIP-896, the change only affects older clients compatibility with newer brokers, not the other way around, right? In other words a 0.11 client could still run against a 4.0 broker?
There was a problem hiding this comment.
In other words a 0.11 client could still run against a 4.0 broker?
I don't think so. According to KIP-896:
Users relying on clients not included in this document will have to ensure they are using a version that does not rely on protocol API versions that are being removed as part of this proposal.
This means that broker version 4.x can only communicate with clients version 2.1 and above.
This PR covers all the docs for KIP-1112, including the new config and a note about the new APIs in the 4.0 section of the upgrade guide.
This also fixes/updates some unrelated parts of the upgrade guide that were out-of-date, such as the broker compatibility matrix