-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Data Retention Rule containing Pipeline condition causes Impact Summary to fail #3074
Comments
at055612
added a commit
that referenced
this issue
Oct 19, 2022
at055612
added a commit
that referenced
this issue
Oct 20, 2022
at055612
added a commit
that referenced
this issue
Oct 20, 2022
at055612
added a commit
that referenced
this issue
Nov 1, 2022
Fix inFolder code. Change store to push filtering by name down to the persistence.
at055612
added a commit
that referenced
this issue
Nov 3, 2022
This is more efficient use of the db. Also add suggestions to some of the searchables.
The following SQL will identify processor filters that use now unsupported term conditions on the select
p.id as processor_id,
pf.id as filter_id,
d.name as pipeline_name,
pf.data as filter_xml
from processor_filter pf
inner join processor p on pf.fk_processor_id = p.id
inner join doc d on p.pipeline_uuid = d.uuid and d.ext = 'meta'
where ExtractValue(
pf.data,
"count(/query/expression//term[./field='Pipeline' and (./condition='EQUALS' or ./condition='CONTAINS' or ./condition='IN' or ./condition='IN_DICTIONARY')])") > 0; |
at055612
added a commit
that referenced
this issue
Nov 3, 2022
at055612
added a commit
that referenced
this issue
Nov 24, 2022
at055612
added a commit
that referenced
this issue
Nov 24, 2022
PR for #3074 - Data Retention Rule containing Pipeline condition causes Impact Summary to fail
Fixed in v7.0.10 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add a rule
Pipeline is aPipelineName
, press save, then hit the Impact Summary go buttonYou should get get a blank popup.
The text was updated successfully, but these errors were encountered: