Sunday, April 03, 2016
A pipeline is composed of a collection of components. Each component performs a specific function during the transformation of source data into Endeca records. Components are linked together by means of cross-references, giving the pipeline a sequential flow.
Find out the way below to debug Endeca Pipeline Components transformation working as expected or not.
1. Set the global log level. Log level can be set in Forge component using -v[f|e|w|i|d] option. Use -vd flag to increase Forge logging visibility as debug mode.
2. -printRecords flag option to print records as they are produced by each pipeline component.
3. Use Record Adapter - Insert a Record adapter between the pipeline components that needs to be review and set direction as Output. Make sure the Record source the component whose output needs to be examined. Pipeline stores the data in XML format and can be seen output XML under <<Endeca_App>>/data/processing folder.
Find out screen shot below
Find out the way below to debug Endeca Pipeline Components transformation working as expected or not.
1. Set the global log level. Log level can be set in Forge component using -v[f|e|w|i|d] option. Use -vd flag to increase Forge logging visibility as debug mode.
2. -printRecords flag option to print records as they are produced by each pipeline component.
3. Use Record Adapter - Insert a Record adapter between the pipeline components that needs to be review and set direction as Output. Make sure the Record source the component whose output needs to be examined. Pipeline stores the data in XML format and can be seen output XML under <<Endeca_App>>/data/processing folder.
Find out screen shot below
No comments
Post a Comment
Note: Only a member of this blog may post a comment.