Open BenoitRanque opened 2 years ago
When browsing data from the console data tab, the /v1/query api is used to fetch and update rows.
/v1/query
This is a problem as this api is undocumented, which can be confusing. The endpoint is also documented as being deprecated.
Note this is not about the use of run_sql used for things like fetching information on database structure. That uses the /v2/query api.
run_sql
/v2/query
The use of the api should be deprecated and the graphql api used instead.
If these APIs are to be used in the long term, they should be documented.
We're planning on moving console's browse rows tab to work off the /graphql endpoint going forward. This work is already in progress, will update this thread soon!
/graphql
Is your proposal related to a problem?
When browsing data from the console data tab, the
/v1/query
api is used to fetch and update rows.This is a problem as this api is undocumented, which can be confusing. The endpoint is also documented as being deprecated.
Note this is not about the use of
run_sql
used for things like fetching information on database structure. That uses the/v2/query
api.Describe the solution you'd like
The use of the api should be deprecated and the graphql api used instead.
Describe alternatives you've considered
If these APIs are to be used in the long term, they should be documented.
8997 proposes the opposite approach: document these APIs and make them official.