[
https://issues.apache.org/jira/browse/NIFI-7738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nissim Shiman updated NIFI-7738:
--------------------------------
Description:
A feature that some NiFi administrators would find useful is doing an inverse
search on provenance.
So for example, instead of just being able to search on provenance to find
provenance with Event Type of SEND
we also have the option of finding all provenance that does NOT have Event Type
of SEND.
The underlying apache lucene already supports Boolean queries.
Actually, NiFi is already doing a Boolean query.
But now instead of doing an Occur.MUST, NiFi will also be able to do an
Occur.MUST_NOT [1]
There will be a GUI change as well, (see attached snapshot/picture) as there
will be a "NOT" column header at the far right of the Provenance's Search
Events pop up, with checkboxes underneath it (i.e. a checkbox to the right of
each fieldname/value that a user can query provenance events for). If the
checkbox is checked, then the user is indicating to do an inverse query for the
value entered.
[1]
[https://github.com/apache/nifi/blob/rel/nifi-1.11.4/nifi-nar-bundles/nifi-provenance-repository-bundle/nifi-persistent-provenance-repository/src/main/java/org/apache/nifi/provenance/lucene/LuceneUtil.java#L108]
was:
A feature that some NiFi administrators would find useful is doing an inverse
search on provenance.
So for example, instead of just being able to search on provenance to find
provenance with Event Type of SEND
we also have the option of finding all provenance that does NOT have Event Type
of SEND.
The underlying apache lucene already supports Boolean queries.
Actually, NiFi is already doing a Boolean query.
But now instead of doing an Occur.MUST, NiFi will also be able to do an
Occur.MUST_NOT [1]
There will be a GUI change as well, (see attached snapshot/picture) as there
will be a "NOT" column header at the far right of the Provenance's Search
Events pop up, with checkboxes underneath it (i.e. a checkbox to the right of
each fieldname/value that a user can query provenance events for). If the
checkbox is checked, then the user is indicating to do an inverse query for the
value entered.
[1]
https://github.com/apache/nifi/blob/main/nifi-nar-bundles/nifi-provenance-repository-bundle/nifi-persistent-provenance-repository/src/main/java/org/apache/nifi/provenance/lucene/LuceneUtil.java#L108
> Provenance Search Events - add feature to allow inverse query
> -------------------------------------------------------------
>
> Key: NIFI-7738
> URL: https://issues.apache.org/jira/browse/NIFI-7738
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Nissim Shiman
> Assignee: Nissim Shiman
> Priority: Major
> Fix For: 1.13.0
>
> Attachments: provenanceSearchEvents_InverseSearch.png
>
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> A feature that some NiFi administrators would find useful is doing an inverse
> search on provenance.
> So for example, instead of just being able to search on provenance to find
> provenance with Event Type of SEND
> we also have the option of finding all provenance that does NOT have Event
> Type of SEND.
> The underlying apache lucene already supports Boolean queries.
> Actually, NiFi is already doing a Boolean query.
> But now instead of doing an Occur.MUST, NiFi will also be able to do an
> Occur.MUST_NOT [1]
> There will be a GUI change as well, (see attached snapshot/picture) as there
> will be a "NOT" column header at the far right of the Provenance's Search
> Events pop up, with checkboxes underneath it (i.e. a checkbox to the right of
> each fieldname/value that a user can query provenance events for). If the
> checkbox is checked, then the user is indicating to do an inverse query for
> the value entered.
>
>
> [1]
> [https://github.com/apache/nifi/blob/rel/nifi-1.11.4/nifi-nar-bundles/nifi-provenance-repository-bundle/nifi-persistent-provenance-repository/src/main/java/org/apache/nifi/provenance/lucene/LuceneUtil.java#L108]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
