You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2023/06/16 20:52:00 UTC

[jira] [Commented] (NIFI-11167) Add Excel Record Reader

    [ https://issues.apache.org/jira/browse/NIFI-11167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17733655#comment-17733655 ] 

ASF subversion and git services commented on NIFI-11167:
--------------------------------------------------------

Commit e4d1dab8f7f901acb62a896acd3d6533caefb7cc in nifi's branch refs/heads/main from dan-s1
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=e4d1dab8f7 ]

NIFI-11167 Added ExcelReader to nifi-poi-nar

- Moved shared schema inference components to nifi-record-serialization-services-shared

This closes #7194

Signed-off-by: David Handermann <ex...@apache.org>


> Add Excel Record Reader
> -----------------------
>
>                 Key: NIFI-11167
>                 URL: https://issues.apache.org/jira/browse/NIFI-11167
>             Project: Apache NiFi
>          Issue Type: New Feature
>          Components: Extensions
>            Reporter: David Handermann
>            Assignee: Daniel Stieglitz
>            Priority: Minor
>          Time Spent: 10h
>  Remaining Estimate: 0h
>
> A new Excel Record Reader should be implemented to support reading XSLX spreadsheet rows as NiFi Records. This Reader will enable integration with various record-oriented components, obviating the need for the narrowly focused ConvertExcelToCSVProcessor. The initial version of the Excel Reader should not support the legacy binary XLS format.
> The ExcelReader should use a library that supports reading from a stream of rows to avoid consuming large amounts of heap memory during processing.
> The ExcelReader should support configurable properties to read selected sheets. With Excel supporting typed field values, some amount of field type mapping will be required. Additional input filtering properties should not be implemented as existing Processors like QueryRecord support a wide variety of filtering and projection use cases.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)