ADF Event trigger issue
Hello Team, I have created an storage EVENT trigger in ADF and it is based on the Blob creation under one of the folders in the container (storage explorer). Here is my issue If
- I manually drop a BLOB under a folder in container, Event trigger triggers as expecteD. This works great.
- I write a BLOB from an external software agent(in my In-premise server) into the container(in the same folder when manually creation of BLOB trigger the event trigger), my event trigger doesn't trigger at all. please advise what I could be missing. I have verified all the required privileges and very surprisingly it works when I create the same file in the same folder under container but manually.
Azure Blob Storage
Azure Data Factory
-
Piyush Tiwari 5 Reputation points
2023-04-24T04:48:40.1+00:00 Anybody at MS to support?
-
Nandan Hegde 31,511 Reputation points • MVP
2023-04-24T05:50:12.2533333+00:00 Hey, Can you please check what is the content-type of your file in both scenarios?
-
Piyush Tiwari 5 Reputation points
2023-04-24T14:55:16.5833333+00:00 Hi Nandan, It's same file type for both scenarios. Please see the screenshot as below. It's same for both.
Regards, PK
-
Nandan Hegde 31,511 Reputation points • MVP
2023-04-24T15:04:37.84+00:00 Hey, In the screenshot I am not seeing Content-type property. Click on the file and overview and check the property (for both scenarios)
-
Piyush Tiwari 5 Reputation points
2023-04-24T15:13:47.42+00:00 I am so sorry. I took the wrong screenshot. Here it is :
-
RevelinoB 2,780 Reputation points
2023-04-24T15:53:11.1533333+00:00 Hi Piyush, There could be several reasons why your event trigger is not working when a blob is written from your Hadoop agent. Here are a few things to check:
- Check that the Hadoop agent is writing the blob to the correct folder in the container. Make sure that the path and name of the blob match the criteria specified in the trigger.
- Verify that the Hadoop agent has the necessary permissions to write to the container. You may need to check the access policies for the container to ensure that the agent has the appropriate level of access.
- Ensure that the Hadoop agent is using the correct connection string to write to the container. Check that the connection string is correct and that it includes the storage account name, container name, and access key.
- Check the status of the trigger. You may need to monitor the trigger's execution history to see if it is failing or encountering errors.
- Consider enabling diagnostic logging for the trigger. This can help you identify any issues that may be occurring during the execution of the trigger.
-
Piyush Tiwari 5 Reputation points
2023-04-24T16:03:16.9233333+00:00 With a discussion here, I was expecting much better support than scripted answer from ChatGPT. Please don't do that. Thanks in advance. When I say, Hadoop is already writing a file to my container, IT IS! I do NOT need to check if Hadoop had rights to write the file in my container. please dont copy paste.
-
Piyush Tiwari 5 Reputation points
2023-04-24T16:05:18.0333333+00:00 @Nandan Hegde Any thoughts for me?
-
PRADEEPCHEEKATLA-MSFT 85,746 Reputation points • Microsoft Employee
2023-04-25T04:16:57.61+00:00
Piyush Tiwari - You may checkout MS Q&A thread which addressing similar issue.Hope this helps. Do let us know if you any further queries.
-
PRADEEPCHEEKATLA-MSFT 85,746 Reputation points • Microsoft Employee
2023-04-27T09:18:06.65+00:00 Piyush Tiwari - We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
-
Piyush Tiwari 5 Reputation points
2023-04-30T19:57:16.56+00:00 @PRADEEPCHEEKATLA-MSFT Thaks for trying to be a help. Unfortunately, the issue is not fixed. Also, I created a Microsoft ticket (TrackingID#2304240040007587) and very expectedly Microsoft expert gave million dollar excuse of Product limitation. This is so unfortunate that Microsoft doesn't know it's own product and have absolutely no clue what is what. This is not a feedback for you Pradeep. It's a feedback for MS. We are still stuck with our issue and as always MS has no clue how to fix it. If you can only help me, please escalate this to someone who understand MS product well and more importantly, MS customers.
regards,
piyush
-
PRADEEPCHEEKATLA-MSFT 85,746 Reputation points • Microsoft Employee
2023-05-01T04:13:51.7333333+00:00 Piyush Tiwari - We are reaching out to the internal team to get more information related to your query and will get back to you as soon as we have an update.
-
Piyush Tiwari 5 Reputation points
2023-05-02T12:40:28.28+00:00 Any luck?
-
PRADEEPCHEEKATLA-MSFT 85,746 Reputation points • Microsoft Employee
2023-05-04T05:33:19.7033333+00:00 Piyush Tiwari - We are still awaiting for internal team response and will get back to you as soon as we have an update.
-
Piyush Tiwari 5 Reputation points
2023-05-08T05:44:46.2566667+00:00 Any update?
Sign in to comment