Skip to content
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

Jump to bottom

Add missing methods for API level 720 #116

Open
9 of 12 tasks
KrzysFR opened this issue May 15, 2023 · 0 comments
Open
9 of 12 tasks

Add missing methods for API level 720 #116

KrzysFR opened this issue May 15, 2023 · 0 comments
Labels
api Issues or changes related to the client API native Interop with the native client library

Comments

@KrzysFR
Copy link
Member

KrzysFR commented May 15, 2023 •
edited
Loading

A quick look at the current documentation for 7.2 shows that the following native methods are not implemented currently:

  • fdb_add_network_thread_completion_hook
  • fdb_future_get_key_array
  • fdb_database_open_tenant
  • fdb_database_reboot_worker
  • fdb_database_force_recovery_with_data_loss
  • fdb_database_create_snapshot
  • fdb_database_get_main_thread_busyness
  • fdb_tenant_destroy
  • fdb_tenant_create_transaction
  • fdb_transaction_get_estimated_range_size_bytes
  • fdb_transaction_get_range_split_points
  • fdb_error_predicate

These should be added and exposed in the public API.

The new Tenant API needs probably some special handling because it seems to obsolete the previous solution of using top-level partition with the Directory Layer.
@KrzysFR KrzysFR added api Issues or changes related to the client API native Interop with the native client library labels May 15, 2023
@KrzysFR KrzysFR mentioned this issue May 17, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
api Issues or changes related to the client API native Interop with the native client library
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@KrzysFR