title: Prevent AWS glue crawler to create multiple tables
body: <p>I created a glue crawler which crawls the data and creates the table in the glue data catalog. Suppose I have a CSV file (<code>file1.csv</code>) which has a schema like (<code>id</code>,<code>name</code>) and once the crawler job execution is completed it creates the Athena table (<code>crawler_file</code>) with 2 columns (<code>id</code>,<code>name</code>). Now there is a new file (<code>file2.csv</code>) which has a schema like (<code>id</code>,<code>name</code>,<code>roll_no</code>). Currently when the glue crawler is executing it is creating a new Athena table (<code>crawler_file_111</code>) with schema (<code>id</code>,<code>name</code>,<code>roll_no</code>). Can I configure the crawler in such a way that the crawler instead of creating the new table updates the existing schema of the table? In this scenario instead of creating a new Athena table (<code>crawler_file_111</code>) it should update the existing Athena table (<code>crawler_file</code>). Can I somehow achieve this scenario?</p>