Hmm, I have heard this feedback before. Perhaps a more low-key approach would be either a static timer that checked or a timer bolt that sent a periodic timer and the parser bolt reconfigured the parser (or indeed we added a Reloadable interface with a 'reload' method). We could be smart also and only set up the topology with the timer bolt if the parser actually implemented the Reloadable interface. Just some thoughts that might be easy and avoid instability.
On Tue, Jan 30, 2018 at 3:42 PM, Otto Fowler <ottobackwa...@gmail.com> wrote: > It is still @unstable, but the jiras : > https://issues.apache.org/jira/browse/HDFS-8940?jql= > project%20%3D%20HDFS%20AND%20status%20in%20(Open%2C%20% > 22In%20Progress%22)%20AND%20text%20~%20%22INotify%22 > that I see are stall from over the summer. > > They also seem geared to scale or changing the filter object not the api. > > > > On January 30, 2018 at 14:19:56, JJ Meyer (jjmey...@gmail.com) wrote: > > Hello all, > > I had created a NiFi processor a long time back that used the inotify API. > One thing I noticed while working with it is that it is marked with the > `Unstable` annotation. It may be worth checking if anymore work is going on > with it and if it will impact this (if it hasn't already been looked into). > > Thanks, > JJ > > On Mon, Jan 29, 2018 at 7:27 AM, Otto Fowler <ottobackwa...@gmail.com> > wrote: > > > I have updated the jira as well > > > > > > On January 29, 2018 at 08:22:34, Otto Fowler (ottobackwa...@gmail.com) > > wrote: > > > > https://github.com/ottobackwards/hdfs-inotify-zookeeper > > >
