Issue with Databricks File Arrival Trigger – Missing File Name Information
The File Arrival Trigger in Databricks is practically useless if it does not provide the file name and path of the triggering file. In Azure Blob Storage triggers (Function Apps, ADF, Event Grid, etc.), we receive the exact file path, allowing efficient processing of only the new file.

However, in Databricks, if we have to list all files in the storage account on every run just to determine which one is new, this defeats the purpose of the trigger. This needs to be patched, or the feature adds unnecessary overhead to workflows. Please address this issue so that Databricks can be used effectively for event-driven file processing.