Customer Portal

Calling the process of storage nodes

Comments 4

  • Avatar
    hwhwhw
    0
    Comment actions Permalink
    I contrast etl some similar products, these products are in the process of storage support, I would like to cloverEtl open-source organizations achieve this demand should not be very difficult?
  • Avatar
    hwhwhw
    0
    Comment actions Permalink
    You think that the demand is not necessary?
    I sincerely hope that the functions of cloverETL can be more powerful.
  • Avatar
    avackova
    0
    Comment actions Permalink
    Hi,
    could you please explain more what you think? Something like you wrote in first post can do DBInputTable: when you set maxErrors>0 then correct records will be sent to database and incorrect you can log.
  • Avatar
    hwhwhw
    0
    Comment actions Permalink
    Thank you for your response, I think, this node will be responsible only for the importation of the record sent to the database server storage process, and can return to the stored procedure in the definition of parameters.
    Each node can be set up through the corresponding record of success and the failure of the information recorded information output to a designated location, this should belong to log module functions.
    Successful track record is based on the number of users in the storage process is set up transactions, and if the settings and the affairs of the rollback transactions, the records of the number of so successful is 0.
    (MaxErrors attributes) in the process of storage services with high-level should be as DB_OUTPUT_TABLE nodes in the errorAction attribute priority.
    Output port storage output value of the return process.

    Example:
    <Node id="DB_CALL_PROCEDURE_0" type="DB_CALL_PROCEDURE" errorAction="ROLLBACK" fieldMap="cloverField=storageProcessArgs" />

Please sign in to leave a comment.