Skip to content

fix duplicate changelog header#530

Closed
jshook wants to merge 1 commit into
mainfrom
jshook/fixheader
Closed

fix duplicate changelog header#530
jshook wants to merge 1 commit into
mainfrom
jshook/fixheader

Conversation

@jshook
Copy link
Copy Markdown
Contributor

@jshook jshook commented Sep 19, 2025

This merely removes a duplicitous header which was added when I "updated" changelog. The changelog logic doesn't know how to reconcile deltas to the same labeled section yet.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Sep 19, 2025

Before you submit for review:

  • Does your PR follow guidelines from CONTRIBUTIONS.md?
  • Did you summarize what this PR does clearly and concisely?
  • Did you include performance data for changes which may be performance impacting?
  • Did you include useful docs for any user-facing changes or features?
  • Did you include useful javadocs for developer oriented changes, explaining new concepts or key changes?
  • Did you trigger and review regression testing results against the base branch via Run Bench Main?
  • Did you adhere to the code formatting guidelines (TBD)
  • Did you group your changes for easy review, providing meaningful descriptions for each commit?
  • Did you ensure that all files contain the correct copyright header?

If you did not complete any of these, then please explain below.

@jshook jshook closed this Sep 22, 2025
@jshook
Copy link
Copy Markdown
Contributor Author

jshook commented Sep 22, 2025

I'll add a new PR which will avoid the breaking path

@jshook jshook deleted the jshook/fixheader branch September 22, 2025 18:34
eolivelli added a commit to eolivelli/jvector that referenced this pull request May 11, 2026
Introduce a dedicated CompactionProgressListener functional interface
and a compact(Path, CompactionProgressListener) overload so callers
can track streaming compaction I/O progress without parsing log messages.

The listener is called every ten batches (and at level completion) with
(completedBatches, totalBatches) for each graph level processed.  The
existing compact(Path) delegate passes null and preserves full backward
compatibility.

Motivated by HerdDB issue datastax#530: the index-optimizer's GET /status
endpoint showed batches_written=0 / pct_complete=0 throughout multi-
minute streaming compaction runs because there was no hook to propagate
the per-batch progress counters back to the HTTP status object.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant