[ https://issues.apache.org/jira/browse/NIFI-11167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17707426#comment-17707426 ]
Daniel Stieglitz edited comment on NIFI-11167 at 3/31/23 9:04 PM: ------------------------------------------------------------------ [~exceptionfactory] Is there documentation and or diagrams on how the {code:java} org.apache.nifi.schema.inference.InferSchemaAccessStrategy {code} and its related classes work? I am having a hard time wrapping my head around this in order to integrate this with an Excel reader. I believe I have the basic strategies working but I am looking to see how I can implement the inference and header strategies similar to the CSV reader. was (Author: JIRAUSER294662): [~exceptionfactory] Is there documentation and or diagrams on how the {code:java} org.apache.nifi.schema.inference.InferSchemaAccessStrategy {code} and its related classes work? I am having a hard time wrapping my head around this in order to integrate this with an Excel reader. I have the basic strategies working but I am looking to see how I can implement the inference and header strategies similar to the CSV reader. > 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 > > 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)