irods: Removing collections without forcing throws `specificQuery status = -853000` in logs

• main (code change only)
• 4-3-stable (code change only)
• 4-2-stable (docs only)

---

Bug Report

iRODS Version, OS and Version

4.2.11 centos7, 4.3.0 almalinux8

What did you try to do?

I tried to remove a collection (no matter that collection has any content) without using f option by irm r and PRC. Meaning I tried to move it to my trash.

Expected behavior

I expected that collection to be removed without any noise.

Observed behavior (including steps to reproduce, if applicable)

I observed that collection is removed (moved to the trash collection) with info level logs outputs concerning with specificQuery.

client:

imkdir test
irm -r test

logs of 4.3.0:

irods stdout | {"log_category":"legacy","log_facility":"local0","log_level":"info","log_message":"_rsSpecificQuery: specificQuery status = -853000","request_api_name":"RM_COLL_AN","request_api_number":679,"request_api_version":"d","request_client_user":"rods","request_host":"10.0.2.100","request_proxy_user":"rods","request_release_version":"rods4.3.0","server_host":"dev-u0137480-instance1.irods.t.icts.kuleuven.be","server_pid":84121,"server_timestamp":"2023-02-10T09:57:23.821Z","server_type":"agent"}
irods stdout | {"log_category":"legacy","log_facility":"local0","log_level":"info","log_message":"rsSpecificQuery: rcSpecificQuery failed, status = -853000","request_api_name":"RM_COLL_AN","request_api_number":679,"request_api_version":"d","request_client_user":"rods","request_host":"10.0.2.100","request_proxy_user":"rods","request_release_version":"rods4.3.0","server_host":"dev-u0137480-instance1.irods.t.icts.kuleuven.be","server_pid":84121,"server_timestamp":"2023-02-10T09:57:23.821Z","server_type":"agent"}
irods stdout | {"log_category":"legacy","log_facility":"local0","log_level":"info","log_message":"Note: DataObjInCollReCur specific-Query failed (not defined?), running standard query, status=-853000","request_api_name":"RM_COLL_AN","request_api_number":679,"request_api_version":"d","request_client_user":"rods","request_host":"10.0.2.100","request_proxy_user":"rods","request_release_version":"rods4.3.0","server_host":"dev-u0137480-instance1.irods.t.icts.kuleuven.be","server_pid":84121,"server_timestamp":"2023-02-10T09:57:23.821Z","server_type":"agent"}

logs of 4.2.11:

rsyslogd stdout | 2023-02-10T10:39:18.558994+01:00 dev-u0137480 rodsServer[10946]: u0137480 - NOTICE: _rsSpecificQuery: specificQuery status = -853000
rsyslogd stdout | 2023-02-10T10:39:18.559092+01:00 dev-u0137480 rodsServer[10946]: u0137480 - NOTICE: rsSpecificQuery: rcSpecificQuery failed, status = -853000
rsyslogd stdout | 2023-02-10T10:39:18.559143+01:00 dev-u0137480 rodsServer[10946]: u0137480 - NOTICE: Note: DataObjInCollReCur specific-Query failed (not defined?), running standard query, status=-853000

What is the DataObjInCollReCur specific query? Should we add it? Does it hurt anything if we dont add?