[
https://issues.apache.org/jira/browse/SPARK-48123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17844245#comment-17844245
]
Steve Loughran commented on SPARK-48123:
----------------------------------------
this doesn't handle nested stack traces. I seem to have my comments here
ignored. let me repeat
* deep nested are common, especially those coming from networks, where have to
translate things like aws sdk errors into meaningful and well known exceptions.
* these consist of a chain of exceptions, each with their own message and stack
trace
* any log format which fails to anticipate or support these is inadequate to
diagnose a large portion of the stack traces a failing app will generate
* thus destroying its utility value
has a decision been made to ignore my requirements?
> Provide a constant table schema for querying structured logs
> ------------------------------------------------------------
>
> Key: SPARK-48123
> URL: https://issues.apache.org/jira/browse/SPARK-48123
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
> Affects Versions: 4.0.0
> Reporter: Gengliang Wang
> Assignee: Gengliang Wang
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0
>
>
> Providing a table schema LOG_SCHEMA, so that users can load structured logs
> with the following:
> ```
> spark.read.schema(LOG_SCHEMA).json(logPath)
> ```
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
