Dong Lin
The purpose of this PR is to allow expired content on the nightly build Flink website to expire. Currently, flink-web does not explicitly specify `ExpiresActive` in `.htaccess`, and therefore content...
We should also replace timestamp format values such as `epoch` and `epoch_millis` with enums.
Users should also be able to specify whether a build-side entry can be deleted after it is successfully matched with a probe-side event. As an example user side, let's say...
It would be useful to support the following expression ``` DerivedFeatureView( name="feature_view_1", source=source, features=[ "remote_table.feature_name + 10", ], ) ```
See https://stackoverflow.com/questions/75074182/feature-and-featureview-versioning This can make it easy for data scientists to do experiments and compare which version of feature can produce better results.
Users should be able to run the following code ``` f_price = Feature( name="price", dtype=types.Float32, transform="item_price_events.price", keys=["item_id"], ) purchase_events_with_features = DerivedFeatureView( name="purchase_events_with_features", source=purchase_events_source, features=[ f_price, f_total_payment_last_two_minutes, ], keep_source_fields=True, ) ```