Assigned
Status Update
Comments
ch...@google.com <ch...@google.com> #2
Changing this to a feature request. It's a known issue that some size related fields are missing for BigQuery table. This is because those fields are changing too frequently (all the time for streaming). We are working with BigQuery team to find a best way to address it.
ch...@google.com <ch...@google.com>
sa...@google.com <sa...@google.com> #3
The Cloud asset inventory result is also missing fields bigquery field such as the type of table and materialized view information.
"type": "MATERIALIZED_VIEW",
"location": "US",
"materializedView": {
"query": "(
SELECT
logName,
trace
FROM
project.dataset.table
)",
de...@americanas.io <de...@americanas.io> #4
Same goes for fields storageBillingModel and maxTimeTravelHours.
yu...@google.com <yu...@google.com>
yi...@google.com <yi...@google.com> #5
CAIS is working together with BigQuery team to migrate to the new data flow that provides all fields. ETA end of 2023Q1
[Deleted User] <[Deleted User]> #6
2023Q1 has already passed. What is the status now?
o....@plarium.com <o....@plarium.com> #7
+1
[Deleted User] <[Deleted User]> #8
+1
di...@google.com <di...@google.com>
di...@google.com <di...@google.com> #9
yuchens@google.com could you look into this and see if we are unblocked by BQ (as per comment #5 )? Thanks!
yu...@google.com <yu...@google.com> #10
CAIS team is actively working on this. The current plan is to have all non-volatile fields ready to serve by early Q4'23. *non-volatile fields means fields that do not change too frequently. For example the numBytes, numRows...etc are volatile fields. storageBillingModel is not volatile.
Please let us know if there are needs for volatile fields, or the timeline doesn't work. We can try to better priotize.
Please let us know if there are needs for volatile fields, or the timeline doesn't work. We can try to better priotize.
[Deleted User] <[Deleted User]> #11
This issue affects many fields in BigQuery resources, but has not yet been documented in the supported asset types docs.
https://cloud.google.com/asset-inventory/docs/supported-asset-types
I would like to see it documented, as I often believe the schema on BigQuery in Cloud Asset Export and assume the values are filled in.
I would like to see it documented, as I often believe the schema on BigQuery in Cloud Asset Export and assume the values are filled in.
di...@google.com <di...@google.com> #12
Good point we should highlight exceptions. I will discuss this internally see how we could improve our docs. thanks
ad...@capitalone.com <ad...@capitalone.com> #13
Any update for fields like numBytes?
rp...@ford.com <rp...@ford.com> #14
Also interested to hear any updates for these null fields.
do...@google.com <do...@google.com> #15
We're working on migrating CAIS feeds to new feeds which include the missing fields, current ETA is by Q1/2024.
pa...@sabre.com <pa...@sabre.com> #16
Hi, we would like to have also violate fields like numBytes ( it can be daily snapshot)
Description
Issue summary: The customer is trying to get the billing sync table information from the resulting table of a cloud asset inventory export.
The customer is using the table id of the billing sync table on bigquery
But when the customer retrieves the information from the cloud asset export in bigquery, the query returns information related to the billing sync table, but a lot of columns returned a null value and the customer needs information about the size of the table, number of rows of the table etc.
The related attributes are null:
1.- Why that attributes are coming all as "null"?
2.- Isn't the Cloud Asset export supposed to fill those fields?.