Skip to content

README.md: Remove stale cass_future_coordinator from limitations #316

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 6, 2025
+2 −9
Merged

README.md: Remove stale cass_future_coordinator from limitations #316

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 2 additions & 9 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -115,7 +115,7 @@ The logging API and implementation are compatible with the C++ driver, for more
As the `tracing` framework is used under the hood to instrument the collection of logs from the Rust driver and the Cpp-Rust wrapper,
the logging level and callback are passed through a custom event subscriber which is globally set as default when `cass_log_set_level` is called.
So, `cass_log_set_level` *must* be called only once as subsequent attempts trying to modify the globally set event subscriber will be ignored.
Also, Rust programs using Cpp-Rust driver under the hood must avoid calling `tracing::subscriber::set_global_default` as this will cause conflicts.
Also, Rust programs using Cpp-Rust driver under the hood must avoid calling `tracing::subscriber::set_global_default` as this will cause conflicts.
Comment on lines 116 to 119
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

did we verify that this tracing::subscriber::set_global_default issue is actually true?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can't remember.

##### Note: The logging configuration must be done before any other driver function is called, otherwise, the default logging callback will be used, and logs will appear on stderr.
Expand Down Expand Up @@ -153,7 +153,7 @@ The driver inherits almost all the features of C/C++ and Rust drivers, such as:

# Limitations

##### Note: This section may be incomplete, so not everything that is unimplemented is mentioned here.
##### Note: This section may be incomplete, so not everything that is unimplemented is mentioned here.

<table>
<thead>
Expand All @@ -170,13 +170,6 @@ The driver inherits almost all the features of C/C++ and Rust drivers, such as:
<td>cass_statement_bind_custom[by_name]</td>
<td>Binding is not implemented for custom types in the Rust driver.</td>
</tr>
<tr>
<td colspan=2 align="center" style="font-weight:bold">Future</td>
</tr>
<tr>
<td>cass_future_coordinator</td>
<td>Unimplemented</td>
</tr>
<tr>
<td colspan=2 align="center" style="font-weight:bold">Collection</td>
</tr>
Expand Down