Hi @abhaga, the missing fields seem to correspond to list attributes which have been converted from arrays in the source GeoJSON document. A list attribute could contain multiple values as its elements, whereas each field in the destination table can only contain a single value, so FME won't map a list attribute to a field automatically.
See here to learn more about list attribute: About List Attributes
The solution depends on how you need to write the list elements into the destination table.
For example, the "wof:belongsto" array in the GeoJSON example contains six elements (102191575, 85633793, 85977539, etc.). How do you want to write them into the destination table?