[
https://issues.apache.org/jira/browse/CASSANDRA-20053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Semb Wever updated CASSANDRA-20053:
-------------------------------------------
Component/s: Tool/cqlsh
> Consider exposing the ability to select event loops for cqlsh
> -------------------------------------------------------------
>
> Key: CASSANDRA-20053
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20053
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Tool/cqlsh
> Reporter: Bret McGuire
> Priority: Normal
>
> The Python driver currently includes support for [multiple event
> loops|https://docs.datastax.com/en/developer/python-driver/3.29/installation/index.html#supported-event-loops].
> Users can specify a specific event loop by defining the "connection_class"
> param on the Cluster object; if this isn't done a default selection process
> will be performed.
>
> cqlsh doesn't expose the ability to define this property on Cluster objects;
> this prevents users from leveraging other event loops without explicitly
> modifying cqlsh code. This matters in cases where customers see problems
> with a specific event loop selected by the default selection process
> (something we have [seen in the
> wild|https://datastax-oss.atlassian.net/browse/PYTHON-1400]). It also might
> help out Python 3.12 users who wish to specify a specific event loop (since
> the default of asyncore is no longer available to them).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
