<pstyle="padding:5px 0px;margin-bottom:0px;width:800px">This table keeps several important hive-specific pipeline-wide key-value pairs such as hive_sql_schema_version, hive_use_triggers and hive_pipeline_name.</p>
<pstyle="padding:5px 0px;margin-bottom:0px;width:800px">This table contains a simple hash between pipeline_wide_parameter names and their values. The same data used to live in 'meta' table until both the schema and the API were finally separated from Ensembl Core.</p>
<pstyle="padding:5px 0px;margin-bottom:0px;width:800px">This table keeps several important hive-specific pipeline-wide key-value pairs such as hive_sql_schema_version, hive_use_triggers and hive_pipeline_name.</p>
<pstyle="padding:5px 0px;margin-bottom:0px;width:800px">This table comes from the Ensembl core schema. It is created here with the 'IF NOT EXISTS' option to avoid a potential clash if we are dealing with core-hive hybrid that is created in the wrong order. At the moment meta table is used (1) for compatibility with the Core API ('schema_version'), (2) to keep pipeline-wide parameters.</p>
<trclass="bg1"><td><b>meta_id</b></td><td>INTEGER</td><td></td><td>auto-incrementing primary key, not really used per se</td><td></td></tr>
<trclass="bg2"><td><b>species_id</b></td><td>INTEGER</td><td>1</td><td>always 1, kept for compatibility with the Core API</td><td>unique key: species_key_value_idx<br/>key: species_value_idx</td></tr>
<trclass="bg1"><td><b>meta_key</b></td><td>VARCHAR(255)</td><td></td><td>the KEY of KEY-VALUE pairs</td><td>unique key: species_key_value_idx</td></tr>
<trclass="bg2"><td><b>meta_value</b></td><td>TEXT</td><td></td><td>the VALUE of KEY-VALUE pairs</td><td>unique key: species_key_value_idx<br/>key: species_value_idx</td></tr>
<trclass="bg1"><td><b>time</b></td><td>TIMESTAMP</td><td>CURRENT_TIMESTAMP</td><td>when this snapshot was taken</td><td></td></tr>
<trclass="bg2"><td><b>workers</b></td><td>INTEGER</td><td>0</td><td>number of running workers</td><td></td></tr>
<trclass="bg1"><td><b>throughput</b></td><td>FLOAT</td><td>NULL</td><td>average numb of completed Jobs per sec. of the hive (this number is calculated using running workers only)</td><td></td></tr>
<trclass="bg2"><td><b>per_worker</b></td><td>FLOAT</td><td>NULL</td><td>average numb of completed Jobs per sec. per Worker (this number is calculated using running workers only)</td><td></td></tr>
<trclass="bg1"><td><b>analysis</b></td><td>TEXT</td><td>NULL</td><td>a comma-separated list of analyses running at the time of snapshot</td><td></td></tr>