OpenedDataObjInp object and data object path

[ll4strw]

OpenedDataObjInp object and data object path

[trel]

with this Python rule...

def pep_api_data_obj_read_pre(rule_args, callback, rei):
    callback.writeLine("serverLog", rule_args[2])

I see...

Attempted to extract a boost::python::object containing a non-conforming type

---

with iRODS Rule Language...

pep_api_data_obj_read_pre(*INSTANCE, *COMM, *DATAOBJREADINP, *BUFF){
  writeLine("serverLog", *DATAOBJREADINP)
}

I see...

"log_message":"writeLine: inString = KeyValue[7]:bytesWritten=0;keyValPair_t=nullptr;l1descInx=3;len=12;offset=0;oprType=0;whence=0;\n"

So, indeed, object path does not appear to be there...

And looking at that data structure... indeed it is not...

irods/lib/api/include/irods/dataObjInpOut.h

Lines 95 to 103 in efa5f26

	typedef struct OpenedDataObjInp {
	int l1descInx; /* for read, write, close */
	int len; /* length of operation for read, write */
	int whence; /* used for lseek */
	int oprType;
	rodsLong_t offset;
	rodsLong_t bytesWritten; /* for close */
	keyValPair_t condInput; /* include chksum flag and value */
	} openedDataObjInp_t;

So... the question is how do we get that information?

[alanking]

With the l1 descriptor, one can use msi_get_file_descriptor_info to get the obj path and much more:

https://docs.irods.org/4.3.2/doxygen/microservices_2src_2get__file__descriptor__info_8cpp.html#ac1cf34b6716c433bfc8cf0b6a020b95b

As it returns a JSON object, you may also need to use the JSON microservices to get at the information.

It shouldn't be very expensive because the l1 descriptor is in the same agent process. Also, I haven't tested this. :)

[trel]

Oh, nice. Sounds like we need an example in the docs somewhere once we see it work.