[
https://issues.apache.org/jira/browse/NIFI-6680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16933356#comment-16933356
]
Tamas Palfy commented on NIFI-6680:
-----------------------------------
Wondering if it would make sense to actually enhance the
{{org.apache.nifi.serialization.record.RecordSchema}} interface with something
like this:
{code:java}
/**
* @param mutator formatting logic to run on all fields
* @return the names of the fields after applying the mutator to each
*/
List<String> getFieldNames(Function<String, String> mutator);
{code}
Could be an overkill only for this case but the idea would be that similar
issues may come up in other places. And the concrete issue could vary (e.g. fix
width, prefix/suffix, encoding, to name a few).
> Nifi PutKudu processor - Convert record field names to lowercase
> ----------------------------------------------------------------
>
> Key: NIFI-6680
> URL: https://issues.apache.org/jira/browse/NIFI-6680
> Project: Apache NiFi
> Issue Type: Wish
> Components: Extensions
> Affects Versions: 1.9.2
> Reporter: Kevin J McCarthy
> Priority: Major
> Original Estimate: 1h
> Time Spent: 0.5h
> Remaining Estimate: 0.5h
>
> Kudu supports case sensitive column names while query tools built over Kudu
> (eg. Impala) do not. If a table is created via Impala, which is the most
> common use case, all column names are converted to lowercase. If an incoming
> record in a FlowFile contains uppercase column names, the columns won't match
> the schema of the destination table unless the schema for the record is
> modified to have lowercase field names.
> Rather than converting the schema of the record, I propose field names are
> converted to lowercase before they are put into Kudu.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
