My app has a static lookup my_lookup.csv with static data.
This is my sample csv data which cause a failure.
DataOne,DataTwo ,"Data Three with double quotes & commas, such as this=""Hi@Im.in "", that=""Hi@You.in"". "
I got AppInspect below failures.
This .csv lookup is not formatted as valid csv. Details: The number of columns in row 2 (=4 columns) does not match the number of columns in the csv's header (=3 columns). The header is considered row 1. Please edit/remove this lookup. File: lookups/my_lookup.csv
Question: My csv file is proper with 3 header (=3 columns) with proper data.Then why AppInspect considering =4 columns ? Is it bug in AppInspect? Or I have to handle this scenario in different way.
Kamlesh - thank you for catching this! Indeed it appears that your sample CSV is recognized and parsed correctly by Splunk's inputlookup command so this AppInspect check is at fault. We have filed a bug and hope to align our parsing of CSV files with the inputlookup implementation. For now please ignore this check failure.