MeiliSearch/dump
bors[bot] 60018d0fe4
Merge #3343
3343: Extract creation and last updated timestamp for v3 dump r=curquiza a=FrancisMurillo

# Pull Request

## Related issue
Fixes #2988

## What does this PR do?

Inspired by the v4 dump implementation, this extracts the first `createdAt` and last `updatedAt` fields by parsing the task queue.

Questions:
- Should the parsing of the tasks be cached instead of being parsed for every index since it might add a performance penalty?
- I am not sure if the `created_at` and `processed_at` fields are correct 
- Should I assume the data is sorted in some order like with `uuid` or `updateId`? I assumed the list is unordered.
- I was planning to populate my dev instance with data and dump my data. Is there a way to dump with previous versions?

## PR checklist
Please check if your PR fulfills the following requirements:
- [x] Does this PR fix an existing issue, or have you listed the changes applied in the PR description (and why they are needed)?
- [x] Have you read the contributing guidelines?
- [x] Have you made sure that the title is accurate and descriptive of the changes?

Thank you so much for contributing to Meilisearch!


Co-authored-by: Francis Murillo <evacuee.overlap.vs3op@aleeas.com>
2023-01-19 16:14:21 +00:00
..
src Merge #3343 2023-01-19 16:14:21 +00:00
tests/assets Add v1 reader 2022-12-01 14:03:15 +01:00
Cargo.toml Update version for the next release (v1.0.0) in Cargo.toml files 2022-12-08 12:20:17 +00:00
README.md remove an unused file 2022-10-27 11:34:02 +02:00

dump
├── indexes
│   ├── cattos
│   │   ├── documents.jsonl
│   │   └── settings.json
│   └── doggos
│       ├── documents.jsonl
│       └── settings.json
├── instance-uid.uuid
├── keys.jsonl
├── metadata.json
└── tasks
    ├── update_files
    │   └── [task_id].jsonl
    └── queue.jsonl