[
https://issues.apache.org/jira/browse/NIFI-12491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17859712#comment-17859712
]
Daniel Stieglitz edited comment on NIFI-12491 at 6/24/24 3:39 PM:
------------------------------------------------------------------
[~iiojj2] [~brendanbuhr]
I would like to clarify questions I have with you both.
# Did you envision the header strategy to only allow the first row to have the
headers or do you foresee the need to choose which row has the headers? In
other words could the 'Starting Row' property be used to determine where the
header column names begin?
# Did you envision there can be multiple sheets in one spreadsheet with the
same header? In other words, did you foresee the ability for a user to choose
multiple sheets with this header strategy and expect there to a header row on
all of those sheets?
was (Author: JIRAUSER294662):
[~iiojj2] [~brendanbuhr]
I would like to clarify questions I have with you both.
# Did you envision the header strategy to only allow the first row to have the
headers or do you foresee the need to choose which row has the headers?
# Did you envision there can be multiple sheets in one spreadsheet with the
same header? In other words, did you foresee the ability for a user to choose
multiple sheets with this header strategy and expect there to a header row on
all of those sheets?
> 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
>
> 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)
