Advertising

Yuri edited comment on NIFI-4234 at 8/5/17 7:56 PM:
----------------------------------------------------
It seems the current simple regex match on processor tags doesn't fit for a bit
more complex use cases.
Queries containing the tag separator char ({{,}}) should be treated separately.
In this particular case the query would be tokenized and behave like:
"_database && rdbms_". This way it makes sense to me, since you are being more
specific by adding tags.
In this case the "_database rdbms_" query wouldn't work. Since tags like "_data
science_" exist, the space char can't be treated like a token separator.
I'm not sure an actual query language is needed.
was (Author: yuri1969):
It seems the current simple regex match on processor tags doesn't fit for a bit
more complex use cases.
Queries containing the tag separator char ({{,}}) should be treated separately.
In this particular case the query would be tokenized and behave like:
"_database && rdbms_". This way it makes sense to me, since you are being more
specific by adding tags.
In this case the "_database rdbms_" query wouldn't work. Since tags like "_data
science_" exist, the {{ }} can't be treated like a token separator.
I'm not sure an actual query language is needed.
> The Filter in the Add Processor window should return valid results even if
> search terms do not exactly match tags
> -----------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-4234
> URL: https://issues.apache.org/jira/browse/NIFI-4234
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core UI
> Reporter: Andrew Lim
> Priority: Minor
>
> The filter field should be more forgiving. For example, if you enter
> "database, rdbms" you get 2 results (ConvertJSONToSQL and PutSQL processors).
> I would think the following would also return the same results, but you get
> none:
> "database,rdbms"
> "database rdbms"
> "rdbms, database"
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)