Nice Pierre, that's consistent with which I'm experiencing
Currently, this is what i'm using to process csv with header names
different from db table :
Access strategy = Schema text property
Schema text = ...
Treat First Line as Header = True
Ignore CSV Header Column Names = False
In the schema,
If I recall correctly, if you set the property "Ignore CSV Header Column
Names" to true, then it'll take the columns in the same order as defined in
the schema.
Same on the DB side (PutDatabaseRecord), with the property "Translate Field
Names". If false, the field names must match the column names
Hi Pierre,
Thank you for your input
Schema certainly is a key point here. I used a CSVReader with Use Strings
Fields from Header as access strategy.
Moving access strategy to a text-defined schema solve the issue
On side question: in the schema, what are fields name relative to, csv
header or pgs
Hi François,
How did you define your schema in the PutDatabaseRecord processor?
If you're using a CSV Reader and infer the schema using the header, then
all the fields will be considered as strings.
You probably want to define the schema by yourself so that you can define
the type of each column o
Hi all,
This is my first mail on this feed, as I've discovering NiFi a few days ago.
I'm working for a company involved in software development for utilities
networks operators
One of my first use case to test NiFi is to load a csv file in an existing
pgsql table, which sounds like a pretty commo
