getChunksMeta

getChunksMeta([chunkPath], [top=1024])

Returns the metadata of specified database chunks on the current data node. If chunkPath is not specified, returns the metadata of all database chunks on the current data node.

top (optional) is a positive number specifying the maximum number of chunks in the output. The default value is 1024. If it is set to -1, the number of returned chunks is not limited.

A table with the following columns:

• site: Alias of the node
• chunkId: The chunk ID
• path: The path to database chunks
• dfsPath: The DFS path to database chunks
• type: The partition type. 0 for file chunk; 1 for tablet chunk.
• flag: Flag for deletion. flag=0: The chunk can be queried and accessed; flag=1: The chunk has been logically marked as deleted and cannot be queried, but it has not been removed from disk.
  • When data is deleted using a delete statement, the corresponding chunk is not removed, so the flag of that chunk in the returned result remains 0.
  • When executing the dropPartition, dropDatabase, or dropTable functions, or the drop statement, the flag of the corresponding chunk will be set to 1. However, once the deletion transaction is completed and flag = 1, the metadata of that chunk will no longer be returned, so results with flag = 1 are usually not visible. To see chunks with flag = 1, getChunksMeta must be executed before the deletion transaction finishes.
• size: The disk space (in bytes) occupied by the file chunk. It returns 0 for tablet chunks. Use the getTabletsMeta function to check the disk space tablet chunk occupies.
• version: the version number
• state: Chunk state.
  • 0 (final state): Transaction has been completed or rolled back.
  • 1 (before-commit state): The transaction is being executed on the chunk, such as writing or deleting data.
  • 2 (after-commit state): The transaction has been committed.
  • 3 (waiting-for-recovery state): When there is a version conflict or data corruption, this state occurs after the data node sends a recovery request to the controller and before the controller initiates the recovery.
  • 4 (in-recovery state): This state occurs after the controller receives the recovery request and initiates the recovery. Upon the completion of recovery, the chunk reverts to the final state (0).
• versionList: version list.
• resolved: Whether the transaction of the chunk is in the commit phase that needs to be resolved. True indicates the transaction is in the resolution phase or needs to be resolved; False indicates the transaction has already completed the resolution phase or it is not required.

if(existsDatabase("dfs://testDB")){
  dropDatabase("dfs://testDB")
}
db=database("dfs://testDB", VALUE, 1..10)

n=1000000
t=table(rand(1..10, n) as id, rand(100.0, n) as x)
db.createPartitionedTable(t, `p1, `id).append!(t)

n=2000000
t=table(rand(1..10, n) as id, rand(100.0, n) as x, rand(100, n) as y)
db.createPartitionedTable(t, `pt2, `id).append!(t)
getChunksMeta("/testDB%");

Related function: getTabletsMeta