Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[exporter/elasticsearch] Use exporterhelper/batchsender for reliability #32632
[exporter/elasticsearch] Use exporterhelper/batchsender for reliability #32632
Changes from 74 commits
3cd3903
4341a37
5c04204
39f0fa1
bc692f0
c5fd34c
7fdf150
97d5c19
5608755
c5cbe79
889fe7f
f71d3b2
709ca01
4474b3b
215295e
961ffab
683dca3
e46b165
ca810d4
364e27d
946bf2f
ea3edd3
16ece1c
9d83826
bf115c2
7258704
2958362
6db1c65
ae1c8cb
332ee78
7978e89
33c4bfe
6bcb999
8aa720b
160de51
686e8ae
10a2748
562ebaa
d48f75f
6ecce33
6178e2f
8afdc94
04495ff
33df16b
7c4b5b2
91ea93d
ec37579
f596602
32029c2
babf6ad
454540a
14e1804
8e15426
7dfea92
622d6e8
36bcd9c
18e9ce4
179430b
6fc2df9
da8a530
caa68cf
428f7d7
714e26d
cc83ff1
99f2b63
5f05116
b91a2ad
3a7c19c
ca69b64
e68b427
7312e36
5d428e1
d7fbaa8
27f055d
3a17fa5
a354670
f6910bb
9313acb
96fa3f8
4f591d0
cf6f599
01e1d2c
0e5c381
f6ad0e2
16b3a79
b98f7b2
d17554d
77e99c9
78a8800
0939b45
71d84f6
4bd68f5
6fb2fc3
4c2ba65
1b14f4a
ad23b96
8d4d4c1
97494ed
d9bd55f
0e75f8b
664849f
4006cd9
3828a87
dae3590
1d10bbf
ebd99e2
a64b62b
d5a0d16
0b4acf3
ae9440d
8591c12
031c3c8
8d698f2
eae71c0
0c39b73
a0c4c06
887b06d
20c5799
18ce06d
5652cbf
4acd29e
6140933
5b25bba
c580f37
ac900bd
fd56e5f
96ce9d6
7c24c27
c62b153
fb6fa02
b860dc0
9ee882e
e783105
8d61908
6a5a2e3
50e9353
e87e797
38c01eb
9113d1c
1ad29d4
862876e
7b289f1
d7881b3
be1a7f7
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
bike shed, but mostly interested if this is for parity with commit messages or a desire for how release notes/change log reads
I understand rationale of imperative form in commit messages (do this, vs this does this). That said, is it more natural to as a reader of release notes/change log to say the action taking place?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't mind the bike shed. Not a native speaker so both read identical to me. I use imperative form in git commit messages and therefore the same here.
Would be nice if we can be consistent within this component and even across components. There is no guideline in CONTRIBUTING on what's preferred. Looking at https://github.com/open-telemetry/opentelemetry-collector-contrib/releases it is ~50/50 at the moment.
Would appreciate your thoughts on how to move forward in this PR and in future PRs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TL;DR; I suggest we follow Go on commit style, and happy to raise a PR to the CONTRIBUTING file if there are a couple 👍
Personally, I think release notes are different than commit messages, but I think it helps to consolidate the commit style since you noticed it is 50/50. Release notes, basically I would save to after we agree on commit style ;)
What reads imperative to me ("do this") sounds different if you prefix first. For example, the reason it doesn't sound bad in Go, is because they spell it out. They suggest to think of the prefix "This change modifies Go to _____.", and if that works out, use it as the commit first line (after the prefix of the package affected). You can imagine in this project, we could say "This change modifies the opentelemetry collector exporter/elasticsearch to use exporthelper/batchsender for reliability. Sounds fine to me!
Here's the doc on Go, and I suggest we use/blame it on them, basically derive and cite this is following go contribution style. https://go.dev/doc/contribute#commit_messages
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TIL. Yes, I agree on the commit style. It is also close to my usual practice.