Setting auto.offset.reset=none causes what happens if no offset is found?

Setting auto.offset.reset=none causes what happens if no offset is found?

• A. Read from the end
• B. Throw exception if no offset is found
• C. Read from the beginning
• D. Use last committed offset

Answer: (B)

When there is no previously committed offset for a partition and auto.offset.reset is set to none, the consumer cannot determine where to start reading. In this situation the consumer will throw an exception to signal that it cannot proceed without an explicit offset. This forces you to handle the situation in code (for example, by seeking to a specific offset or by choosing a different reset policy). Context: auto.offset.reset determines where to start if no offset is found. If you want reading to begin from the beginning or from the end instead of failing, you would set it to earliest or latest. The key idea is that none means do not auto-reset and treat the absence of an offset as an error.

When there is no previously committed offset for a partition and auto.offset.reset is set to none, the consumer cannot determine where to start reading. In this situation the consumer will throw an exception to signal that it cannot proceed without an explicit offset. This forces you to handle the situation in code (for example, by seeking to a specific offset or by choosing a different reset policy).

Context: auto.offset.reset determines where to start if no offset is found. If you want reading to begin from the beginning or from the end instead of failing, you would set it to earliest or latest. The key idea is that none means do not auto-reset and treat the absence of an offset as an error.