This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Child pages
  • KIP-216: IQ should throw different exceptions for different errors
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Working In Process

Status

Current state[One of "Under Discussion", "Accepted", "Rejected"]

Discussion thread: here

JIRA KAFKA-5876 - Getting issue details... STATUS

Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).

Motivation

As the moment the IQ is only thrown InvalidStateStoreException for all errors. That means we cannot handle different types of errors. We should throw different exceptions for different types.

Proposed Changes

Add two new exception class for the IQ state store errors:

  • org.apache.kafka.streams.errors.StateStoreMigratedException

     

  • org.apache.kafka.streams.errors.StateStoreClosedException

StateStoreMigratedException used in the QueryableStoreProvider, StreamThreadStateStoreProvider and WrappingStoreProvider. The state store must be rediscovered when state store was migrated. The user can catch StateStoreMigratedException and wait until the store recreation finished.

StateStoreClosedException use for internal 

 

 

 

Compatibility, Deprecation, and Migration Plan

  • Because no classes will be removed, this change will be fully backward.

Rejected Alternatives

TBD


  • No labels