[
https://issues.apache.org/jira/browse/PHOENIX-8049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Kyle Purtell updated PHOENIX-8049:
-----------------------------------------
Description:
Because mappers write directly to the index and reducers emit no file records,
a file destination is unnecessary. However, currently what actually happens is
job submission failures caused by "missing" output directories.
Additionally, error handling should pass the exception details in the log
rather than embedding stack traces into the message text. The default logger
configuration truncates log lines at 1000 chars.
was:
IndexTool defaults to {{NullOutputFormat}} when an output path is omitted.
Because mappers write directly to the index and reducers emit no file records,
a file destination is unnecessary. However, currently what actually happens is
job submission failures caused by "missing" output directories.
Additionally, error handling should pass the exception details in the log
rather than embedding stack traces into the message text. The default logger
configuration truncates log lines at 1000 chars.
> IndexTool runs without an output path
> -------------------------------------
>
> Key: PHOENIX-8049
> URL: https://issues.apache.org/jira/browse/PHOENIX-8049
> Project: Phoenix
> Issue Type: Bug
> Components: core
> Affects Versions: 5.3.2
> Reporter: Andrew Kyle Purtell
> Assignee: Andrew Kyle Purtell
> Priority: Minor
> Fix For: 5.4.0, 5.3.3
>
>
> Because mappers write directly to the index and reducers emit no file
> records, a file destination is unnecessary. However, currently what actually
> happens is job submission failures caused by "missing" output directories.
> Additionally, error handling should pass the exception details in the log
> rather than embedding stack traces into the message text. The default logger
> configuration truncates log lines at 1000 chars.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
