databendlabs/databend

bug: fuse_snapshot timestamp is not right

Open

#7,951 opened on Sep 29, 2022

View on GitHub
 (1 comment) (1 reaction) (0 assignees)Rust (880 forks)github user discovery
C-buggood first issuestale

Repository metrics

Stars
 (9,314 stars)
PR merge metrics
 (Avg merge 4d 18h) (99 merged PRs in 30d)

Description

Summary

select * from fuse_snapshot('db7861', 't7861') order by timestamp limit 1\G;:

The s3 file info:

image

Contributor guide

Research direction
Investigate the timestamp logic in the fuse snapshot function. Compare the timestamp shown in the query result with the actual file modification time on S3 to identify the discrepancy. Look into how snapshots are created and how their timestamps are assigned.
Tech stack
rust
Domain
databasebackend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
RustSQL
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30