You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When writing data using RowInsertRequest, if the semantic of the RowInsertRequest schema does not match the table structure, the table structure semantic type is preferred.
Now it returns InvalidRequestSnafu error here Could this be optimized by adding a semantic representation that follows the original table structure.
Or maybe we need to get the table schema when building the RowInsertRequest in log writing API via json.
Implementation challenges
No response
The text was updated successfully, but these errors were encountered:
What type of enhancement is this?
API improvement
What does the enhancement do?
When writing data using RowInsertRequest, if the semantic of the RowInsertRequest schema does not match the table structure, the table structure semantic type is preferred.
Now it returns
InvalidRequestSnafu
error here Could this be optimized by adding a semantic representation that follows the original table structure.Or maybe we need to get the table schema when building the RowInsertRequest in log writing API via json.
Implementation challenges
No response
The text was updated successfully, but these errors were encountered: