-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New-AzDataLakeGen2Item created files do not trigger ADF event #14745
Comments
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @sumantmehtams. Issue DetailsDescriptionWhen a file is uploaded to our azure data lake via New-AzDataLakeGen2Item the configured event trigger does not fire in ADF. Downloading and then reuploading via Azure Storage Explorer does cause the trigger to fire. Steps to reproduceConfigure an ADF trigger against data lake gen2 and then upload a triggering file via the New-AzDataLakeGen2Item command. Environment data
Module versions
|
What's the detail ADF trigger you have set? For upload file with |
It's data.api string is in CopyBlob PutBlob PutBlockList FlushWithClose DeleteBlob CreateFile DeleteFile thanks, |
In most cases, New-AzDataLakeGen2Item will use PutBlob or PutBlockList to upload File (use which request depends on file size). To get the details, would you please share
|
1. The file is 2.3kb in size
2.
```
$destPath = $dirname + (Get-Item $local_src_file).Name
New-AzDataLakeGen2Item -Context $ctx -FileSystem $filesystemName -Path $destPath -Source $local_src_file
```
3. I don’t understand this – I’m creating the file with the New-AzDataLakeGen2Item cmdlet.
4. Happy to capture this if you can point me to an online guide on how to capture the traffic?
Thanks,
|
From #1, #2, the PutBlob request should be used. |
Ah okay, I'm literally clicking the upload button in Azure Storage Explorer, the underlying command it's running is
Azure Storage Explorer v1.19.0 I'll look into wireshark and fiddler ASAP. |
I also use Azure Storage Explorer v1.19.0. |
Strange. It's 100% reproducible that it works through Storage Explorer and not through the cmdlet. What cmdlet version are you using? |
Good news I've figured it out with fiddler. The powershell script was uploading the file with a path that had a duplicate directory separator. This path was normalised by the storage service so /raw//my_upload -> /raw/my_upload. But the event hub was seeing the original path. As it's matching on the pathname the event was never thrown. Many thanks for your help! |
Description
When a file is uploaded to our azure data lake via New-AzDataLakeGen2Item the configured event trigger does not fire in ADF. Downloading and then reuploading via Azure Storage Explorer does cause the trigger to fire.
Steps to reproduce
Configure an ADF trigger against data lake gen2 and then upload a triggering file via the New-AzDataLakeGen2Item command.
Environment data
Module versions
The text was updated successfully, but these errors were encountered: