title: Glue crawler created multiple tables from a partitioned S3 bucket
body: <p>I have an S3 bucket that is structured like this:</p>
  
  <pre><code>root/
  ├── year=2020/
  │   └── month=01
  │       ├── day=01 
  |       |     ├──  file1.log
  |       |     ├──  ...
  |       |     └──  file8.log
  │       ├── day=...
  │       └── day=31 
  |             ├──  file1.log
  |             ├──  ...
  |             └──  file8.log
  └── year=2019/
          ├── ...
  </code></pre>
  
  <p>Each day would have 8 files with identical names across the days ─ there would be a <code>file1.log</code> in every 'day' folders. I crawled this bucket using a custom classifier. </p>
  
  <p><strong>Expected behavior</strong>: Glue will create one single table with year, month, and day as partition fields, and several other fields that I described in my custom classifier. I then can use the table in my Job scripts.</p>
  
  <p><strong>Actual behavior</strong>: </p>
  
  <p>1) Glue created one table that fulfilled my expectations. However, when I tried to access it in Job scripts, the table was devoid of columns.</p>
  
  <p>2) Glue created one table for every 'day' partitions, and 8 tables for every <code>file&lt;number&gt;.log</code> files </p>
  
  <p>I have tried excluding <code>**_SUCCESS</code> and <code>**crc</code> like people suggested on this other question: <a href="https://stackoverflow.com/questions/48373084/aws-glue-crawler-adding-tables-for-every-partition">AWS Glue Crawler adding tables for every partition?</a> However, it doesn't seem to work. I have also checked the 'Create a single schema for each S3 path' option in the crawler's setting. It still doesn't work.</p>
  
  <p>What am I missing?</p>