[
https://issues.apache.org/jira/browse/TRAFODION-910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14720947#comment-14720947
]
Suresh Subbiah commented on TRAFODION-910:
------------------------------------------
Changed in trafodion:
importance: Undecided → High
milestone: none → r1.1
assignee: nobody → Adriana Fuentes (adriana-fuentes)
Suresh Subbiah (suresh-subbiah) wrote on 2015-01-20: #1
Likely a bug in the UDF. I can work on it if Adriana does not mind.
Changed in trafodion:
assignee: Adriana Fuentes (adriana-fuentes) → Suresh Subbiah
(suresh-subbiah)
Aruna Sadashiva (aruna-sadashiva) on 2015-01-20
Changed in trafodion:
importance: High → Critical
Hans Zeller (hans-zeller) wrote on 2015-01-21: #2
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".
Changed in trafodion:
assignee: Suresh Subbiah (suresh-subbiah) → Hans Zeller (hans-zeller)
status: New → In Progress
Hans Zeller (hans-zeller) wrote on 2015-01-21: #3
Fix committed in https://review.trafodion.org/#/c/998/
Changed in trafodion:
status: In Progress → Fix Committed
gaoruixian (ruixian-gao) wrote on 2015-01-26: #4
The fix has been verified on traf_0122 build on centos-mapr1.
Changed in trafodion:
status: Fix Committed → Fix Released
> 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)
