Screenshot of a tFileInputJSON Component
A few readers have asked about tFileInputJSON. This post shows a simple job that writes the JSON structure shown in the foreground.
This JSON structure is based on the a structure "attribs" which has fields of name and value.
The result of running the job is the following
Starting job JSONInputJob at 15:41 30/03/2012.
[statistics] connecting to socket on port 3501[statistics] connected
req|1
data|2
[statistics] disconnected
Job JSONInputJob ended at 15:41 30/03/2012. [exit code=0]
Note that the two JSON paths are not correlated. This means that every attribs record will need to have the full set of fields. Taking out 'name' from req|1 will shuffle up the name of data.
This JSON structure is based on the a structure "attribs" which has fields of name and value.
 |
| A Talend Job Featuring the tFileInputJSON Component |
Starting job JSONInputJob at 15:41 30/03/2012.
[statistics] connecting to socket on port 3501[statistics] connected
req|1
data|2
[statistics] disconnected
Job JSONInputJob ended at 15:41 30/03/2012. [exit code=0]
Note that the two JSON paths are not correlated. This means that every attribs record will need to have the full set of fields. Taking out 'name' from req|1 will shuffle up the name of data.
No comments:
Post a Comment