euvre f3b7d55a1e fix: handle Infinity table-not-exist error (3022) in update() methods (#14153) ...

### What problem does this PR solve?

## Summary

Closes #6102

When using Infinity as the document store engine (GPU version), calling
`update()` on a non-existent table throws an unhandled
`InfinityException` with error code 3022 (`TABLE_NOT_EXIST`). This
causes users to see a raw "3022" error when clicking on a parsed
document.

## Root Cause

The `update()` methods in both `rag/utils/infinity_conn.py` and
`memory/utils/infinity_conn.py` call `db_instance.get_table(table_name)`
without catching `InfinityException`. In contrast, other CRUD methods
(`insert`, `delete`, `search`) all handle this exception gracefully:

| Method   | Handles table-not-exist? | Behavior |
|----------|--------------------------|----------|
| `insert`  | ✅ Yes | Auto-creates the table |
| `search`  | ✅ Yes | Skips the table |
| `delete`  | ✅ Yes | Returns 0 |
| `update`  | ❌ **No** | Crashes with 3022 |

Additionally, `api/apps/document_app.py` worked around this with a
fragile string match (`"3022" in msg`) to detect the error.

## Changes

- **`rag/utils/infinity_conn.py`**: Catch `InfinityException` in
`update()`. When `TABLE_NOT_EXIST` is detected, log a warning and return
`False` — consistent with `delete()`.
- **`memory/utils/infinity_conn.py`**: Apply the same fix to its
`update()` method.
- **`api/apps/document_app.py`**: Remove the fragile `"3022"`
string-matching workaround. Table-not-exist is now handled by the `if
not ok` path with an improved error message.

### Type of change

- [x] Refactoring

---------

Signed-off-by: noob <yixiao121314@outlook.com>

2026-04-27 11:52:22 +08:00

..

services

fix: strip single quotes from synonym terms to prevent Infinity TokenError (#13969)

2026-04-09 19:10:34 +08:00

utils

fix: handle Infinity table-not-exist error (3022) in update() methods (#14153)

2026-04-27 11:52:22 +08:00

__init__.py

Feat: message manage (#12196)

2025-12-25 21:18:13 +08:00