You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Enhance documentation and examples for HNSW (JVector) indexing
- Updated references from JVector to HNSW (JVector) across multiple documentation files, including testing guides, examples, and index descriptions.
- Clarified the use of HNSW in vector search examples and improved explanations of indexing performance.
- Adjusted code snippets to reflect best practices for using HNSW (JVector) in various contexts, including schema creation and data import.
- Removed deprecated JSON import examples and streamlined CSV import documentation.
- Ensured consistency in terminology and improved clarity in descriptions of vector search capabilities.
Copy file name to clipboardExpand all lines: bindings/python/docs/api/async_executor.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,18 @@
2
2
3
3
The AsyncExecutor provides low-level async operations for parallel processing, automatic batching, and optimized WAL operations. It offers 3-5x faster bulk inserts compared to sequential operations.
4
4
5
+
!!! tip "Using Context Managers"
6
+
For automatic resource cleanup, prefer using context managers:
7
+
```python
8
+
with arcadedb.create_database("./mydb") as db:
9
+
async_exec = db.async_executor()
10
+
async_exec.set_parallel_level(8)
11
+
# Use for bulk operations...
12
+
async_exec.wait_completion()
13
+
# Database automatically closed
14
+
```
15
+
Examples below show explicit `db.close()` for clarity, but context managers are recommended in production.
The `Importer` class and convenience functions provide high-performance data import capabilities for ArcadeDB. The Java importer supports CSV/TSV and XML. For full-database migrations, use ArcadeDB's native JSONL export/import via the `IMPORT DATABASE file://...` SQL command (see JSONL example below).
3
+
The `Importer` class and convenience functions provide high-performance data import
4
+
capabilities for ArcadeDB. For full-database migrations, use ArcadeDB's native JSONL
5
+
export/import via the `IMPORT DATABASE file://...` SQL command (see JSONL example
6
+
below).
4
7
5
8
## Overview
6
9
7
10
The importer uses streaming parsers for memory efficiency and performs batch transactions (default 1000 records per commit) for optimal performance. It can import data as documents, vertices, or edges depending on your schema needs.
8
11
9
12
**Supported Formats:**
10
-
-**CSV/TSV**: Comma or tab-separated values
11
-
-**XML**: Attribute-focused importer
13
+
-**CSV/TSV**: Comma or tab-separated values (recommended for bulk imports)
12
14
-**ArcadeDB JSONL export/import**: Use `IMPORT DATABASE file://...` via SQL for full database moves (see example)
15
+
-**XML**: Limited support via Java importer (not recommended for production use)
13
16
14
17
## Module Functions
15
18
16
-
Convenience functions for common import tasks without creating an `Importer` instance. These call the underlying Java importer (CSV/TSV, XML) or native SQL for full-database JSONL imports.
19
+
Convenience functions for common import tasks without creating an `Importer` instance.
20
+
These call the underlying Java importer (CSV/TSV) or native SQL for full-database JSONL
Copy file name to clipboardExpand all lines: bindings/python/docs/api/results.md
+11Lines changed: 11 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,17 @@
2
2
3
3
The `ResultSet` and `Result` classes provide Python-friendly interfaces for working with query results from ArcadeDB. They handle iteration, property access, and type conversion automatically.
4
4
5
+
!!! tip "Using Context Managers"
6
+
For automatic resource cleanup, prefer using context managers:
7
+
```python
8
+
with arcadedb.open_database("./mydb") as db:
9
+
result_set = db.query("sql", "SELECT FROM Person WHERE age > 25")
10
+
for result in result_set:
11
+
print(result.get("name"))
12
+
# Database automatically closed
13
+
```
14
+
Examples below show explicit `db.close()` for clarity, but context managers are recommended in production.
15
+
5
16
## Overview
6
17
7
18
When you execute a query, ArcadeDB returns a `ResultSet` that can be iterated to access individual `Result` objects. Each `Result` represents one row/record from your query.
0 commit comments