Pierre,

I think this discussion brings up a valid conversation point. At some point
a PMC member needs to approve the merge request, so from a contributors
level what can we do to make that merge both easier and/or more likely to
happen. That and how the community can help filter down the ever growing
backlog of PRs.

Thanks and look forward to helping,

Phillip

On Wed, Oct 7, 2020 at 2:04 PM Pierre Villard <pierre.villard...@gmail.com>
wrote:

> Nissim,
>
> Thanks a lot for your contribution but there are 277 pull requests opened
> at this time. This is a community effort, and if you expect people to
> review your PRs, you'd have to also try reviewing PRs opened by others in
> the community. Otherwise this will need to wait for someone with some
> bandwidth to focus on this.
>
> Thanks,
> Pierre
>
> Le mer. 7 oct. 2020 à 19:59, Nissim Shiman <nshi...@yahoo.com.invalid> a
> écrit :
>
> >  Second attempt...
> >
> >
> > Hello NiFi team,
> >
> > Could someone respond to this email.
> >
> > Thanks,
> > Nissim Shiman
> >     On Monday, October 5, 2020, 11:01:57 AM EDT, Nissim Shiman
> > <nshi...@yahoo.com.invalid> wrote:
> >
> >  Hello NiFi team,
> > Could someone review the pull request for NIFI-7738 (
> > https://issues.apache.org/jira/browse/NIFI-7738), that was put in 5 days
> > ago?
> > (Provenance Search Events - add feature to allow inverse query)
> >
> > One case this will come in handy is if a particular flowfile has an issue
> > and goes in circles through processors and ends up emitting a lot of
> > provenance making it hard to follow other flowfiles.
> >
> > This feature will allow users to query for all provenance except for the
> > uuid of the problematic flowfile.
> >
> >
> >
> > This can also be used for any indexed field or attribute as well.
> > This has been compiled and tested on java 8 and java11 for all 4
> > provenance repository implementations  for both indexed fields and
> indexed
> > attributes
> > The only "real" code changes were made to LuceneUtil.java (to handle
> > WriteAhead, EncryptedWriteAhead and Persistent Provenance Repostories)
> and
> > VolatileProvenanceRepository.java
> > The rest are just involved in propagating the ability to query the "NOT"
> > option for a given user entered provenance search value from the gui to
> the
> > backend query.
> >
> > Thank You,
> > Nissim Shiman
>

Reply via email to