You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@iotdb.apache.org by "changxue (Jira)" <ji...@apache.org> on 2022/11/11 07:58:00 UTC

[jira] [Created] (IOTDB-4915) [trigger]must have a way to drop bad trigger

changxue created IOTDB-4915:
-------------------------------

             Summary: [trigger]must have a way to drop bad trigger
                 Key: IOTDB-4915
                 URL: https://issues.apache.org/jira/browse/IOTDB-4915
             Project: Apache IoTDB
          Issue Type: Improvement
            Reporter: changxue
            Assignee: Yuan Tian


[trigger]trigger could not drop if onDrop throws exception

 

environment:

3C3D cluster

 

consider this 2 scenarios below:

1. If I develop a trigger class and I make some mistakes in onDrop method,  I'd like to drop it and update it, but I could not.

2. If I send message in onDrop and it couldn't connect now, the trigger would be updated or dropped, but I could not.

 

So, it must be a way to drop useless or bad trigger.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)