[
https://issues.apache.org/jira/browse/IMPALA-8057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong resolved IMPALA-8057.
-----------------------------------
Resolution: Later
I don't think it's worth tracking tasks of this granularity unless someone is
imminently going to do them. Will close to reduce size of backlog.
> Unhelpful messages in impalad.INFO log
> --------------------------------------
>
> Key: IMPALA-8057
> URL: https://issues.apache.org/jira/browse/IMPALA-8057
> Project: IMPALA
> Issue Type: Improvement
> Affects Versions: Impala 3.1.0
> Reporter: Paul Rogers
> Priority: Minor
>
> Am analyzing a log. I seem many lines of the form:
> {noformat}
> I0108 15:27:04.868429 4182 udf.cc:446] Allocate Local:
> FunctionContext=0x7f9745a24430 size=6 result=0x7f9754a08928
> {noformat}
> and
> {noformat}
> 0x7f96ea0cc400
> 0x7f96ea0cc420
> 0x7f96ea0cc440
> {noformat}
> In the current form, these don't convey much information, especially the
> numbers.
> This is probably a trace-level log. But, even there, just displaying hex
> numbers is not super informative.
> Perhaps the log messages need a good scrub to ensure that they are useful.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
