Weston Pace 9148cd6d47 feat: page_token / limit to native table_names function. Use async table_names function from sync table_names function (#1059) ...

The synchronous table_names function in python lancedb relies on arrow's
filesystem which behaves slightly differently than object_store. As a
result, the function would not work properly in GCS.

However, the async table_names function uses object_store directly and
thus is accurate. In most cases we can fallback to using the async
table_names function and so this PR does so. The one case we cannot is
if the user is already in an async context (we can't start a new async
event loop). Soon, we can just redirect those users to use the async API
instead of the sync API and so that case will eventually go away. For
now, we fallback to the old behavior.

2024-03-05 08:38:18 -08:00

..

connection.rs

feat: page_token / limit to native table_names function. Use async table_names function from sync table_names function (#1059)

2024-03-05 08:38:18 -08:00

error.rs

feat: more accessible errors (#1025)

2024-03-05 07:57:11 -08:00

lib.rs

feat: port create_table to the async python API and the remote rust API (#1031)

2024-02-29 13:29:29 -08:00

table.rs

feat: add support for add to async python API (#1037)

2024-03-04 09:27:41 -08:00