Last modified: 2014-04-21 18:46:41 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T62549, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 60549 - Analytics: Error when attempting COUNT and GROUP BY on webrequest_mobile
Analytics: Error when attempting COUNT and GROUP BY on webrequest_mobile
Status: RESOLVED WONTFIX
Product: Analytics
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-01-29 00:10 UTC by Oliver Keyes
Modified: 2014-04-21 18:46 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments
Error log (9.61 KB, text/plain)
2014-01-29 00:10 UTC, Oliver Keyes
Details

Description Oliver Keyes 2014-01-29 00:10:48 UTC
Created attachment 14403 [details]
Error log

Something to do with the fact that it's a JSON table? Full log attached.
Comment 1 Bingle 2014-01-29 00:20:31 UTC
Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/analytics/cards/cards/1417
Comment 2 christian 2014-01-29 10:37:41 UTC
Taking a brief look at the error log, it seems the culprit is again an
unquoted nan as value (see time_firstbyte):

  {"hostname":"cp1046.eqiad.wmnet","sequence":952664769,"dt":"2014-01-04T07:02:58","time_firstbyte":nan,[...]

which causes the root exception

  Caused by: org.codehaus.jackson.JsonParseException: Unrecognized token 'na': was expecting 'null', 'true' or 'false'

.

@ottomata: As that log line is from 2014-01-04 (which is before the
nan-fix IIRC), should we correct this data by hand, or just drop the
data up to when the fix went in.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links