{"action":"created","issue":{"url":"https://api.github.com/repos/datacleaner/DataCleaner/issues/1446","repository_url":"https://api.github.com/repos/datacleaner/DataCleaner","labels_url":"https://api.github.com/repos/datacleaner/DataCleaner/issues/1446/labels{/name}","comments_url":"https://api.github.com/repos/datacleaner/DataCleaner/issues/1446/comments","events_url":"https://api.github.com/repos/datacleaner/DataCleaner/issues/1446/events","html_url":"https://github.com/datacleaner/DataCleaner/issues/1446","id":165756863,"number":1446,"title":"Tool for creating a dictionary/staging table that can be used in the same job","user":{"login":"jhorcicka","id":13213915,"avatar_url":"https://avatars.githubusercontent.com/u/13213915?v=3","gravatar_id":"","url":"https://api.github.com/users/jhorcicka","html_url":"https://github.com/jhorcicka","followers_url":"https://api.github.com/users/jhorcicka/followers","following_url":"https://api.github.com/users/jhorcicka/following{/other_user}","gists_url":"https://api.github.com/users/jhorcicka/gists{/gist_id}","starred_url":"https://api.github.com/users/jhorcicka/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jhorcicka/subscriptions","organizations_url":"https://api.github.com/users/jhorcicka/orgs","repos_url":"https://api.github.com/users/jhorcicka/repos","events_url":"https://api.github.com/users/jhorcicka/events{/privacy}","received_events_url":"https://api.github.com/users/jhorcicka/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/datacleaner/DataCleaner/labels/Type:%20Question","name":"Type: Question","color":"fbca04"}],"state":"open","locked":false,"assignee":{"login":"jhorcicka","id":13213915,"avatar_url":"https://avatars.githubusercontent.com/u/13213915?v=3","gravatar_id":"","url":"https://api.github.com/users/jhorcicka","html_url":"https://github.com/jhorcicka","followers_url":"https://api.github.com/users/jhorcicka/followers","following_url":"https://api.github.com/users/jhorcicka/following{/other_user}","gists_url":"https://api.github.com/users/jhorcicka/gists{/gist_id}","starred_url":"https://api.github.com/users/jhorcicka/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jhorcicka/subscriptions","organizations_url":"https://api.github.com/users/jhorcicka/orgs","repos_url":"https://api.github.com/users/jhorcicka/repos","events_url":"https://api.github.com/users/jhorcicka/events{/privacy}","received_events_url":"https://api.github.com/users/jhorcicka/received_events","type":"User","site_admin":false},"assignees":[{"login":"jhorcicka","id":13213915,"avatar_url":"https://avatars.githubusercontent.com/u/13213915?v=3","gravatar_id":"","url":"https://api.github.com/users/jhorcicka","html_url":"https://github.com/jhorcicka","followers_url":"https://api.github.com/users/jhorcicka/followers","following_url":"https://api.github.com/users/jhorcicka/following{/other_user}","gists_url":"https://api.github.com/users/jhorcicka/gists{/gist_id}","starred_url":"https://api.github.com/users/jhorcicka/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jhorcicka/subscriptions","organizations_url":"https://api.github.com/users/jhorcicka/orgs","repos_url":"https://api.github.com/users/jhorcicka/repos","events_url":"https://api.github.com/users/jhorcicka/events{/privacy}","received_events_url":"https://api.github.com/users/jhorcicka/received_events","type":"User","site_admin":false}],"milestone":null,"comments":1,"created_at":"2016-07-15T10:28:28Z","updated_at":"2016-07-15T10:56:03Z","closed_at":null,"body":"In some of our tasks we need to simulate SQL \"...where exists (select ... where A and B and C...)...\". We do it with the help of staging tables or dictionaries that we create in a separate job as a pre-phase. Then in the main DC job we use it by LookupTable. \r\n\r\nIt would be much better if the task was implemented by a single job. I could image a component that would do a separate call to the datastore for each row (very ineffective) but still the power of specifying conditions is very limited in this way. \r\n\r\nSo, I'd like to ask if there is some \"simple\" way to introduce a new component (or whatever) that we could use to basically define two streams and then do a lookup from one to the other. \r\n\r\n![exists](https://cloud.githubusercontent.com/assets/13213915/16871373/d95c389c-4a86-11e6-8c53-198d23650bd3.png)\r\n\r\nIn the blue area imagine a chain of various conditions/filters. The red area is a place where I would like to see a new-working component that can simulate \"...where exists...\". \r\n"},"comment":{"url":"https://api.github.com/repos/datacleaner/DataCleaner/issues/comments/232922276","html_url":"https://github.com/datacleaner/DataCleaner/issues/1446#issuecomment-232922276","issue_url":"https://api.github.com/repos/datacleaner/DataCleaner/issues/1446","id":232922276,"user":{"login":"LosD","id":1282832,"avatar_url":"https://avatars.githubusercontent.com/u/1282832?v=3","gravatar_id":"","url":"https://api.github.com/users/LosD","html_url":"https://github.com/LosD","followers_url":"https://api.github.com/users/LosD/followers","following_url":"https://api.github.com/users/LosD/following{/other_user}","gists_url":"https://api.github.com/users/LosD/gists{/gist_id}","starred_url":"https://api.github.com/users/LosD/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/LosD/subscriptions","organizations_url":"https://api.github.com/users/LosD/orgs","repos_url":"https://api.github.com/users/LosD/repos","events_url":"https://api.github.com/users/LosD/events{/privacy}","received_events_url":"https://api.github.com/users/LosD/received_events","type":"User","site_admin":false},"created_at":"2016-07-15T10:56:03Z","updated_at":"2016-07-15T10:56:03Z","body":"We've been talking about something similar lately.  It would make much more sense with a join component that used existing available tables instead of the table lookup that is both more annoying to use, and doesn't show very well what it does. \r\n\r\nFor it to be really good, we need two things to work properly, though: The MultiStreamComponent needs to work with competent outputs (and preferably also multiple output streams), and it needs to be easier to add more datastores to the job. \r\n\r\nIt would also get rid of  one of the enormously annoying things with TableLookup: There's no way to use templating. "}}
{"actor":{"display_login":"LosD"}}