Note for auto_create_table#8891
Conversation
AUTO_CREATE_TABLE implies that it should only be used if the target table does not exist; however, this is not true. This can be enabled which make use of more optimized code paths for parquet which can also impact data type mapping. See IcM 379492745.
|
@scott-epperly : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit d5f1cc1: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Can you review the proposed changes? When the changes are ready for publication, add a #label:"aq-pr-triaged" |
|
Learn Build status updates of commit 24cd231: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
#sign-off |
|
PR 8891 has been merged from scott-epperly:patch-5 to MicrosoftDocs:live by Jak-MS. |
|
Learn Build status updates of commit efefd5e: ❌ Validation status: errorsPlease follow instructions here which may help to resolve issue.
For more details, please refer to the build report. Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them. For any questions, please:
|
AUTO_CREATE_TABLE implies that it should only be used if the target table does not exist; however, this is not true. This can be enabled which make use of more optimized code paths for parquet which can also impact data type mapping. See IcM 379492745.