我有这个调用，它会返回成功，但不会反映所需的更改在架构上。 tracking_prod_type 是一个新字段，它不会添加到模式中。我们尝试了 Patch 和 Update 的方式，我们无法添加额外的列。更新返回：提供的架构不匹配。补丁返回有效。
I had this call, it returns successful but the required changes are not reflected on the schema. tracking_prod_type is a new field, and it's not added to the schema. We tried Patch and the Update way, and we can't add the additional columns. The update returns: Provided Schema does not match. Patch returns valid.
在postBody上，我们尝试了不同的语法，并且它们都不起作用。 [etag] => （字符串）wRHWmN_1J7FEq2j8vIkltiyoyRw / GVGxfUY15UK1iZLhzZzfWOf-1Ow
On the postBody, we tried different syntax's and none of them works. [etag] => (string) "wRHWmN_1J7FEq2j8vIkltiyoyRw/GVGxfUY15UK1iZLhzZzfWOf-1Ow"
我们尝试了以下Q& A Bigquery为表格模式添加列
We tried following this Q&A Bigquery add columns to table schema
我们看到Last Modified字段在我们发出调用时，在表模式上进行修改，但结构中没有新列。
We see the Last Modified field get modified on the table schema, when we issue the call, but the structure doesn't have the new columns.
已更新
Google_Http_Request object { batchHeaders => array(3) ( [Content-Type] => (string) application/http [Content-Transfer-Encoding] => (string) binary [MIME-Version] => (string) 1.0 ) queryParams => array(0) requestMethod => (string) PATCH requestHeaders => array(2) ( [content-type] => (string) application/json; charset=UTF-8 [authorization] => (string) edited ) baseComponent => (string) www.googleapis path => (string) /bigquery/v2/projects/aerobic-forge-504/datasets/wr_dev/tables/user_profile postBody => (string) {"fields":[{"name":"user_id","type":"integer","mode":"nullable"},{"name":"is_complete","type":"integer","mode":"nullable"},{"name":"country_id","type":"integer","mode":"nullable"},{"name":"state","type":"string","mode":"nullable"},{"name":"city","type":"string","mode":"nullable"},{"name":"zip","type":"string","mode":"nullable"},{"name":"language","type":"string","mode":"nullable"},{"name":"industry_id","type":"integer","mode":"nullable"},{"name":"subscribed_status","type":"integer","mode":"nullable"},{"name":"timestamp","type":"timestamp","mode":"required"},{"name":"tags","type":"string","mode":"repeated"},{"name":"utm","type":"record","mode":"nullable","fields":[{"name":"source","type":"string","mode":"nullable"},{"name":"medium","type":"string","mode":"nullable"},{"name":"campaign","type":"string","mode":"nullable"},{"name":"content","type":"string","mode":"nullable"},{"name":"term","type":"string","mode":"nullable"}]},{"name":"meta","type":"string","mode":"nullable"},{"name":"tracking_prod_type","type":"string","mode":"nullable"},{"name":"tracking_prod_id","type":"integer","mode":"nullable"}]} userAgent => null canGzip => null responseHttpCode => nu...使用PATCH的update2
这是当我有tableResource和架构，并使用PATCH。架构中列出了两个额外的列。我有：提供的模式不匹配表有氧锻造504：wr_dev.user_profile
This is when I have tableResource and schema, and using PATCH. Two additional columns listed in the schema. And I've got: Provided Schema does not match Table aerobic-forge-504:wr_dev.user_profile
Google_Http_Request object { batchHeaders => array(3) ( [Content-Type] => (string) application/http [Content-Transfer-Encoding] => (string) binary [MIME-Version] => (string) 1.0 ) queryParams => array(0) requestMethod => (string) PATCH requestHeaders => array(3) ( [content-type] => (string) application/json; charset=UTF-8 [authorization] => (string) edited [accept-encoding] => (string) gzip ) baseComponent => (string) www.googleapis path => (string) /bigquery/v2/projects/aerobic-forge-504/datasets/wr_dev/tables/user_profile postBody => (string) {"tableReference":{"datasetId":"wr_dev","projectId":"aerobic-forge-504","tableId":"user_profile"},"schema":{"fields":[{"name":"user_id","type":"integer","mode":"nullable"},{"name":"is_complete","type":"integer","mode":"nullable"},{"name":"country_id","type":"integer","mode":"nullable"},{"...update3 using PUT
使用更新节点时，我仍然得到模式不匹配表有氧锻造504：wr_dev.user_profile
When using the update node I still get Provided Schema does not match Table aerobic-forge-504:wr_dev.user_profile
Google_Http_Request object { batchHeaders => array(3) ( [Content-Type] => (string) application/http [Content-Transfer-Encoding] => (string) binary [MIME-Version] => (string) 1.0 ) queryParams => array(0) requestMethod => (string) PUT requestHeaders => array(4) ( [content-type] => (string) application/json; charset=UTF-8 [authorization] => (string) edited [accept-encoding] => (string) gzip [content-length] => (int) 1221 ) baseComponent => (string) www.googleapis path => (string) /bigquery/v2/projects/aerobic-forge-504/datasets/wr_dev/tables/user_profile postBody => (string) {"tableReference":{"datasetId":"wr_dev","projectId":"aerobic-forge-504","tableId":"user_profile"},"schema":{"fields":[{"name":"user_id","type":"integer","mode":"nullable"},{"name":"is_complete","type":"integer","mode":"nullable"},{"name":"country_id","type":"integer","mode":"nullable"},{"...推荐答案
在调用补丁或更新时，您需要提供类似于表格的东西。在上例中，看起来您没有传递一个表格资源，只是表格资源中的字段，你可能需要用 {schema：{fields：postBody}}
When calling patch or update, you need to provide something that looks like a table. In your example above, it looks like you're not passing a table resource, just the fields inside the table resource. You may need to wrap your postBody in something like {"schema": {"fields": postBody } }
这个问题有点令人困惑，因为bq update会为你打包。
This is a little bit confusing from the other question, because bq update does this wrapping for you.
你看到更新失败是因为bigquery服务器根本没有看到任何模式，所以它认为你正试图删除模式。并且修补程序成功但没有ng，因为它根本没有看到任何有效的字段，所以它只是做一个空补丁操作。
The reason you're seeing update fail is because the bigquery server doesn't see any schema at all, so it thinks you're trying to delete the schema. And patch succeeds but does nothing, because it doesn't see any valid fields at all, so it just does a null patch operation.
下面是一个curl会话的例子，它将字段添加到一个模式。适应php应该相对容易。它使用来自此处的auth.py
Here is an example of a curl session that adds fields to a schema. It should be relatively easy to adapt to php. It uses auth.py from here
PROJECT_ID=<your_project_here> DATASET_ID=scratch BASE_URL=www.googleapis/bigquery/v2/projects TABLES_URL=${BASE_URL}/${PROJECT_ID}/datasets/${DATASET_ID}/tables ### Make a scratch dataset. bq --project_id=${PROJECT_ID} mk –d ${DATASET_ID} SCHEMA="{'fields': [{'name':'foo', 'type': 'STRING'}]}" TABLE_REF="{'tableId': 'table1', \ 'datasetId': 'scratch', \ 'projectId': '${PROJECT_ID}'}" ### Make a temporary table with a schema. curl -H "$(python auth.py)" \ -H "Content-Type: application/json" \ -X POST \ -d "{'tableReference': ${TABLE_REF}, \ 'schema': ${SCHEMA}}" \ "${TABLES_URL}" ### Tables.update() SCHEMA2="{'fields': [ \ {'name':'foo', 'type': 'STRING'}, \ {'name': 'bar', 'type': 'FLOAT'}]}" TABLE_JSON="{'tableReference': ${TABLE_REF}, 'schema': ${SCHEMA2}}" curl -H "$(python auth.py)" \ -H "Content-Type: application/json" \ -X PUT \ -d "${TABLE_JSON}" \ "${TABLES_URL}/table1" ### Tables.patch() EXPIRATION_TIME=$(($(date +"%s")+24*60*60))000 curl -H "$(python auth.py)" \ -H "Content-Type: application/json" \ -X PATCH \ --data-binary "{'expirationTime': '${EXPIRATION_TIME}'}" \ "${TABLES_URL}/table1"更多推荐
Google BigQuery表补丁/更新不起作用
发布评论