[
https://issues.apache.org/jira/browse/NIFI-10792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17700844#comment-17700844
]
ASF subversion and git services commented on NIFI-10792:
--------------------------------------------------------
Commit 6c64050a29a42bb36571217f9566116d27ef0a96 in nifi's branch
refs/heads/main from dan-s1
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=6c64050a29 ]
NIFI-10792 Updated ConvertExcelToCSV to handle files over 10 MB
- Refactored to reduce the cognitive complexity in the onTrigger method
- Added log4j-to-slf4j library and adjusted formatting
- Removed unnecessary graphics2d dependency
This closes #7016
Signed-off-by: David Handermann <[email protected]>
> ConvertExcelToCSVProcessor : Failed to convert file over 10MB
> --------------------------------------------------------------
>
> Key: NIFI-10792
> URL: https://issues.apache.org/jira/browse/NIFI-10792
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core UI
> Affects Versions: 1.17.0, 1.16.3, 1.18.0
> Reporter: mayki
> Assignee: Daniel Stieglitz
> Priority: Critical
> Labels: Excel, csv, processor
> Fix For: 1.15.3
>
> Attachments: ConvertExcelToCSVProcessor_1_18_0_with_POI_OLD.PNG,
> ConvertExcelToCSVProcessor_1_19_1.PNG
>
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
> Hello all,
> It seems all version greater 1.15.3 introduce a failure on the processor
> *ConvertExcelToCSVProcessor* with this error :
> {code:java}
> Tried to allocate an array of length 101,695,141, but the maximum length for
> this record type is 100,000,000. If the file is not corrupt or large, please
> open an issue on bugzilla to request increasing the maximum allowable size
> for this record type. As a temporary workaround, consider setting a higher
> override value with IOUtils.setByteArrayMaxOverride() {code}
> I have tested with 2 differences instances nifi version 1.15.3 ==> Work: OK
> And since upgrade in 1.16, 1.17, 1.18 ==> same processsor *failed* with file
> greater than 10MB.
> Could you help us to correct this bug ?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
