<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: select count query taking more time in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/select-count-query-taking-more-time/m-p/225399#M187260</link>
    <description>&lt;P&gt;Hi &lt;A rel="user" href="https://community.cloudera.com/users/1897/ashneesharma88.html" nodeid="1897"&gt;@Ashnee Sharma&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Based on the logs I could see that when you run a count query it triggers a mapreduce job and it takes time. Could you check running this command (set hive.stats.fetch.column.stats) and verify that it status is true?&lt;/P&gt;&lt;P&gt;Because when this property is enable then stats should be fetched based on stats information available in the metastore which will not trigger any jobs when you run a count query. It should work regardless whether you are using mr/tez as your execution engine. &lt;/P&gt;&lt;P&gt;Hope it helps!!&lt;/P&gt;</description>
    <pubDate>Wed, 20 Dec 2017 16:46:41 GMT</pubDate>
    <dc:creator>balavignesh_nag</dc:creator>
    <dc:date>2017-12-20T16:46:41Z</dc:date>
  </channel>
</rss>

