mattcasters opened a new pull request, #8807:
URL: https://github.com/apache/hop/pull/8807

   Documents the high-volume, insert-heavy SCD2 pattern from issue #8803 as a 
how-to guide.
   
   The page walks through sorted sources, a `record_source` constant, Sorted 
schema merge, Repeat fields with *Current when indicated*, an Analytic Query 
validity range, If null sentinels, and an optional Group By collapse. 
Screenshots from the issue are included, along with the customer 360 
initial-load pipeline and the option to expose the current SCD2 row as an SCD1 
view for facts.
   
   The guide is linked from the how-to index, the manual navigation, Dimension 
lookup/update, Sorted schema merge, Repeat fields, Joins and lookups, Change 
Data Capture, and the getting-started next steps.
   
   fixes #8803
   
   ------------------------
   
   Thank you for your contribution! Follow this checklist to help us 
incorporate your contribution quickly and easily:
   - [ ] Run `mvn clean install apache-rat:check` to make sure basic checks 
pass. A more thorough check will be performed on your pull request 
automatically.
   - [x] If you have a group of commits related to the same change, please 
squash your commits into one and force push your branch using `git rebase -i`.
   - [x] Mention the appropriate issue in your description (for example: 
`addresses #123`), if applicable.
   
   To make clear that you license your contribution under the [Apache License 
Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   you have to acknowledge this by using the following check-box.
   
   - [x] I hereby declare this contribution to be licensed under the [Apache 
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   - [ ] In any other case, please file an [Apache Individual Contributor 
License Agreement](https://www.apache.org/licenses/icla.pdf).
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to