title: Aws Glue Catalog - How not to partition table with glue catalog
body: <p>I have S3 folder structure of the following format, let's say: Abc/123/xyz.txt and Abc/456/jkl.txt etc.
  Where xyz.txt and jkl.txt have same structure.
  I am cataloguing it using AWS glue crawler where I am passing the source as: Abc/ and specifying the option of creating a single table for S3 files. What I perceive is that it will create a table with 2 partitions I.e. 123 and 456. But I want to have a single table without any partitioning and contains the data from both xyz.txt and jkl.txt when queried through Atehna. Any ideas on how this can be achieved?</p>