cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Francisco Bento da Silva Neto (Jira)" <>
Subject [jira] [Updated] (CASSANDRA-16703) Exception thrown by custom QueryHandler constructor is ignored
Date Fri, 02 Jul 2021 12:47:00 GMT


Francisco Bento da Silva Neto updated CASSANDRA-16703:
    Impacts:   (was: None)

> Exception thrown by custom QueryHandler constructor is ignored
> --------------------------------------------------------------
>                 Key: CASSANDRA-16703
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Local/Startup and Shutdown
>            Reporter: Francisco Bento
>            Assignee: Zoltan Ersek
>            Priority: Normal
>         Attachments: 16703-trunk.txt
>          Time Spent: 50m
>  Remaining Estimate: 0h
> When a exception is thrown during the instantiation of the _cassandra.custom_query_handler_class,_
depending on the exception thrown cassandra will simply log an info message and proceed with
the bootstraping with the standard _QueryHandler_ as a fallback measure: [|]
> The end-user will never know if the custom _QueryHandler_ is actually registered or not,
unless he notices the info message on the logs.
> Ideally, the message should be logged as error and JVM should stop as it cannot proceed
according with the user expected configuration.
> *Scenario*:
> In our scenario, we have a custom _QueryHandler_ that receives specific configuration,
and we throw a _ConfigurationException_ at instantiation time in case of any invalid config
value. It is expected that cassandra stop the bootstraping instead of skipping the QH.

This message was sent by Atlassian Jira

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message