2013-06-28 33 views
0

在此處使用代碼http://fusion-tables-api-samples.googlecode.com/svn/trunk/ftapi/ [1]我可以通過運行[2]​​來產生成功響應。但是,我看到MYTABLEID通過CURL導入行,成功響應但在Fusion表中無變化表

指定的融合表沒有改變有些事情我已經試過:不正確的數 -upload到新的空白表正確的列數...相同的結果 -upload到其他表列...收到有關列的錯誤 - 對ftupload.sh中curl命令的各種修改[3] --remove -s -S(因此可以獲得完整的輸出)...相同的結果 - 將文件提供爲參數而不是流標準輸入[4] ...相同的結果 - 發送沒有--data-binary標誌..產生HTTP/1.1 405方法不允許
- 發送與-v標誌,產生以下日誌HTTP請求的[5]

[1],這是功能上等同於http://fusion-tables-api-samples.googlecode.com/svn/trunk/ftapi,由於該代碼不從rev56改變rev57

[2]在慶典/ Ubuntu的

[3]最初:

curl -s -S --data-binary @- -H "Authorization: Bearer $access_token" \ 
    -H "Content-Type: application/octet-stream" \ 
    "https://www.googleapis.com/upload/fusiontables/v1/tables/$1/import" 

[4]

curl -s -S --data-binary @PATHTOMYDATA.csv -H "Authorization: Bearer $access_token" \ 
    -H "Content-Type: application/octet-stream" \ 
    "https://www.googleapis.com/upload/fusiontables/v1/tables/$1/import" 

[5]

* About to connect() to www.googleapis.com port 443 (#0) 
* Trying 74.125.29.95... connected 
* successfully set certificate verify locations: 
* CAfile: none 
    CApath: /etc/ssl/certs 
* SSLv3, TLS handshake, Client hello (1): 
* SSLv3, TLS handshake, Server hello (2): 
* SSLv3, TLS handshake, CERT (11): 
* SSLv3, TLS handshake, Server key exchange (12): 
* SSLv3, TLS handshake, Server finished (14): 
* SSLv3, TLS handshake, Client key exchange (16): 
* SSLv3, TLS change cipher, Client hello (1): 
* SSLv3, TLS handshake, Finished (20): 
* SSLv3, TLS change cipher, Client hello (1): 
* SSLv3, TLS handshake, Finished (20): 
* SSL connection using ECDHE-RSA-RC4-SHA 
* Server certificate: 
*  subject: C=US; ST=California; L=Mountain View; O=Google Inc; CN=*.googl       eapis.com 
*  start date: 2013-06-19 12:43:04 GMT 
*  expire date: 2013-10-31 23:59:59 GMT 
*  subjectAltName: www.googleapis.com matched 
*  issuer: C=US; O=Google Inc; CN=Google Internet Authority 
*  SSL certificate verify ok. 
> POST /upload/fusiontables/v1/tables/MYTABLEID/import HTTP/1.1 
> User-Agent: curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0 OpenSSL/1.0.1 zli       b/1.2.3.4 libidn/1.23 librtmp/2.3 
> Host: www.googleapis.com 
> Accept: */* 
> Authorization: Bearer ya29.AHES6ZTZG_aqdYJYg-JgeAMOHOQIJOYFWAaGzzDWDlP2OKzpof8       MIkuPUA 
> Content-Type: application/octet-stream 
> Content-Length: 50 
> 
* upload completely sent off: 50out of 50 bytes 
< HTTP/1.1 200 OK 
< ETag: "TMh8SguO4XpkjXICbs8TpuVjR5I/BKKfZXT4y10ldV7sI6nrMgeYYNw" 
< Content-Type: application/json 
< Content-Length: 60 
< Date: Fri, 28 Jun 2013 15:09:00 GMT 
< Server: HTTP Upload Server Built on Jun 25 2013 11:32:14 (1372185134) 
< 
{ 
"kind": "fusiontables#import", 
"numRowsReceived": "1" 
} 
* Connection #0 to host www.googleapis.com left intact 
* Closing connection #0 
* SSLv3, TLS alert, Client hello (1): 

回答

0

有一個錯誤,吞噬了API上傳的第一行。它於2013年4月左右推出,截至2013年8月1日。

相關問題