HI, I would like to eliminate several fetures comming into process, based on another table.
the reference tale is big, so tester is not an option.
Thanks in advance for any ideas.
LP, Miha
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
- 8394 replies
There are several possible solutions, but the easiest is perhaps to use a FeatureMerger, set to "Suppliers first", with the reference table connected to the Supplier port. However, you have to make sure that the reference table is read before the other data, e.g. using a separate reader. (Using "suppliers first" isn't crucial to this solution, but it will be more efficient.)
The output you want will be available on the UnmergedRequestor port.
+44- Influencer
- 3427 replies
Depending on the format of your reference table, the DatabaseJoiner might be a good option here, just using the output from the unjoined port
+20- Safer
- 3719 replies
Depending on the format of your reference table, the DatabaseJoiner might be a good option here, just using the output from the unjoined port
And be sure you've got an index set on the ID column in your reference table. If the # of "table 1" entries is drastically less than the # of entries in the reference table, I'd think DatabaseJoiner would be the way to go. But it might be worth comparing head to head with FeatureMerger as along as you do the suppliers first trick below...
+1Thanks for both solutions. I tried both transformers - both executed the model correctly and perform same solution. The database joiner was a little bit faster and to me is not so confusing, while you dont have to attach more than one input with lines (second is set directly in transformer).
The model is validating database if the synchronization of some points was correct (if they are in right place - spatialy)- those wich are diagnostified as possibile wrong and than confirmed as right are deployed into the referenced table, that next run of the model - iteration leave them as correct.
thanks, Bye
