Skip to main content
  • EN

Hi,

My workspace worked in 2019.x, but I noticed an issue when it was migrated to 2022.2.0.

 

I read in multiple *.TXT files from a single folder using a FeatureReader (passing the folder name with a parameter), they are actually csv files - so use that as the format. In the Parameters I set "Field Names Line" to None as there are none. I expose "col0,col1". It reads all the files and I get the correct feature count, but it reads the first file fine, but all subsequent files it uses the values from the first line as the field names - effectively ignoring the "Field Names Line" Parameter.

 

Is this a bug? As I say, it worked before.

 

Kind regards

 

John

Hello @johnt​, are you able to share a few sample / mock datasets with a workspace that demonstrates the issue you're experiencing? Otherwise, it would be good to check if there are any upgradable transformers in the workspace (in the Naivatore pane)? Can you share the value set for the 'Output Ports' parameter in the FeatureReader? (see: FeatureReader > Parameters > Output > Output Ports). Happy to help, Kailin.

Hi @kailinatsafe​, good shout on the upgradeable transformers. This workspace appears to be one that missed the upgrade process. So I added a new feature reader and repeated, but I have the same issue. As I use dynamic parameters, the single output port outputs on Generic (where I expose col0, col1 to change the name and manipulate as necessary). I just downloaded 2023.1 and copied the feature reader into there and it runs as it should (ie not trying to set the first row of data as the schema for all files after the first file). Should be easy to replicate.

Hi @kailinatsafe​, good shout on the upgradeable transformers. This workspace appears to be one that missed the upgrade process. So I added a new feature reader and repeated, but I have the same issue. As I use dynamic parameters, the single output port outputs on Generic (where I expose col0, col1 to change the name and manipulate as necessary). I just downloaded 2023.1 and copied the feature reader into there and it runs as it should (ie not trying to set the first row of data as the schema for all files after the first file). Should be easy to replicate.

Hello @johnt​, sorry for not reaching out again sooner! Can you pass along a screenshot of your FeatureReader parameters please? I want to make sure I have everything configured similarly. All the best, Kailin

Hello @johnt​, sorry for not reaching out again sooner! Can you pass along a screenshot of your FeatureReader parameters please? I want to make sure I have everything configured similarly. All the best, Kailin

Hi @kailinatsafe​ , also sorry for late reply - busy week! Please see attached, but that attachment widget thing is horrible. Only one image per reply it seems. I did try changing the Feature Type Name(s) parameter to File Name - and other variations. I have a work around to read as Text File with text_line_data and splitting by comma - but I can only do this as the data is a known quantity and good quality, i.e. no commas expected in the data.

 

Reply


Community Stats

30,108
Posts
114,295
Replies
37,745
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.