-
Notifications
You must be signed in to change notification settings - Fork 353
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Way to relate initial seed to output at the end of an operation chain #1345
Comments
This is linked to #1301. |
After #1301 is done, we should then be able to create an Operation perhaps called 'ExtractItems'. E.g and we ask to extract the second item out of the iterables then the result would be: This would allow us to create an Operation Chain like this: @gchqdev03 - would that work for you? |
@p013570 I think that would work for our use-case. It'd be nice to be able to very easily 'pick up' properties as you traverse, but perhaps that's a separate issue? |
OK great. However, @javadev001001 - I'm not sure what you mean by 'pick up' properties? |
Just to clarify the desired behaviour for the extraction of items..
|
@m607123 the way your code currently looks seems to be going in the right direction. It allows users to plug in any map Function or flatMap Function so they can extract whatever they want. So I would imagine they would do something like:
[
[[1-2], [2-3], [3-4]],
[[1-5], [5-6], [6-7]]
]
This would return: [
[1-2],
[1-5]
]
[
1-2,
1-5
]
[
1,
1
]
[
1
] A bit complicated but quite descriptive. Perhaps we could have a function that merges the first 2 flatmap operations into 1. |
Merged into develop. |
It would be really useful if there was a way to relate the results of a multihop operation chain to the initial seeds that were passed into the chain. If the operation chain has more than one operation and the end result elements/objects do not have an identifier that is easily relatable to any of the seeds that were passed in, then it is difficult to know which seeds resulted in which answers
The text was updated successfully, but these errors were encountered: