[
https://issues.apache.org/jira/browse/NIFI-12491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17859735#comment-17859735
]
Daniel Stieglitz commented on NIFI-12491:
-----------------------------------------
[~brendanbuhr] So I believe the row needs to be specified to identify where the
headers are. All non-empty columns will be assumed to be the headers.
Subsequent data will be read based on those columns. If you want to filter out
any other columns, then the use of QueryRecord could allow you with a SQL query
to pick those columns you want which would then automatically filter out the
ones you do not want.
> ExcelReader - new Schema Access strategy: Use String Fields From Header
> -----------------------------------------------------------------------
>
> Key: NIFI-12491
> URL: https://issues.apache.org/jira/browse/NIFI-12491
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Affects Versions: 1.23.2
> Reporter: Philipp Korniets
> Assignee: Daniel Stieglitz
> Priority: Major
> Attachments: image-2024-06-24-18-01-49-886.png,
> image-2024-06-24-18-02-36-592.png
>
>
> ExcelReader needs an ability similar to CSVReader to "Use String Fields From
> Header" as a Schema Access Strategy.
> Current implementation has:
> 1. Use Schema Name/Schema Text - this option relies on the order of the
> columns. Possible issues - order of the columns change, but types dont. This
> cause further calculations to be erroneous.
> 2. Infer Schema - replaces real column names with column_1,column_2 etc -
> this again loses the "context" of the column and forces us to rely on how
> columns are ordered.
> Any workarounds make workflow more complicated.
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
