{"action":"created","issue":{"url":"https://api.github.com/repos/awslabs/aws-lambda-redshift-loader/issues/59","labels_url":"https://api.github.com/repos/awslabs/aws-lambda-redshift-loader/issues/59/labels{/name}","comments_url":"https://api.github.com/repos/awslabs/aws-lambda-redshift-loader/issues/59/comments","events_url":"https://api.github.com/repos/awslabs/aws-lambda-redshift-loader/issues/59/events","html_url":"https://github.com/awslabs/aws-lambda-redshift-loader/issues/59","id":125298756,"number":59,"title":"Enhancement to Support Running SQL Scripts Pre and Post Load","user":{"login":"FrancisLau-Smartsheet","id":16261725,"avatar_url":"https://avatars.githubusercontent.com/u/16261725?v=3","gravatar_id":"","url":"https://api.github.com/users/FrancisLau-Smartsheet","html_url":"https://github.com/FrancisLau-Smartsheet","followers_url":"https://api.github.com/users/FrancisLau-Smartsheet/followers","following_url":"https://api.github.com/users/FrancisLau-Smartsheet/following{/other_user}","gists_url":"https://api.github.com/users/FrancisLau-Smartsheet/gists{/gist_id}","starred_url":"https://api.github.com/users/FrancisLau-Smartsheet/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/FrancisLau-Smartsheet/subscriptions","organizations_url":"https://api.github.com/users/FrancisLau-Smartsheet/orgs","repos_url":"https://api.github.com/users/FrancisLau-Smartsheet/repos","events_url":"https://api.github.com/users/FrancisLau-Smartsheet/events{/privacy}","received_events_url":"https://api.github.com/users/FrancisLau-Smartsheet/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2016-01-07T00:58:32Z","updated_at":"2016-01-11T12:34:23Z","closed_at":null,"body":"Ian\r\n\r\nWe have a scenario where we like to run a SQL script against Redshift after a load succeeds. Before we implement it, we like to run it by you and get your feedback. Here is the functional overview:\r\n\r\n1. During setup, user can specify a URI to a SQL script in S3 to execute before or after the data load. One or both can specified.\r\n\r\n2. At runtime, the appropriate SQL scripts are executed against the Redshift DB either before or after the copy command. \r\n\r\nAny pitfalls we should watch out for? Any feedback for improvements? Do you know if we can get error codes from the SQL execution back to the Lambda function? Will this feature be useful to other users?\r\n\r\nThanks"},"comment":{"url":"https://api.github.com/repos/awslabs/aws-lambda-redshift-loader/issues/comments/170530072","html_url":"https://github.com/awslabs/aws-lambda-redshift-loader/issues/59#issuecomment-170530072","issue_url":"https://api.github.com/repos/awslabs/aws-lambda-redshift-loader/issues/59","id":170530072,"user":{"login":"IanMeyers","id":6339696,"avatar_url":"https://avatars.githubusercontent.com/u/6339696?v=3","gravatar_id":"","url":"https://api.github.com/users/IanMeyers","html_url":"https://github.com/IanMeyers","followers_url":"https://api.github.com/users/IanMeyers/followers","following_url":"https://api.github.com/users/IanMeyers/following{/other_user}","gists_url":"https://api.github.com/users/IanMeyers/gists{/gist_id}","starred_url":"https://api.github.com/users/IanMeyers/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/IanMeyers/subscriptions","organizations_url":"https://api.github.com/users/IanMeyers/orgs","repos_url":"https://api.github.com/users/IanMeyers/repos","events_url":"https://api.github.com/users/IanMeyers/events{/privacy}","received_events_url":"https://api.github.com/users/IanMeyers/received_events","type":"User","site_admin":false},"created_at":"2016-01-11T12:34:23Z","updated_at":"2016-01-11T12:34:23Z","body":"2.2.0 is now out, so feel free to build against that version. I've thought it through, and I think this would be a good addition. Let's make the load of the objects from S3 very resistant to failures, and have think about what configuration options make sense regarding failure tolerance (if any...).\r\n\r\nThanks!"}}