Skip to content

Conversation

@ph
Copy link
Contributor

@ph ph commented Nov 10, 2014

This PRs includes a lot of changes.

@jordansissel
Copy link
Contributor

Does this fix elastic/logstash#1528, also?

@ph
Copy link
Contributor Author

ph commented Nov 11, 2014

yes it also fix elastic/logstash#1528
Had a similar bug when I moved to an async uploader.

@jsvd
Copy link
Member

jsvd commented Nov 21, 2014

@ph please remove the "Gemfile.orig" from the PR :)

@ph
Copy link
Contributor Author

ph commented Nov 21, 2014

Good catch @jsvd !

@luismfonseca
Copy link

Can anyone estimate when will this be merged?

@ph
Copy link
Contributor Author

ph commented Jan 7, 2015

@suyograo can you review this? It also have the feature describe in #2

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a matter of style, but this two lines could be generalized using using let statements.

@purbon
Copy link

purbon commented Jan 8, 2015

As a general comment on the specs, I would enforce the idea of using more the power of subjects, something like what we can see http://www.relishapp.com/rspec/rspec-core/v/2-11/docs/subject/explicit-subject#subject-in-top-level-group, what do you think?

@ph
Copy link
Contributor Author

ph commented Jan 9, 2015

@purbon I have added the tests to ensure we don't lose any events when doing the file rotation.
Concerning using more subjects, could you take one or 2 example in the suite to give me an idea how you would do it?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need a timestamp for this temp file name?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After thinking, this would make sure the check works if something goes wrong.
I'll add it.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe move this to the outside of the if, since it will be called either way

@ph
Copy link
Contributor Author

ph commented Jan 15, 2015

adressed @jsvd and @purbon comments.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As far as this test are using a real S3 for testing, they should go into the integration part.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well they test if the file rotation is done locally and we don't drop events when creating new files. Not sure why this local test would require a real S3 connection?

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It requires a local connection for me, you should probably mock the connection parts.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll do more testing, the AWS.stub! at https://github.com/logstash-plugins/logstash-output-s3/pull/1/files#diff-14cf776b93312a411664cdaf9463b8b3R14 should mock all the connections made from the aws-sdk.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not in this case, at less for me.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Adding a note:
The call was mocked, but the S3 settings were not explicitly set in the config for the test.
The aws_mixin has multiples fallback and it was picking the config in my environment.

@elasticsearch-bot
Copy link

Merged sucessfully into master!

@ph ph closed this in f1816fb Jan 16, 2015
ph added a commit that referenced this pull request Jan 16, 2015
… gemspec to require stud 0.0.18

adding integration test for s3

Fixes #1
ph added a commit that referenced this pull request Jan 16, 2015
ph added a commit that referenced this pull request Jan 16, 2015
ph added a commit that referenced this pull request Jan 16, 2015
ph added a commit that referenced this pull request Jan 16, 2015
ph added a commit that referenced this pull request Jan 16, 2015
ph added a commit that referenced this pull request Jan 16, 2015
ph added a commit that referenced this pull request Jan 16, 2015
ph added a commit that referenced this pull request Jan 16, 2015
ph added a commit that referenced this pull request Jan 16, 2015
ph added a commit that referenced this pull request Jan 16, 2015
ph added a commit that referenced this pull request Jan 16, 2015
ph added a commit that referenced this pull request Jan 16, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment