[
https://issues.apache.org/jira/browse/PHOENIX-5632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17045859#comment-17045859
]
Chinmay Kulkarni edited comment on PHOENIX-5632 at 2/26/20 8:09 PM:
--------------------------------------------------------------------
[~kadir] [~gjacoby] Any other ideas you guys have on what might be useful to
store in the TASK_DATA json? Currently (as of when this JIRA was created) we
only store the task status or job ID in case of index rebuilds. Stack trace in
case of failures is one option. FYI [~christine.feng]
was (Author: ckulkarni):
[~kadir] [~gjacoby] Any other ideas you guys have on what might be useful to
store in the TASK_DATA json? Currently (as of when this JIRA was created) we
only store the task status. Stack trace in case of failures is one option. FYI
[~christine.feng]
> Add more information to SYSTEM.TASK TASK_DATA field apart from the task status
> ------------------------------------------------------------------------------
>
> Key: PHOENIX-5632
> URL: https://issues.apache.org/jira/browse/PHOENIX-5632
> Project: Phoenix
> Issue Type: Improvement
> Affects Versions: 4.15.0
> Reporter: Chinmay Kulkarni
> Priority: Minor
> Labels: beginner, newbie
> Fix For: 4.15.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It would be helpful for debugging if we could add more information to the
> TASK_DATA json that is upserted into SYSTEM.TASK apart from just the task
> status. For example, in failures cases, perhaps we can add the stack trace
> for the failing task.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
