Closed GoogleCodeExporter closed 9 years ago
Thank you for the bug report! We're looking into to it and will update the bug
once we have a fix or more information.
Original comment by roselan...@google.com
on 20 Aug 2014 at 4:09
Same here! This is a blocker, expecially when using automated dashboard tools
like BIME or Tableau
Original comment by lorenzo....@noovle.it
on 12 Nov 2014 at 1:59
Any news about this? I created a view with a timestamp field from a query with
a GROUP BY and BigQuery still creates the additional _usec field.
Thanks!
Original comment by l.oluy...@gmail.com
on 12 Jan 2015 at 4:22
Any Update on this? We are facing the same problem and it is a show stopper for
us. We expose the tables thru apis and apis gets the schema of the views,
tables from metadata then construct the query...
Original comment by bnemu...@zulily.com
on 10 Feb 2015 at 11:04
Apparently they have noticed this behavior and they are working on it. But I
saw some workarounds on StackOverflow.
Original comment by luxia...@gmail.com
on 16 Mar 2015 at 10:41
Same here, big issue in tableau on BQ !
Any link to the workarounds ?
Original comment by mathysfr...@gmail.com
on 27 May 2015 at 10:45
Original comment by mos...@google.com
on 1 Jun 2015 at 6:43
I'd really like to have some workaround too.
Original comment by anto...@iceberg-marketplace.com
on 11 Jun 2015 at 4:34
This problem should be fully fixed now.
Original comment by mos...@google.com
on 11 Jun 2015 at 8:58
It's not fixed for me:
Waiting on bqjob_r6e2f2c7fcc12302e_0000014de7a5a588_1 ... (0s) Current status:
DONE
Error in query string: Error processing job
'iceberg-marketplace:bqjob_r6e2f2c7fcc12302e_0000014de7a5a588_1': Schema
changed for Timestamp field
order_created_on
And now I can't even access the web interface.
Original comment by anto...@iceberg-marketplace.com
on 12 Jun 2015 at 12:11
The web interface is back
Original comment by anto...@iceberg-marketplace.com
on 12 Jun 2015 at 1:49
Thanks - the "Wrong schema for Views with TIMESTAMP" is different issue, and we
are taking care of it right now.
Original comment by mos...@google.com
on 12 Jun 2015 at 1:54
The timestamp error in #10 should be fixed. Please let us know if you see any
more issues.
Original comment by jcon...@google.com
on 12 Jun 2015 at 2:52
Its fixed. Thanks
Original comment by anto...@iceberg-marketplace.com
on 12 Jun 2015 at 3:37
Well its not fixed everywhere. Is this has to be solved table by table ? Some
job ids:
Error: Schema changed for Timestamp field created_on
Job ID: iceberg-marketplace:job_5b-cJ8AAPxu4WBtx2DJoAQEd0lo
Error: Schema changed for Timestamp field created_on
Job ID: iceberg-marketplace:job_x6Di5O0XnVsVcYuHY7L0k906ADo
Error: Schema changed for Timestamp field timestamp
Job ID: iceberg-marketplace:job_SCxOuoZFS5xoNG5CUd0e4dmuYx0
Error: Schema changed for Timestamp field created_on
Job ID: iceberg-marketplace:job_LnHYey3w_tt4Nuq2jqUZzubDri0
Original comment by anto...@iceberg-marketplace.com
on 12 Jun 2015 at 4:19
I've fixed up all tables in that dataset. How does it look now?
Original comment by jcon...@google.com
on 12 Jun 2015 at 6:08
Tested and approved. Thanks
Original comment by anto...@iceberg-marketplace.com
on 13 Jun 2015 at 9:11
Hello, It's me again.
Some tables in the iceberg_sandbox dataset from the iceberg-marketplace project
are facing the same problems.
Original comment by anto...@iceberg-marketplace.com
on 15 Jun 2015 at 3:41
Fixed! Let me know if anything else is amiss.
Original comment by jcon...@google.com
on 15 Jun 2015 at 9:07
Works like a charm. Thanks
Original comment by anto...@iceberg-marketplace.com
on 15 Jun 2015 at 10:33
Original issue reported on code.google.com by
ale...@freshplanet.com
on 20 Aug 2014 at 3:33