← 输入框|github.com|刷新
Skip to content

docs: Clarify the initial incremental materialization window - #6888

Merged
ntkathole merged 1 commit into
feast-dev:masterfrom
zqzq0422:docs/initial-incremental-window
Sep 29, 2026
Merged

ntkathole merged 1 commit into
feast-dev:masterfrom
zqzq0422:docs/initial-incremental-window

Conversation

@zqzq0422

Copy link
Copy Markdown
Contributor

What this PR does / why we need it:

The CLI reference says the first incremental materialization starts at the beginning of time. For regular (non-on-demand) feature views, the implementation uses the current time minus the feature view TTL, falls back to 52 weeks for a zero TTL, and requires a previous materialization when the TTL is unset.

Update the CLI reference and quickstart to describe this initial window and distinguish current time from the supplied end timestamp. This is a documentation-only change.

Which issue(s) this PR fixes:

No linked issue.

Checks

  • I've made sure the tests are passing.
  • My commits are signed off (git commit -s)
  • My PR title follows conventional commits format

Testing Strategy

  • Unit tests
  • Integration tests
  • Manual tests
  • Testing is not required for this change

Compared both descriptions with FeatureStore.materialize_incremental and its CLI caller at base revision 213a130c333bdf6ae47b9d8178c7d2c6aff9f396. A focused documentation/source consistency check fails before the edits and passes afterward. git diff --check passes. Runtime tests and a full documentation build were not run.

Misc

Checked the related changes in #4734 and #6481: the former introduced the earlier quickstart wording; the latter clarifies historical retrieval TTL versus online-store expiration. This PR specifically addresses the initial incremental materialization window.

Signed-off-by: chloe <823083779@qq.com>
@zqzq0422
zqzq0422 requested a review from a team as a code owner September 29, 2026 02:27
@ntkathole
ntkathole merged commit 0b03236 into feast-dev:master Sep 29, 2026
21 checks 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