Client meta file fields garbled

[aaronmbr]

Original issue 58 created by aaronmbr on 2011-09-15T20:03:21.000Z:

The problem was noticed by Tiziana Refice at Google when summarizing the distinct values for client_os field and the client_browser fields. The values she found don't make sense, looking like maybe the client code responsible for parsing them out of the user agent string has a bug.

The tables below, from her findings, including the distinct values for the respective fields and the count of each from the data collected August 2011.

Values for the client_os field:

| Linux | 176 | | net | 6915 | | d | 4 | | et | 124 | | tbusiness.net | 2 | | k | 10 | | iamedia.cz--kontakty.viamedia.info | 16 | | liant.net | 2 | | ddr.arpa | 2 | | t.net | 10 | | SunOS | 2 | | 9.in-addr.arpa | 2 | | a | 4 | | t | 2 | | pa | 2 | +------------------------------------+----------------------------------+

Values for the client_browser field:

| fo | 16 |

[aaronmbr]

Comment #1 originally posted by aaronmbr on 2014-04-15T07:23:51.000Z:

Tiziana, is this ticket still valid?

[aaronmbr]

Comment #2 originally posted by aaronmbr on 2014-04-15T08:03:53.000Z:

The results for the first quarter of 2014 are Row connection_spec_client_os count
1 Windows 29552877040
2 24081657251
3 Linux 66508123
4 qnx 40946
5 9.in-addr.arpa 3947

FYI: The BigQuery query run to get the results above is

SELECT connection_spec.client_os, count(*) as count FROM m_lab.2014_01,m_lab.2014_02,m_lab.2014_03 GROUP BY connection_spec.client_os;

[aaronmbr]

Comment #3 originally posted by aaronmbr on 2014-06-25T08:18:57.000Z:

<empty>