In the quickstart documentation, step 6 mistakenly provides both start and end date parameters to the feast materialize-incremental command (which only takes an end date). This was probably just confused with the parameters for the feast materialize command. Running the command as is results in an error.
In addition, the docs explain that materialize-incremental "serializes all new features since the last materialize call", but this is confusing since no materialize call has been run in the quickstart.
In this PR, I fixed the parameter input, and improved the documentation to include a mention of when the ttl is used.
Which issue(s) this PR fixes:
Misc
To reproduce the issue:
Initialize the quickstart repo: feast init feature_repo # run in examples/quickstart
What this PR does / why we need it:
In the quickstart documentation, step 6 mistakenly provides both start and end date parameters to the
feast materialize-incremental
command (which only takes an end date). This was probably just confused with the parameters for thefeast materialize
command. Running the command as is results in an error.In addition, the docs explain that
materialize-incremental
"serializes all new features since the last materialize call", but this is confusing since nomaterialize
call has been run in the quickstart.In this PR, I fixed the parameter input, and improved the documentation to include a mention of when the ttl is used.
Which issue(s) this PR fixes:
Misc
To reproduce the issue:
feast init feature_repo
# run in examples/quickstartfeast apply
feast materialize-incremental $LAST_YEAR $CURRENT_TIME