{"action":"created","issue":{"url":"https://api.github.com/repos/elasticsearch/logstash-contrib/issues/74","labels_url":"https://api.github.com/repos/elasticsearch/logstash-contrib/issues/74/labels{/name}","comments_url":"https://api.github.com/repos/elasticsearch/logstash-contrib/issues/74/comments","events_url":"https://api.github.com/repos/elasticsearch/logstash-contrib/issues/74/events","html_url":"https://github.com/elasticsearch/logstash-contrib/issues/74","id":35851764,"number":74,"title":"S3 output on windows - no absolute path.","user":{"login":"SleeperSmith","id":1109339,"avatar_url":"https://avatars.githubusercontent.com/u/1109339?v=3","gravatar_id":"","url":"https://api.github.com/users/SleeperSmith","html_url":"https://github.com/SleeperSmith","followers_url":"https://api.github.com/users/SleeperSmith/followers","following_url":"https://api.github.com/users/SleeperSmith/following{/other_user}","gists_url":"https://api.github.com/users/SleeperSmith/gists{/gist_id}","starred_url":"https://api.github.com/users/SleeperSmith/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/SleeperSmith/subscriptions","organizations_url":"https://api.github.com/users/SleeperSmith/orgs","repos_url":"https://api.github.com/users/SleeperSmith/repos","events_url":"https://api.github.com/users/SleeperSmith/events{/privacy}","received_events_url":"https://api.github.com/users/SleeperSmith/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2014-06-17T01:46:15Z","updated_at":"2015-02-11T14:18:28Z","closed_at":"2015-02-11T14:18:28Z","body":"Version 1.4.1\r\n\r\nWhen I try to use S3 output on windows, an error saying\r\n\r\nNeither current working directory (null) nor /opt/\\<blah blah> resolve to absolute path.\r\n\r\nThrows an exception, continues to log into S3_temp (the part file keeps growing). As far as I have seen, it just throws once and never tries again.\r\n\r\nOn a side note, there's also a bug with S3_temp path. I have put logstash in D:\\logstash. It opens a file in D:\\logstash\\opt\\\\\\<blah>\\S3_temp\\ and then proceeds to log into D:\\opt\\\\\\<blah>\\S3_temp\\"},"comment":{"url":"https://api.github.com/repos/elasticsearch/logstash-contrib/issues/comments/73887432","html_url":"https://github.com/elasticsearch/logstash-contrib/issues/74#issuecomment-73887432","issue_url":"https://api.github.com/repos/elasticsearch/logstash-contrib/issues/74","id":73887432,"user":{"login":"ph","id":640,"avatar_url":"https://avatars.githubusercontent.com/u/640?v=3","gravatar_id":"","url":"https://api.github.com/users/ph","html_url":"https://github.com/ph","followers_url":"https://api.github.com/users/ph/followers","following_url":"https://api.github.com/users/ph/following{/other_user}","gists_url":"https://api.github.com/users/ph/gists{/gist_id}","starred_url":"https://api.github.com/users/ph/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ph/subscriptions","organizations_url":"https://api.github.com/users/ph/orgs","repos_url":"https://api.github.com/users/ph/repos","events_url":"https://api.github.com/users/ph/events{/privacy}","received_events_url":"https://api.github.com/users/ph/received_events","type":"User","site_admin":false},"created_at":"2015-02-11T14:18:28Z","updated_at":"2015-02-11T14:18:28Z","body":"Yes it is solved, in the next version of the plugin we are using the OS tmp dir as the default, so you will get `/tmp/logstash` on unix. But you can now override it using the `temporary_directory` option."}}