Page Comparison

...

Also, the description will include the supported data types, which will help user to enter the correct or expected types for particular field.

Assumptions:

For every structured record received to the transform plugin, the output will also be a single structured record.

Example

Questions/Clarifications

...

1. For defining the output field types, field names and xpath value, following approach can be used:
   1. Common widget with 2 text boxes and a drop down   or 
   2. key value widget to take the output field name and xpath expression, and a second output schema widget
      
      

2. User is able to specify what should happen when there is error in processing. Errors could be:

1. IllegalCharacter

2. Type conversion error

3. NULL or EMPTY value for non nullable column value

   
   

3.  

   Requirement: User is NOT able to XPaths that are arrays. It should be runtime error. 

    Understanding: xPath returning multiple nodes with same name. Suppose we have below input:

   <Cities>

       <City>Paris</City>

       <City>Lyon</City>

       <City>Marseille</City>

    </Cities>

    And user wants to extract city ['Paris', 'Lyon', 'Marseille'] and provides xPath till /Cities /City. Then as per our use case, we should throw an error.

    a. Is this understanding correct or are we missing anything on xPath arrays?

    

   
   

Questions:

1. If the xpath evaluates to a node with child elements, how should the plugin handle this?

   1. Return the text in child node elements as comma separated values
   2. Return value as an XML record, similar to the record emitted by XMLReader plugin
   3. Throw exception
   4. or anything other than this
2. How can we get data-set in transform plugin; could not find getDataset() in TransformContext object?