[
https://issues.apache.org/jira/browse/TRAFODION-910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suresh Subbiah resolved TRAFODION-910.
--------------------------------------
Resolution: Fixed
> LP Bug: 1412642 - udf- event_log_reader: tm.log_0_xxxx.log is not processed
> by the udf
> --------------------------------------------------------------------------------------
>
> Key: TRAFODION-910
> URL: https://issues.apache.org/jira/browse/TRAFODION-910
> Project: Apache Trafodion
> Issue Type: Bug
> Reporter: Gao, Rui-Xian
> Assignee: Hans Zeller
> Priority: Blocker
> Fix For: 1.1 (pre-incubation)
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
