feature-engineering

• transform_primitive.py is becoming very large. I suggest splitting out into separate files.
• We could split this file up by groups (such as LatLong transform primitives in 1 file).

The current DynamoDB implementation does sequential gets (https://github.com/feast-dev/feast/blob/master/sdk/python/feast/infra/online_stores/dynamodb.py#L163)

Possible Solution

A better approach is to do some multi-get operation or at least run these queries in parallel and collect the results.

Problem
Some of our transformers & estimators are not thoroughly tested or not tested at all.

Solution
Use OpTransformerSpec and OpEstimatorSpec base test specs to provide tests for all existing transformers & estimators.

This issue has been coming up when I use,
automl.predict_proba(input)

I am using the requirements.txt in venv. Shouldn't input have feature names?
This message did not used to come up and I don't know why.

The OpenMLDB project is a community-driven project, thus we welcome all kinds of contribution from the community. We have started an OpenMLDB Contributor Program, which provides rewards to encourage you to join our community.

Here is the explanation about this program (we also provide a Chinese version here):

• We have listed issues that are suitable

The transformer should create computations over windows of past values of the features, and populate them at time t, t being the time of the forecast.

It uses pandas rolling, outputs several comptutations, mean, max, std, etc, and pandas shift to move the computations to the right row.

tmp = (data[variables]
       .rolling(window='3H').mean()  # Average the last 3 hr values.
       .

Currently IterativeAlgorithm logging outputs n pipelines ready for search in the logger when running AutoMLSearch. However, DefaultAlgorithm does not have such output. There could be more places where there are inconsistencies in output and this issue should track investigating where inconsistencies and how to resolve them.