title: Hive partitioning for data on s3
body: <p>Our data is stored using <code>s3://bucket/YYYY/MM/DD/HH</code>  and we are using aws firehouse to land parquet data in there locations in near real time . I can query data using AWS athena just fine however we have a hive query cluster which is giving troubles querying data when partitioning is enabled . </p>
  
  <p>This is what I  am doing : 
  <code>PARTITIONED BY ( 
    `year` string, 
    `month` string, 
    `day` string, 
    `hour` string)</code></p>
  
  <p>This doesn't seem to work when data on s3 is stored as <code>s3:bucket/YYYY/MM/DD/HH</code> </p>
  
  <p>however this does work for <code>s3:bucket/year=YYYY/month=MM/day=DD/hour=HH</code></p>
  
  <p>Given the stringent bucket paths of firehose i cannot modify  the s3 paths. So my question is what's the right partitioning scheme in hive ddl  when you don't have an explicitly defined column name on your data path like <code>year</code> = or <code>month</code>= ?</p>