Fluent API entry points that don't require Data as Input if the Metrics are already available in a MetricsRepository

[stefan-grafberger]

Using the MetricsRepository, you can reuse metrics calculated at some earlier point. If you do that, you don't always require the data again if everything that's needed was already calculated before. At the moment, it is possible to work around that issue for most cases by just inputting an empty DataFrame and then use the method .reuseExistingResultsForKey(resultKey, failIfResultsForReusingMissing=true). However, we should properly support this use case in our API, for example by adding a method .withoutData in addition to the current .onData methods. In case we need some information about the schema, providing that instead of the data itself should be enough.

[Yash0215]

if the metrics is already available that means its already calculated on some data and also there no need to merge previous State into new State since there is no data. so why we need this kind of API if metrics already calculated? can you proved some use case?

[lange-labs]

Closing due to inactivity