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

[Feature] Specify table API which Rest catalog needs support #4715

Open
2 tasks done
jerry-024 opened this issue Dec 16, 2024 · 8 comments
Open
2 tasks done

[Feature] Specify table API which Rest catalog needs support #4715

jerry-024 opened this issue Dec 16, 2024 · 8 comments
Labels
enhancement New feature or request

Comments

@jerry-024
Copy link
Contributor

jerry-024 commented Dec 16, 2024

Search before asking

  • I searched in the issues and found nothing similar.

Motivation

Specify table API which Rest catalog needs support.

Solution

I have searched other catalog APIs like iceberg Rest catalog and unity catalog,

  • the APIs we need support with are
    • getTable
    • listTables
    • dropTable
    • createTable
    • renameTable
    • alterTable
    • getTableLocation: as it only use when clone table
  • need discuss
    • tableExists: as we needn't use this API in common so getTable is enough

Other catalog APIs

iceberg
  • listTables
  • createTable
  • tableExists
  • dropTable
  • renameTable
  • loadTable
  • invalidateTable
  • registerTable
unity catalog
  • listTables
  • getTable
  • deleteTable
  • tableExists

Are you willing to submit a PR?

  • I'm willing to submit a PR!
@jerry-024 jerry-024 added the enhancement New feature or request label Dec 16, 2024
@jerry-024 jerry-024 changed the title [Feature] Table API which Rest catalog need support [Feature] Specify table API which Rest catalog needs support Dec 16, 2024
@adrian-wang
Copy link
Contributor

How about getTables to batch get tables to avoid network communication overhead?

@jerry-024
Copy link
Contributor Author

What's the different between listTables and getTables?

@sundapeng
Copy link
Member

Are there any plans to support the snapshot, branch, or tag API ?

@JingsongLi
Copy link
Contributor

Are there any plans to support the snapshot, branch, or tag API ?

Good point, these need some refactor, we will discuss them in follow issues.

@JingsongLi
Copy link
Contributor

How about getTables to batch get tables to avoid network communication overhead?

@adrian-wang Do you know which scenarios need this batch API? I cannot see it in computation engines.

@sundapeng
Copy link
Member

Are there any plans to support the snapshot, branch, or tag API ?

Good point, these need some refactor, we will discuss them in follow issues.

I'm looking forward to the discussion.

@sundapeng
Copy link
Member

How about getTables to batch get tables to avoid network communication overhead?

@adrian-wang Do you know which scenarios need this batch API? I cannot see it in computation engines.

@JingsongLi , APIs for tables can optimize certain management scenarios, such as listTables typically returning table names and getTables needing to return full table objects. Multi-table join scenarios may also benefit.

Based on my previous experience, batch APIs for partitions can also significantly improve performance in some queries.

Any thought? @adrian-wang

@adrian-wang
Copy link
Contributor

@sundapeng +1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants