Skip to content

NIFI-16045: Initial API for Processor / Connector Backlog#98

Merged
pvillard31 merged 2 commits into
apache:mainfrom
markap14:api-connector-backlog
Jun 25, 2026
Merged

NIFI-16045: Initial API for Processor / Connector Backlog#98
pvillard31 merged 2 commits into
apache:mainfrom
markap14:api-connector-backlog

Conversation

@markap14

Copy link
Copy Markdown
Contributor

Summary

NIFI-00000

Tracking

Please complete the following tracking steps prior to pull request creation.

Issue Tracking

Pull Request Tracking

  • Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
  • Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

  • Pull Request based on current revision of the main branch
  • Pull Request refers to a feature branch with one commit containing changes

* @param instant the moment at which the component was last observed as fully caught up
* @return a new Backlog
*/
public static Backlog lastCaughtUp(final Instant instant) {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Since lastCaughtUp(Instant) is documented as useful for combining with a count-only Backlog, but plus() downgrades any count-only combine with it to AT_LEAST, is that downgrade intended when the timestamp adds no numeric uncertainty?

}

@Test
public void testCaughtUpFactoryProducesZerosAndTimestamp() {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Can we add a small test for the builder rejecting negative flowFiles, bytes, and records values?

* @return a Future that will be completed when the draining is complete
*/
CompletableFuture<Void> drainFlowFiles(FlowContext flowContext);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Is the extra blank line at the end of Connector intended, or a stray change?

@markap14

Copy link
Copy Markdown
Contributor Author

[gpt-5.4] @pvillard31 I addressed the follow-up feedback in 33109c8.

  • Combining a count-only Backlog with a timestamp-only Backlog now preserves exact numeric precision.
  • Added focused tests for the timestamp-only combination case and for rejecting negative flowFiles, bytes, and records values.
  • Removed the stray blank line in Connector and cleaned up the adjacent JavaDocs touched in this pass.

Preserve exact numeric precision when combining a count-only Backlog with a timestamp-only Backlog, and add focused tests for timestamp-only and negative-value cases. Also clean up related API JavaDocs and formatting surfaced during review.
@markap14 markap14 force-pushed the api-connector-backlog branch from 33109c8 to b33a3a1 Compare June 25, 2026 14:48
@pvillard31 pvillard31 merged commit ef1d975 into apache:main Jun 25, 2026
1 check passed
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.

2 participants