Table of Contents

Search

  1. Preface
  2. Transformations
  3. Source transformation
  4. Target transformation
  5. Access Policy transformation
  6. Aggregator transformation
  7. B2B transformation
  8. Chunking transformation
  9. Cleanse transformation
  10. Data Masking transformation
  11. Data Services transformation
  12. Deduplicate transformation
  13. Expression transformation
  14. Filter transformation
  15. Hierarchy Builder transformation
  16. Hierarchy Parser transformation
  17. Hierarchy Processor transformation
  18. Input transformation
  19. Java transformation
  20. Java transformation API reference
  21. Joiner transformation
  22. Labeler transformation
  23. Lookup transformation
  24. Machine Learning transformation
  25. Mapplet transformation
  26. Normalizer transformation
  27. Output transformation
  28. Parse transformation
  29. Python transformation
  30. Rank transformation
  31. Router transformation
  32. Rule Specification transformation
  33. Sequence transformation
  34. Sorter transformation
  35. SQL transformation
  36. Structure Parser transformation
  37. Transaction Control transformation
  38. Union transformation
  39. Vector Embedding transformation
  40. Velocity transformation
  41. Verifier transformation
  42. Web Services transformation

Transformations

Transformations

Sequence transformation rules and guidelines

Sequence transformation rules and guidelines

Consider the following guidelines when you create a Sequence transformation:
  • When you map the NEXTVAL or CURRVAL output fields, ensure that the data type of the mapped field is appropriate.
  • When you run the mapping in the Mapping Designer, the current value is not saved so each time you run the mapping, it begins with the initial value.
  • When you run the task in the
    mapping
    task wizard, you can edit the current value to start the sequence with a specified value.
  • Before the Sequence transformation runs,
    Data Integration
    checks for sufficient space between the starting value and the end value. If you set an end value that's too close to the starting value, the mapping fails with a sequence overflow error. This error can occur even if the starting value plus the number of rows processed would be less than the end value. If you encounter a sequence overflow error, increase the end value.
  • You can't use a Sequence transformation in a mapplet.
  • To use the Sequence transformation in advanced mode, the Secure Agent must run on a virtual machine.
  • A self-service cluster might intermittently fail to connect to the agent, which can cause the mapping to fail. Error messages related to this appear in the session logs.
  • In advanced mode, generated values might not increase monotonically. Values are generated based on the order that the Spark engine processes the data.
  • In mappings in SQL ELT mode, you can't use shared sequences.
  • In mappings in SQL ELT mode, a Sequence transformation needs to be connected directly to a downstream Expression transformation or target.

0 COMMENTS

We’d like to hear from you!