{"action":"created","issue":{"url":"https://api.github.com/repos/amplab/keystone/issues/276","repository_url":"https://api.github.com/repos/amplab/keystone","labels_url":"https://api.github.com/repos/amplab/keystone/issues/276/labels{/name}","comments_url":"https://api.github.com/repos/amplab/keystone/issues/276/comments","events_url":"https://api.github.com/repos/amplab/keystone/issues/276/events","html_url":"https://github.com/amplab/keystone/pull/276","id":156647462,"number":276,"title":"Internal dag execution","user":{"login":"tomerk","id":676357,"avatar_url":"https://avatars.githubusercontent.com/u/676357?v=3","gravatar_id":"","url":"https://api.github.com/users/tomerk","html_url":"https://github.com/tomerk","followers_url":"https://api.github.com/users/tomerk/followers","following_url":"https://api.github.com/users/tomerk/following{/other_user}","gists_url":"https://api.github.com/users/tomerk/gists{/gist_id}","starred_url":"https://api.github.com/users/tomerk/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tomerk/subscriptions","organizations_url":"https://api.github.com/users/tomerk/orgs","repos_url":"https://api.github.com/users/tomerk/repos","events_url":"https://api.github.com/users/tomerk/events{/privacy}","received_events_url":"https://api.github.com/users/tomerk/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-05-25T02:00:47Z","updated_at":"2016-05-25T05:45:20Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/amplab/keystone/pulls/276","html_url":"https://github.com/amplab/keystone/pull/276","diff_url":"https://github.com/amplab/keystone/pull/276.diff","patch_url":"https://github.com/amplab/keystone/pull/276.patch"},"body":"Introduces user APIs that build on top of the previously introduced Graph.\r\n"},"comment":{"url":"https://api.github.com/repos/amplab/keystone/issues/comments/221478775","html_url":"https://github.com/amplab/keystone/pull/276#issuecomment-221478775","issue_url":"https://api.github.com/repos/amplab/keystone/issues/276","id":221478775,"user":{"login":"etrain","id":1326181,"avatar_url":"https://avatars.githubusercontent.com/u/1326181?v=3","gravatar_id":"","url":"https://api.github.com/users/etrain","html_url":"https://github.com/etrain","followers_url":"https://api.github.com/users/etrain/followers","following_url":"https://api.github.com/users/etrain/following{/other_user}","gists_url":"https://api.github.com/users/etrain/gists{/gist_id}","starred_url":"https://api.github.com/users/etrain/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/etrain/subscriptions","organizations_url":"https://api.github.com/users/etrain/orgs","repos_url":"https://api.github.com/users/etrain/repos","events_url":"https://api.github.com/users/etrain/events{/privacy}","received_events_url":"https://api.github.com/users/etrain/received_events","type":"User","site_admin":false},"created_at":"2016-05-25T05:45:20Z","updated_at":"2016-05-25T05:45:20Z","body":"I am still working my way through this PR and won't look at your responses tonight - so don't feel like you need to post them real-time. \r\n\r\nMy meta-takeaway from this so far is that \r\n1. There are a bunch of new classes being introduced, and I don't have a clear sense of the execution flow through these new classes - I don't know if it's a written description or a box and pointers diagram or what - but as it stands now this code feels like something that fits in your head but isn't self-explanatory. It doesn't have to be self-explanatory, of course, but it should be something you can explain in a small document or ideally on a napkin :)\r\n2. Let's be careful about changing our user-facing APIs too much. They're simple and that's a good thing. Changing method names that we expose to users when simply creating a new method name for the internal behavior we want to support is probably a better approach.\r\n3. I think there's a decent amount of confusion/complexity coming in because we say that pipelines take RDDs and emit `PipelineDatasetOut`. Instead if we're going to introduce yet another wrapper for a data set, we should at least have the API consistently work with these things both as input and output. I'm still not convinced we need it, but it will at least make the API more consistent and easier to understand and may solve a bunch of the naming/override problems we're seeing.\r\n\r\n"}}
{"actor":{"display_login":"etrain"}}