-
Notifications
You must be signed in to change notification settings - Fork 127
Closed
Labels
api: bigqueryIssues related to the googleapis/java-bigquery API.Issues related to the googleapis/java-bigquery API.priority: p3Desirable enhancement or fix. May not be included in next release.Desirable enhancement or fix. May not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Description
Thanks for stopping by to let us know something could be better!
PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.
Is your feature request related to a problem? Please describe.
The BigQuery REST API supports the followings fields in its response.
{
"numTimeTravelPhysicalBytes": "23083567",
"numTotalLogicalBytes": "222712206",
"numActiveLogicalBytes": "222712206",
"numLongTermLogicalBytes": "0",
"numTotalPhysicalBytes": "83798234",
"numActivePhysicalBytes": "83798234",
"numLongTermPhysicalBytes": "0"
}
However, the corresponding getters are not available in the JAVA client: com.google.cloud.bigquery.Table
Describe the solution you'd like
Add the above fields in TableInfo
class of the JAVA client.
Describe alternatives you've considered
N/A
Additional context
N/A
Metadata
Metadata
Assignees
Labels
api: bigqueryIssues related to the googleapis/java-bigquery API.Issues related to the googleapis/java-bigquery API.priority: p3Desirable enhancement or fix. May not be included in next release.Desirable enhancement or fix. May not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.