This is an automated email from the ASF dual-hosted git repository.
lujiajing pushed a change to branch optimize-banyandb-measure-integration
in repository https://gitbox.apache.org/repos/asf/skywalking.git
discard 143141069d polish registry
omit 9768f5ad35 Merge branch 'master' into
optimize-banyandb-measure-integration
omit 93468c96fc Merge branch 'master' into
optimize-banyandb-measure-integration
omit 29a7043af4 fix stream settings
omit a9b67f8e65 address #10102
omit 24b4e46081 resolve issue #10104
add c5cbd3a14c Optimize `flushInterval` of ElasticSearch BulkProcessor
(#10135)
add 4c08dbf4c7 resolve issue #10104
add 6a99bac112 address #10102
add 5d0d869884 fix stream settings
add ce3a554f54 polish registry
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (143141069d)
\
N -- N -- N refs/heads/optimize-banyandb-measure-integration
(ce3a554f54)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
docs/en/changes/changes.md | 1 +
.../library/elasticsearch/bulk/BulkProcessor.java | 20 ++++++++++++++++++--
2 files changed, 19 insertions(+), 2 deletions(-)
