udf- event_log_reader: tm.log_0_xxxx.log is not processed by the udf

[gaoruixian]

Since all tm.log_0_xxxx.log are empty on my testing system(centos-mapr1), I copied tm.log to tm.log_0_7476.log. It has content so should be processed by the udf.

I created tm.log_0_7476.log on both node0(centos-mapr1) and node2(centos-mapr3) because logs on node0 won’t show up.
But there is no record of tm.log_0_7476.log returned by the udf.

tm.log will be processed, but not tm.log_0_xxxx.log

Tried on both workstation and cluster –

SQL>select count(*) from udf(event_log_reader('f')) where log_file_name like 'tm.log_%';

(EXPR)
--------------------
                   0

--- 1 row(s) selected.

[Suresh Subbiah (suresh-subbiah)]

Likely a bug in the UDF. I can work on it if Adriana does not mind.

[Hans Zeller (hans-zeller)]

There was a bug in the file name test. When the file name contained the string ".log" internally, not just at the end, we failed the test that was supposed to check that the file name ends in ".log".

[Hans Zeller (hans-zeller)]

Fix committed in https://review.trafodion.org/#/c/998/

[gaoruixian (ruixian-gao)]

The fix has been verified on traf_0122 build on centos-mapr1.