[rest] Introduce snapshot loading to REST Catalog

[JingsongLi]

Purpose

At present, for REST Catalog, table commits are all sent to the REST server, so it has the opportunity to cache snapshots, which can avoid the computing engine obtaining snapshots through the file system and accelerate the OLAP queries of the computing engine.

This PR introduces:

  /v1/{prefix}/databases/{database}/tables/{table}/snapshot:
    get:
      tags:
        - table
      summary: Get table snapshot
      operationId: getTableSnapshot
      parameters:
        - name: prefix
          in: path
          required: true
          schema:
            type: string
        - name: database
          in: path
          required: true
          schema:
            type: string
        - name: table
          in: path
          required: true
          schema:
            type: string
      responses:
        "200":
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GetTableSnapshotResponse'
        "404":
          description: Resource not found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        "500":
          description: Internal Server Error

And the GetTableSnapshotResponse is:

    GetTableSnapshotResponse:
      type: object
      properties:
        snapshot:
          $ref: '#/components/schemas/Snapshot'

When no snapshot for this table, REST can return 404 with SNAPSHOT ErrorResponseResourceType in NoSuchResourceException.

Tests

API and Format

Documentation

[jerry-024]

+1