ragflow

mirror of https://github.com/infiniflow/ragflow.git synced 2026-06-29 23:41:12 +08:00

Files

euvre 9bd53ce675 fix: return full record in get_ingestion_log (#16120 )

### What problem does this PR solve?

The `get_ingestion_log` endpoint (both Python
`dataset_api_service.get_ingestion_log` and Go
`DatasetService.GetIngestionLog`) was returning only the
**dataset-level** field set, which omits critical fields such as `dsl`,
`document_id`, `parser_id`, `document_name`, `pipeline_id`, etc.

This caused the front-end **dataflow-result page** to be unable to
render the pipeline timeline and chunks when viewing a single ingestion
log, regardless of whether the log was a dataset-level operation
(graph/raptor/mindmap) or a per-file parse.

### Background

`PipelineOperationLogService` provides two field sets:

| Method | Fields |
|---|---|
| `get_dataset_logs_fields` | Minimal set (progress, status, timestamps,
etc.) |
| `get_file_logs_fields` | Superset — includes `document_id`, `dsl`,
`parser_id`, `document_name`, `pipeline_id`, … |

When listing logs, the API correctly distinguishes dataset-level vs
file-level logs and uses the appropriate converter. However, when
**fetching a single log by ID**, both the Python and Go implementations
were hardcoded to the dataset-level set, dropping the extra fields that
the front-end needs.

2026-06-17 13:03:51 +08:00

auth

Fix: JWT algorithm-confusion in OIDC ID token verification (#15181 )

2026-05-29 19:37:01 +08:00

restful_apis

Refactor: rename /chat_channels to /chat-channels (#16099 )

2026-06-16 19:15:43 +08:00

services

fix: return full record in get_ingestion_log (#16120 )

2026-06-17 13:03:51 +08:00

__init__.py

Fix: consolidate beta auth (#15581 )