Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal: introducing table functions that export fuse table meta #2946

Closed
1 task done
Tracked by #1780
dantengsky opened this issue Nov 22, 2021 · 2 comments
Closed
1 task done
Tracked by #1780

Proposal: introducing table functions that export fuse table meta #2946

dantengsky opened this issue Nov 22, 2021 · 2 comments
Labels
C-proposal Category: proposal

Comments

@dantengsky
Copy link
Member

dantengsky commented Nov 22, 2021

Summary

introducing system table functions, which export fuse table's segment/block metadata

The "semantics" of this function:

  • grab a snapshot of the given table db_name.tbl_name (by using catalog)
  • list all the segment infors of the given table

about the schema of resultset, use DataType::Struct for nested data structure and Struct::List for map.
EDIT: let's start what flatten table first

later

  • we may use the above function(s) to verify the effect of compaction/GC
  • or even, as the upstream datasource of the distributed GC pipeline

@dantengsky dantengsky added the C-proposal Category: proposal label Nov 22, 2021
@Veeupup
Copy link
Contributor

Veeupup commented Dec 1, 2021

maybe with HTTP api to return json result with segments statistics will be more clear ? Because fuse meta data will have some complicated nested structure which can be described by nested json. @dantengsky

@dantengsky
Copy link
Member Author

addressed by PR #3301

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-proposal Category: proposal
Projects
None yet
Development

No branches or pull requests

2 participants