{"action":"created","issue":{"url":"https://api.github.com/repos/knowbi/knowbi-pentaho-pdi-neo4j-output/issues/55","repository_url":"https://api.github.com/repos/knowbi/knowbi-pentaho-pdi-neo4j-output","labels_url":"https://api.github.com/repos/knowbi/knowbi-pentaho-pdi-neo4j-output/issues/55/labels{/name}","comments_url":"https://api.github.com/repos/knowbi/knowbi-pentaho-pdi-neo4j-output/issues/55/comments","events_url":"https://api.github.com/repos/knowbi/knowbi-pentaho-pdi-neo4j-output/issues/55/events","html_url":"https://github.com/knowbi/knowbi-pentaho-pdi-neo4j-output/issues/55","id":367797792,"node_id":"MDU6SXNzdWUzNjc3OTc3OTI=","number":55,"title":"For Graph Output have Relationship Names based on a Property","user":{"login":"davidlrosenblum","id":21196824,"node_id":"MDQ6VXNlcjIxMTk2ODI0","avatar_url":"https://avatars1.githubusercontent.com/u/21196824?v=4","gravatar_id":"","url":"https://api.github.com/users/davidlrosenblum","html_url":"https://github.com/davidlrosenblum","followers_url":"https://api.github.com/users/davidlrosenblum/followers","following_url":"https://api.github.com/users/davidlrosenblum/following{/other_user}","gists_url":"https://api.github.com/users/davidlrosenblum/gists{/gist_id}","starred_url":"https://api.github.com/users/davidlrosenblum/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/davidlrosenblum/subscriptions","organizations_url":"https://api.github.com/users/davidlrosenblum/orgs","repos_url":"https://api.github.com/users/davidlrosenblum/repos","events_url":"https://api.github.com/users/davidlrosenblum/events{/privacy}","received_events_url":"https://api.github.com/users/davidlrosenblum/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-10-08T13:45:20Z","updated_at":"2018-11-16T17:36:19Z","closed_at":null,"author_association":"NONE","body":"Take the case of employee we want the relationship to be IS_CURRENT if they are an employee today, and IS_PREVIOUS if they are not.  A property can be set with this in a previous step.\r\n\r\nThe other use case is if the RELATIONSHIP name is data driven, e.g. in the input."},"comment":{"url":"https://api.github.com/repos/knowbi/knowbi-pentaho-pdi-neo4j-output/issues/comments/439469126","html_url":"https://github.com/knowbi/knowbi-pentaho-pdi-neo4j-output/issues/55#issuecomment-439469126","issue_url":"https://api.github.com/repos/knowbi/knowbi-pentaho-pdi-neo4j-output/issues/55","id":439469126,"node_id":"MDEyOklzc3VlQ29tbWVudDQzOTQ2OTEyNg==","user":{"login":"davidlrosenblum","id":21196824,"node_id":"MDQ6VXNlcjIxMTk2ODI0","avatar_url":"https://avatars1.githubusercontent.com/u/21196824?v=4","gravatar_id":"","url":"https://api.github.com/users/davidlrosenblum","html_url":"https://github.com/davidlrosenblum","followers_url":"https://api.github.com/users/davidlrosenblum/followers","following_url":"https://api.github.com/users/davidlrosenblum/following{/other_user}","gists_url":"https://api.github.com/users/davidlrosenblum/gists{/gist_id}","starred_url":"https://api.github.com/users/davidlrosenblum/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/davidlrosenblum/subscriptions","organizations_url":"https://api.github.com/users/davidlrosenblum/orgs","repos_url":"https://api.github.com/users/davidlrosenblum/repos","events_url":"https://api.github.com/users/davidlrosenblum/events{/privacy}","received_events_url":"https://api.github.com/users/davidlrosenblum/received_events","type":"User","site_admin":false},"created_at":"2018-11-16T17:36:19Z","updated_at":"2018-11-16T17:36:19Z","author_association":"NONE","body":"Hi\n\nRight now, the relationship is fixed in the model.  You can specify multiple labels now, but would it work if the label was in the incoming data and what was in the model was just a placeholder <value from property:xyz>?\n\nI can see perhaps a test of the incoming data to pick one of the labels authored in the model as you suggested also working, but not as data driven as above.  The benefit is the model is fixed by the author.\n\nI don't think the third option was what I was trying to accomplish, but maybe I’m not getting it.\n\nDavid\n\n> On Nov 15, 2018, at 4:40 PM, Matt Casters <notifications@github.com> wrote:\n> \n> How would that work in the modelling? We could add multiple labels to the relationship (IS_CURRENT and IS_PREVIOUS). The input mapping could then include which label to pick. What do you think?\n> We can then do a validation to see if the label is valid.\n> Another option is to add multiple relationships in the model between 2 identical node pairs. In the mapping we can then simply pick the right relationship based on the given node label.\n> \n> Any preference?\n> \n> —\n> You are receiving this because you authored the thread.\n> Reply to this email directly, view it on GitHub <https://github.com/knowbi/knowbi-pentaho-pdi-neo4j-output/issues/55#issuecomment-439199953>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AUNwGO06fGqnTteEEf5p0ABlaxLzxhpyks5uvd8_gaJpZM4XM-FA>.\n> \n\n"}}
{"actor":{"display_login":"davidlrosenblum"}}