I am Receiving the following error
invalid property 'ERROR_INTEGRATION' for 'TASK'
when adding notification integration property to TASK OBJECT in snowflake hosted on AWS.
I have defined notification integration <my_notifcation_int> successfully.
invalid property 'ERROR_INTEGRATION' for 'TASK'
The definition of task is as follows :
create task mytask
schedule = '5 MINUTE'
error_integration = <my_notification_int>
as
insert into mytable(ts) values(current_timestamp);
As per snowflake documentation, ERROR_INTEGRATION in TASK OBJECTS is supported.
Any suggestions on resolving this error?
Related
I am building a near real time service. The input is a cloud storage bucket and blob path to a photo image. This horizontally-scalable service is made up of multiple components including ML models running on k8s and Google Cloud Functions, each of which has a chance of failing for a variety of reasons. The ML models are independent and run in parallel. Each component is triggered by a PubSub push message topic unique to the component. Running the entire flow for one photo may take 15 seconds.
I want to return a meaning error message back to the service requester telling which component failed if there is a failure. Essentially, I want to report which image failed and where it failed.
What is the recommended practice for returning an error back to the requester?
There is no built in service for this. But, because you already use PubSub for asynchronous call, I propose to use it also to push back the error.
You can do this in 2 flavors
First, create a PubSub topic for the errors, let's say 'error_topic'
1. Without message customization
In the PubSub message, the requester put which it is in the attribute (let's say 'requester' attribute name)
In the consumer service, if an error occurs, return an error code (500 for example) for push subscription or a NACK in pull subscription.
Configure the PubSub subscription to manage retry and dead letter topic (the dead letter topic is 'error_topic')
Then, create one subscription per requester on the 'error_topic' (use the filter capability for this) and consume the message in the requester services
2. With message customization
In the PubSub message, the requester put which it is in the attribute (let's say 'requester' attribute name)
The consumer service that raises the error create a new message with custom information and copies the 'requester' attribute value and then puts it in attribute of the message in the 'error_topic' (let's say 'original_requester' attribute name).
Then, create one subscription per requester on the 'error_topic' (use the filter capability for this) and consume the message in the requester services
I have a data processing workflow like this. The Download task creates a session ID (GUID) and pass it to Parse task and then the Post task. If any exception occurs in these three tasks, the workflow jumps to Failed task. The Failed task would update the status of the process as failed in DynamoDB. To do that, it needs to get the session ID.
Is there any way to pass the session ID to the Failed task?
Or, if the session ID is created outside and passed in to the workflow, is it possible to share this ID to all the tasks?
Specify ResultPath property in the error catcher. By default it is $, which means that output of a failed Parallel State will be only error info. However, if you set ResultPath to, for example, $.error_info then you will preserve state and error data will be accessible under error_info property.
For more details, you may be interested in https://docs.aws.amazon.com/step-functions/latest/dg/concepts-error-handling.html (Error Handling).
I can not create spanner instance by using nodejs client library.
{ Error: Creating an instance that is in the process of getting
deleted.
at /Users/Chipintoza/GSS Projects/accounts.gss.ge/node_modules/grpc/src/node/src/client.js:442:17
code: 9, metadata: Metadata { _internal_repr: {
'google.rpc.resourceinfo-bin': [Object] } }, note: 'Exception
occurred in retry method that was not classified as transient' }
I looked at Activity and yesterday when i deleted instance it turned out that the error occurred:
Resource name projects/spanner-gss-ge/instances/business-data Error
message Deadline exceeded (HTTP 504): Deadline expired before
operation could complete.
On Console the Instance with this name is not listed.
How can i resolve this issue?
As it is not deleted am i charged on daily basis?
I have no problem with creating instance by the other name.
I have defined a new artifact type and am successfully creating new asset instances of it in the publisher - which works well. Recently I was experimenting with my own create_form.hbs under publisher/extensions/assets//themes/default/partials/ and then decided against continuing. After deleting the newly created '/themes/default/partials/create_form.hbs' I then found that when I now try to publish a new instance of the artifact I get the following error thrown:
[2016-11-11 11:17:06,833] ERROR - Failed to invoke action: Create for the asset of id: "9a3a4e55-a5a3-4c94-a2d0-152a10e4ab45".The following exception was thrown: JavaException: org.wso2.carbon.registry.core.exceptions.RegistryException: Preprequest action must be completed before Create {rxt.asset}
[2016-11-11 11:17:06,833] ERROR - org.wso2.carbon.registry.core.exceptions.RegistryException: Preprequest action must be completed before Create {asset_api_endpoints}
org.mozilla.javascript.WrappedException: Wrapped org.wso2.carbon.registry.core.exceptions.RegistryException: Preprequest action must be completed before Create (eval code#1(eval)#87) at org.mozilla.javascript.Context.throwAsScriptRuntimeEx(Context.java:1754) at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:148) at org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:22
Despite this and the fact that I get the user friendly 'Error' message in the publication page telling me the asset was unable to be created, the new instance does in fact get created (I can see it when I go the the asset list page). I can also edit with no problems.
I'm unsure whether this error is related to the create_form.hbs page I previously created (and then deleted) or whether it is just a coincidence.
Is there a caching problem going on?
Any help on what the error means and how to resolve it would be greatly appreciated.
Thanks in advance.
The defaultAction value (under meta lifecycle) in the asset file was defined as "Create" which didn't match what was in the LifeCycle config. This action must match a valid lifecycle value otherwise the publish page displays an error message despite successfully creating the new asset.
My situation:
I create via OTRS Admin Backend a custom webservice:REST
added an custom invoker on GenericInterface::Invoker::ModuleRegistration
added new invoker:REST Event-Trigger: TicketSlaveLinkAdd
configured otrs as requester HTTP::REST Host as: http://myhost.com
controller mapping: /LinkAdd/:TicketID
standard command: PATCH
My Problem:
System Log returns:
DebugLog error: Summary: HTTP::REST Error while determine Operation for request URI '/LinkAdd'. Data : No data provided.
DebugLog error: Summary: Request could not be processed Data : HTTP::REST Error while determine Operation for request URI '/LinkAdd'..
DebugLog error: Summary: Returning provider data to remote system (HTTP Code: 500) Data : HTTP::REST Error while determine Operation for request URI '/LinkAdd'..
Maybe somebody know about my problem and can help :)
The Error while determine Operation text points out that OTRS is the incoming call is not able to determine the Operation for the incoming URI; please check your data mapping.