In order to get shell access to the Analytics Cluster through Hive you need to be added to either the
analytics-privatedata-users or the
analytics-users shell user group. Per Requesting shell access, create a Phabricator ticket for such request. Some analytics team generated data (like the webrequest logs) are considered private data, and only
analytics-privatedata-users can access it. If you are getting access to Hive, you will probably want to be in this group.
For how to access the servers (once you have the credentials), see: Analytics/Cluster/Access
- Analytics/Cluster/Hive/Queries (includes a FAQ about common tasks and problems)
While hive supports SQL, there are some differences: see the Hive Language Manual for more info.
(see also Analytics/Data)
- Webrequest (raw and refined)
- EventLogging data, in the
- The wmf_raw and wmf databases contain Hive tables maintained by Ops. You can create your own tables in Hive, but please be sure to create them in a different database, preferably one named after your shell username.
- Hive has the ability to map tables on top of almost any data structure. Since webrequest logs are JSON, the Hive tables must be told to use a JSON SerDe to be able to serialize/deserialize to/from JSON. We use the JsonSerDe included with Hive-HCatalog.
- The HCatalog .jar will be automatically added to a Hive client's auxpath. You shouldn't need to think about it.
See the FAQ
Subpages of Analytics/Systems/Cluster/Hive
- Analytics/Cluster/Access - on how to access Hive and Hue (Hadoop User Experience, a GUI for Hive)